Re: lib32 or lib64 (was LFS Directions)

2009-09-18 Thread Bryan Kadzban
Tobias Gasser wrote: > Nathan Coulson schrieb: > >> I have been experimenting with a multilib LFS System (where /lib, >> /usr/lib are used for 64bit, and /lib/32, and /usr/lib/32 are used >> for 32bit). I wanted something as close to LFS as possible, >> primarily 64bit, but just enough 32bit so

Re: LFS Directions

2009-09-18 Thread Bryan Kadzban
Bruce Dubbs wrote: > Bryan Kadzban wrote: >> Matthew Burgess wrote: >>> On Thu, 17 Sep 2009 16:18:16 -0500, Bruce Dubbs >>> wrote: >>> #2033 Create initramfs I think this one should be closed as won't fix. The reason for a initrd is for those systems that don't know in a

Re: Problems with setclock in lfs-bootscripts-20090812 LFS 6.5

2009-09-18 Thread Bryan Kadzban
Matthew Burgess wrote: > On Fri, 18 Sep 2009 15:52:44 -0600, Matthew Burgess > wrote: > >> stty: standard input: Inappropriate ioctl for device > > OK, figured this out to be the section of /etc/rc.d/init.d/functions > that sets the COLUMNS variable by calling 'stty' (obvious now!). So, > why c

Re: Problems with setclock in lfs-bootscripts-20090812 LFS 6.5

2009-09-18 Thread Matthew Burgess
On Fri, 18 Sep 2009 15:52:44 -0600, Matthew Burgess wrote: > stty: standard input: Inappropriate ioctl for device OK, figured this out to be the section of /etc/rc.d/init.d/functions that sets the COLUMNS variable by calling 'stty' (obvious now!). So, why can't it set that then? Am I missing

Re: Problems with setclock in lfs-bootscripts-20090812 LFS 6.5

2009-09-18 Thread Matthew Burgess
On Thu, 17 Sep 2009 21:35:47 -0700, Bryan Kadzban wrote: > The kernel has *no* idea what your local time zone is, so it can't work > with an RTC in local-time (I'm pretty sure the kernel help message for > the last option says something to this effect). It always assumes the > RTC is in UTC whe

Re: lib32 or lib64 (was LFS Directions)

2009-09-18 Thread Ken Moffat
2009/9/18 Tobias Gasser : [ snip good explanations ] > what about the kernel modules. they will be 64 bit, don't they have to > be in /lib64/modules? Tried it in clfs. Not worth the aggro. You have to change the top-level kernel Makefile every time. > perl: most will be in /lib/perl as they

Re: LFS Directions

2009-09-18 Thread Ken Moffat
2009/9/18 Nathan Coulson : . > > I have been experimenting with a multilib LFS System (where /lib, > /usr/lib are used for 64bit, and /lib/32, and /usr/lib/32 are used for > 32bit).  I wanted something as close to LFS as possible, primarily > 64bit, but just enough 32bit so if I wanted to compile s

lib32 or lib64 (was LFS Directions)

2009-09-18 Thread Tobias Gasser
Nathan Coulson schrieb: > > I have been experimenting with a multilib LFS System (where /lib, > /usr/lib are used for 64bit, and /lib/32, and /usr/lib/32 are used for > 32bit). I wanted something as close to LFS as possible, primarily > 64bit, but just enough 32bit so if I wanted to compile some

Re: LFS Directions

2009-09-18 Thread Bruce Dubbs
Bryan Kadzban wrote: > Matthew Burgess wrote: >> On Thu, 17 Sep 2009 16:18:16 -0500, Bruce Dubbs >> wrote: >> >>> #2033Create initramfs >>> >>> I think this one should be closed as won't fix. The reason for a >>> initrd is for those systems that don't know in advance which >>> drivers are