Now that 6.3 is finally done, I wanted to think about things that
could be done for the 7.0 release. These are in addition to the normal
updates/bug fixes/etc.

* x86_64 support - I think it would be great is we could get a native
64 bit implementation. It's a very common architecture, and really
there are few changes from the x86 approach. Jeremy has been working
on this in the jh-branch with feedback from Greg and Alexander. I
think it's still up in the air how the book style would go. I.e.,
single book with conditionals or book-per-architecture. A further goal
would be multilib, but I don't think that should enter the picture
until the pure64 implementation is nicely polished.

* initramfs - The limitation of no initramfs right now is inconvenient
as well as limiting in the ways that the drives can be used.

http://linuxfromscratch.org/pipermail/lfs-dev/2007-June/059512.html

Bryan created an initramfs generating tool that works on LFS and
handles lots of root device options. This should be possible to just
drop into LFS and make optional in the kernel and booting sections.

* LSB bootscripts - I'd like to shed the current custom bootscripts
and move to the standardized LSB style. The advantages (to me) are
standardization, removal of crufty custom functions and entry points
in our current implementation, and managed service levels
(dependencies in the script header mean you don't have to guess run
numbers).

The disadvantages are that all scripts need to be updated and
install_initd still needs to be written (I have a shortcut bash
implementation, but it doesn't implement everything). DJ has a setup
in contrib/lsb-v3 that's pretty solid and contains compatibility
wrappers for all our current LFS functions.

Anyway, those are some ideas I had. I'll be shifting my focus to BLFS
now, so I won't be personally working on much here, but I'd like to
discuss in the meantime.

--
Dan
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to