The Testing Area :: January Extensions

S_I: Many people don't chroot, but if it makes things cleaner, go for it

Are you following a recent LFS with old packages (ie, some instructions and patches don't apply) or an old LFS?

Oh. Have fun, LFS is a great way to get a system just to your liking!

I am using LFS 5.0.
Link to LFS-5.0 index [archive.linuxfromscratch.org]
I'm sorry I forgot to mention which version I was using.

Re: patches
I only patched gcc and glibc so far.
For gcc, the patches are meant for gcc-3.3.1, but would still be relevant for gcc-3.3.6, so I manually edited a few files inside 'gcc-3.3.6/'. The patches are very small and very simple, so it's not very hard.

For glibc:
glibc-2.3.2-sscanf-1.patch
glibc-2.3.2-inlining-fixes-2.patch

For gcc pass 2:
gcc-3.3.1-specs-2.patch
gcc-3.3.1-no-fixincludes-2.patch
For gcc last pass (actual LFS install):
('gcc-3.3.1-specs-2.patch' from pass 1 must NOT be applied this time.)
gcc-3.3.1-no-fixincludes-2.patch
gcc-3.3.1-suppress-libiberty.patch

For other software, e.g. coreutils, zlib, etc, I am using newer releases, so there is no need to apply the LFS-5.0 patches.

Small update:
I am no longer using '-fdata-sections -ffunction-sections' in $CFLAGS/CXXFLAGS and '-Wl,--gc-sections' in $LDFLAGS because '--gc-sections' does not work for all packages.
Am also not using '-fomit-frame-pointer', purely for the sake of convenience.
Now using simply CFLAGS/CXXFLAGS='-Os' for all packages in the experimental chroot-environment extension.

I am thinking of naming the extension 'dev-chroot.unc'.
Is that a good name??

Thanks for reading.

Note for slock.dsl:

I thought it locked out ctrl-alt-backspace, but that's apparently not the case. I think slock is better than nothing, but knowledgeable and/or crafty people can still get past it by killing X. I also think it's better than xscreensaver since it's a lot smaller in size and has lower resource demands (no daemon running in background) as long as the reason for running xscreensaver is to lock and/or require password for resuming a session in X. If you want a daemon to automatically set off fireworks or whatever after certain periods of inactivity, then slock never would appeal to you anyway.

If tighter security than this is desired, I can point users to gnu screen. If you're willing to suspend your X session (go to console) while in screen, you can use screen's lock (C-a C-x) to effectively keep users who don't have or can't break your password from using your computer (without rebooting). And if you're using console apps, you can resume your X session without ever interrupting any of your console apps running in screen. And, of course, screen allows you to detach and reattach sessions even remotely if you need to access your session(s) from elsewhere.

Quote (stupid_idiot @ Jan. 25 2008,18:40)

If it helps in compiling for DSL, awesome.

I've been trying to find a a distro that had the same kernel as dsl, apt-get, gcc and gnu-utils while allowing usb boot and apt-getting to ram (Live cd compile only

) but no luck :/

Even then, usb boot is only needed if I couldn't get live-cd toram and apt-get standard. Debian Sarge with a 2.4.27 kernel installed to a HD won't usb-boot :/

Next Page...
original here.