David D.W. Downey
david.downey at codecastle.com
Tue Sep 12 22:02:30 PDT 2000
hehe I have a script I made for something like that. Whenever I release a
tarball of KiXO Linux, the tarballign script updates a number of things in
the system BEFORE starting the tarball. Like the /etc/KixoLinux-release
file which is the current version like alpha-0.4-tb3 ect ect. It also
updates the /etc/issue and /etc/motd files as well.
give me a day to pull it out of the tarball and you can have the code. I
also worte a simple script which just echos out the contents of the
/etc/KixoLinux-release file so folks can get that info right off the bat.
"Run release for me and tell me what it says" is pretty simple. :-)
0On Tue, 12 Sep 2000, Gerard Beekmans wrote:
> The TODO list showed 'discuss /etc/lfsversion'. Let's start that now.
> I've been thinking about having the user create a simple file /etc/lfsversion
> that contains one line: 2.4
> or whatever version of the book was used.
> This could make it easier for us to ask what version of the book was used,
> especially if the user doens't know anymore, or used more than one version.
> We can then work with whatever their /etc/lfsversion contains
> This would also be a nice thing for ALFS. It provides us with an easy way to
> determine which LFS version has been installed so the ALFS tool will know
> what to do if you tell it to 'upgrade to latest version' or something like
David D.W. Downey Red Hat Certified Engineer | Internet Security Specialist $
KiXO Linux http://www.KiXOLinux.com | http://sourceforge.net/projects/kixolinux/
Member OSWG, LPI http://www.owsg.org | http://www.lpi.org
"Any lad can choose the mundane, but tis the explorers that are truly free in choice!"
More information about the lfs-dev