LFS image directory structure
pj at pcrentals.com
Thu Jun 22 08:08:52 PDT 2000
> What left me wondering was the quad main software directories on the
> pcrdallas site:
> then there is also a
> These directories contain stuff off varying importance and their names maybe
> do not reflect their contents.
you are correct - i have been thinking about changing this structure. We
have added a lot of files since we began. i want it to match Gerard's
book exactly - if he calls it mandatory, then i want the ftp directory
name to be mandatory also. Since i am going on vacation in a week, any
changes will need to wait til i come back.
any changes made on the ftp site cause our mirror sites to have to
transfer these changes (and the austrialian mirror has to pay by the mb).
Since the ftp site is 272mb now, i am careful not to make too many
i have a cd burner now and have made a copy of the web site and ftp site.
i am trying to make it bootable also.
thanks for your suggestions. i will work on this in 3-4 weeks.
lfs ftp/news/mail archive
> A NEW STRUCTURE
> Now, let me propose the following: Create a new directory structure, which
> would be:
> which contains all the packages MENTIONED in the book
> which contains all other favorites, add-ons, and optional stuff.
> contains all user-contributed stuff
> could contain X-related stuff, such as: XFree86 3.3.x, XFree86 4.0,
> URW-fonts, etc...
> could contain window managers and desktop environments, like WindowMaker,
> Gnome, KDE, etc..
> could contain networking extras
> In scripts/etc
> we could have scripts that go into etc, and
> would be installer related scripts
> would contain lfs-specific adjustments, etc. The final layout of the
> canonical LFS - non-bootable - install disk would be:
> Since we mention the LSB, its docs should be on the image.
> Note the platform-specific directories; these would contain files that are
> only usable on one of the platforms. With time, we could have support for
> alpha, sun, etc...
> Further organisation is possible, but we won't gain much; I have
> experimented with up to seven levels of directories, but I finally realized
> that this is not really necessary.
> Now, the usable stuff; pcrdallas could make an update list available every
> night; the files could be names like:
> with contents like
> which would be very easy to follow. 'date' in the file name would be a date
> specification if there is more than one; otherwise the file's modification
> date would suffice. In eighter case, it would be very easy to track changes.
> My idea is to support two levels of logs:
> 1. interim
> 2. release
> where the interim updates would be date tagged and only contain what changed
> on that particular date and
> the release updates would contain everything that has changed since the
> latest release.
> With a more functional organization, Gerard could delegate responsibility
> for entire chapters of the book. Like; LFS COULD support an X setup with a
> window manager and even a desktop enviroment - but somebody else could
> maintain these packages and install notes.
> BTW - why not take the book to SourceForge ? We could then actively help out
> looking for errors and making notes better than now with 'releases'...
> Gerard ?
> I would love to maintain and distribute the master LFS disk (even with a
> bootable option) but with a lousy modem connection, I just can't claim that
> honor. Still, if anyone without a CD-burner needs the 2.3.5 image, drop me a
Mail archive: http://www.pcrdallas.com/mail-archives/lfs-discuss
IRC access: server: irc.linuxfromscratch.org port: 6667 channel: #LFS
Unsubscribe: email lfs-discuss-request at linuxfromscratch.org and put
"unsubscribe" (without the quotation marks) in the body of the message
(no subject is required)
More information about the lfs-dev