An interesting response to what I found the way that I did it. I suspect the cause is partly dyslexia and partly because I am a gui refugee. Please note that I have enjoyed the ordeal so far and I am certainly learning some thing - thank you all for the efforts that have been put into the project.
martin welsh [EMAIL PROTECTED] wrote: > Send lfs-support mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://linuxfromscratch.org/mailman/listinfo/lfs-support > or, via email, send a message with subject or body 'help' to > [EMAIL PROTECTED] > > You can reach the person managing the list at > [EMAIL PROTECTED] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of lfs-support digest..." > > > Today's Topics: > > 1. Re: building LFS (Andreas Hofer) > 2. Urgent help needed (Rajeev Bansal) > 3. Re: building LFS (Luuk) > 4. Re: building LFS ([EMAIL PROTECTED]) > 5. Re: building LFS (Matthias Feichtinger) > 6. Dyslexia - or worse. (martin welsh) > 7. Re: building LFS (Randy McMurchy) > 8. Re: Dyslexia - or worse. (Alan Lord) > 9. Re: Dyslexia - or worse. (Philippe Delavalade) > 10. Re: Dyslexia - or worse. (Alan Lord) > 11. Re: building LFS (Dan Nicholson) > 12. Re: Dyslexia - or worse. (lists) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 06 Dec 2007 08:47:58 +0100 > From: Andreas Hofer <[EMAIL PROTECTED]> > Subject: Re: building LFS > To: LFS Support List <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=us-ascii > > > > -------- Original Message -------- > Subject: building LFS > From: Randy McMurchy <[EMAIL PROTECTED]> > To: LFS Support List <[email protected]> > Date: Donnerstag, 06. Dezember 2007 01:59:26 > > >> Dan Nicholson wrote these words on 12/05/07 18:42 CST: >> >>> That's a pretty good idea. It also might be nice if we placed a >>> pointer back to the introduction text before the first package >>> (binutils-pass1) since most people probably skim that section (or skip >>> it entirely) and miss a crucial piece of information. >>> >> Well, I suppose it couldn't hurt, but if someone is such a newbie >> that they don't know to unpack sources and cd into the working >> directory because they didn't bother reading the preface material, >> what makes you think they'll read anything but the actual commands? >> >> I think it's a waste of time. If someone doesn't know to unpack and >> cd into the newly created directory, they're not going read anything >> anywhere in the book to help them. They're going to blindly subscribe >> to the mailing list and ask for help (probably without even consulting >> the faq). >> >> Just my thoughts. >> >> > > I don't agree. I had exactly the same problem and solved it more by > guessing. But, maybe an addition to the general advice explaining that > after unpacking and cd'ing to the source directory some packages require > to build in a dedicated build directora could help a newbee and avoid > repetition of information. > > Andreas > > > ------------------------------ > > Message: 2 > Date: Thu, 06 Dec 2007 13:52:29 +0530 > From: Rajeev Bansal <[EMAIL PROTECTED]> > Subject: Urgent help needed > To: [email protected] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hi All, > > I am trying to boot up 2.6.20-15 Kernel ( Ubuntu Kernel) using my > custom initramfs. But I am getting Kernel Panic when I boot using my > Init script. I am mentioning my init script below. I have followed the > FC7 init script, I really don't know many things which are being used in > that. > > In this Init script everything goes fie till I execute setuproot, while > running setuproot it complains; > > setuproot: moving /dev failed: No such file or directory > no fstab.sys, mounting internal defaults > setuproot: error mounting /proc: No such file or directory > setuproot: error mounting /sys: No such file or directory > > And it gives Kernel Panic after executing switch_root, I am not sure why > switch_root is not executing the /sbin/init, is it due to it couldn't > find it? > 2 > Kernel Panic message: > > [ 47.972305] kjournald starting. Commit interval 5 seconds > [ 48.037871] EXT3-fs: mounted filesystem with ordered data mode. > [ 48.110173] Kernel panic - not syncing: Attempted to kill init! > > I really don't know its a problem of busybox or in my Init script. > > #!/bin/nash > > mount -t proc /proc /proc > setquiet > echo Mounting proc filesystem > echo Mounting sysfs filesystem > mount -t sysfs /sys /sys > echo Creating /dev > mount -o mode=0755 -t tmpfs /dev /dev > mkdir /dev/pts > mount -t devpts -o gid=5,mode=620 /dev/pts /dev/pts > mkdir /dev/shm > mkdir /dev/mapper > echo Creating initial device nodes > mknod /dev/null c 1 3 > mknod /dev/zero c 1 5 > mknod /dev/systty c 4 0 > mknod /dev/tty c 5 0 > mknod /dev/console c 5 12 > mknod /dev/ptmx c 5 2 > mknod /dev/rtc c 10 135 > mknod /dev/tty0 c 4 0 > mknod /dev/tty1 c 4 1 > mknod /dev/tty2 c 4 2 > mknod /dev/tty3 c 4 3 > mknod /dev/tty4 c 4 4 > mknod /dev/tty5 c 4 5 > mknod /dev/tty6 c 4 6 > mknod /dev/tty7 c 4 7 > mknod /dev/tty8 c 4 8 > mknod /dev/tty9 c 4 9 > mknod /dev/tty10 c 4 10 > mknod /dev/tty11 c 4 11 > mknod /dev/tty12 c 4 122 > mknod /dev/ttyS0 c 4 64 > mknod /dev/ttyS1 c 4 65 > mknod /dev/ttyS2 c 4 66 > mknod /dev/ttyS3 c 4 67 > echo Creating block device nodes. > mkblkdevs > echo "Loading usbcore.ko module" > insmod /lib/usbcore.ko > echo "Loading uhci-hcd.ko module" > insmod /lib/uhci-hcd.ko > echo "Loading ohci-hcd.ko module" > insmod /lib/ohci-hcd.ko > echo "Loading ehci-hcd.ko module" > insmod /lib/ehci-hcd.ko > mount -t usbfs /proc/bus/usb /proc/bus/usb > echo "Loading mbcache.ko module" > insmod /lib/mbcache.ko > echo "Loading jbd.ko mo8dule" > insmod /lib/jbd.ko > echo "Loading ext3.ko module" > insmod /lib/ext3.ko > echo "Loading scsi_mod.ko module" > insmod /lib/scsi_mod.ko > echo "Loading sd_mod.ko module" > insmod /lib/sd_mod.ko > echo "Loading sg.ko module" > insmod /lib/sg.ko > echo "Loading libata.ko module" > insmod /lib/libata.ko > echo "Loading ata_generic.ko module" > insmod /lib/ata_generic.ko > echo "Loading ata_piix.ko module" > insmod /lib/ata_piix.ko > echo Waiting for driver initialization. > stabilized --hash --interval 250 /proc/scsi/scsi > insmod /l8ib/scsi_wait_scan.ko > rmmod scsi_wait_scan > mkblkdevs > echo Creating root device. > mkrootdev -t ext3 -o defaults,ro sda2 > echo Mounting root filesystem. > mount -o defaults,ro -t ext3 /dev/sda2 / > echo Setting up other filesystems. > setuproot > echo Switching to new root and running init. > exec switch_root / .ext3 /sbin/init > echo Booting has failed. > sleep -1 > > Thanks > Rajeev Bansal. > > > ******************************************************************************** > This email message (including any attachments) is for the sole use of the > intended recipient(s) > and may contain confidential, proprietary and privileged information. Any > unauthorized review, > use, disclosure or distribution is prohibited. If you are not the intended > recipient, > please immediately notify the sender by reply email and destroy all copies of > the original message. > Thank you. > > Intoto Inc. > > > > ------------------------------ > > Message: 3 > Date: Thu, 06 Dec 2007 10:03:31 +0100 > From: Luuk <[EMAIL PROTECTED]> > Subject: Re: building LFS > To: LFS Support List <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain > > On Thu, 2007-12-06 at 08:47 +0100, Andreas Hofer wrote: > >> -------- Original Message -------- >> Subject: building LFS >> From: Randy McMurchy <[EMAIL PROTECTED]> >> To: LFS Support List <[email protected]> >> Date: Donnerstag, 06. Dezember 2007 01:59:26 >> >> >>> Dan Nicholson wrote these words on 12/05/07 18:42 CST: >>> >>>> That's a pretty good idea. It also might be nice if we placed a >>>> pointer back to the introduction text before the first package >>>> (binutils-pass1) since most people probably skim that section (or skip >>>> it entirely) and miss a crucial piece of information. >>>> >>> Well, I suppose it couldn't hurt, but if someone is such a newbie >>> that they don't know to unpack sources and cd into the working >>> directory because they didn't bother reading the preface material, >>> what makes you think they'll read anything but the actual commands? >>> >>> I think it's a waste of time. If someone doesn't know to unpack and >>> cd into the newly created directory, they're not going read anything >>> anywhere in the book to help them. They're going to blindly subscribe >>> to the mailing list and ask for help (probably without even consulting >>> the faq). >>> >>> Just my thoughts. >>> >>> >> I don't agree. I had exactly the same problem and solved it more by >> guessing. But, maybe an addition to the general advice explaining that >> after unpacking and cd'ing to the source directory some packages require >> to build in a dedicated build directora could help a newbee and avoid >> repetition of information. >> >> Andreas >> > > exactly that point, about the 'dedicated build directory', was the point > that i missed... > > again, i want to thank everyone for giving feedback on this, > and yes i probably skipped the "Important" sections in chapter 5.1 ;-( > > Luuk > > > > > ------------------------------ > > Message: 4 > Date: Thu, 6 Dec 2007 10:38:12 +0100 > From: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > Subject: Re: building LFS > To: "LFS Support List" <[email protected]> > Message-ID: > <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=UTF-8 > > I skipped that section too initially. And I know how to do a "cd" and > more than that. Its all about losing attention and focus, and being > "fast on the trigger". Given that LFS takes time to build even when > automated, there should be no reason to skip reading the book :) Maybe > a warning sign saying "It takes at least a day for fastest systems to > build LFS, you dont gain anything by jumping straight to commands!" > > -Armen. > > On Dec 6, 2007 10:03 AM, Luuk <[EMAIL PROTECTED]> wrote: > >> On Thu, 2007-12-06 at 08:47 +0100, Andreas Hofer wrote: >> >>> -------- Original Message -------- >>> Subject: building LFS >>> From: Randy McMurchy <[EMAIL PROTECTED]> >>> To: LFS Support List <[email protected]> >>> Date: Donnerstag, 06. Dezember 2007 01:59:26 >>> >>> >>>> Dan Nicholson wrote these words on 12/05/07 18:42 CST: >>>> >>>>> That's a pretty good idea. It also might be nice if we placed a >>>>> pointer back to the introduction text before the first package >>>>> (binutils-pass1) since most people probably skim that section (or skip >>>>> it entirely) and miss a crucial piece of information. >>>>> >>>> Well, I suppose it couldn't hurt, but if someone is such a newbie >>>> that they don't know to unpack sources and cd into the working >>>> directory because they didn't bother reading the preface material, >>>> what makes you think they'll read anything but the actual commands? >>>> >>>> I think it's a waste of time. If someone doesn't know to unpack and >>>> cd into the newly created directory, they're not going read anything >>>> anywhere in the book to help them. They're going to blindly subscribe >>>> to the mailing list and ask for help (probably without even consulting >>>> the faq). >>>> >>>> Just my thoughts. >>>> >>>> >>> I don't agree. I had exactly the same problem and solved it more by >>> guessing. But, maybe an addition to the general advice explaining that >>> after unpacking and cd'ing to the source directory some packages require >>> to build in a dedicated build directora could help a newbee and avoid >>> repetition of information. >>> >>> Andreas >>> >> exactly that point, about the 'dedicated build directory', was the point >> that i missed... >> >> again, i want to thank everyone for giving feedback on this, >> and yes i probably skipped the "Important" sections in chapter 5.1 ;-( >> >> Luuk >> >> >> >> -- >> http://linuxfromscratch.org/mailman/listinfo/lfs-support >> FAQ: http://www.linuxfromscratch.org/lfs/faq.html >> Unsubscribe: See the above information page >> >> > > > ------------------------------ > > Message: 5 > Date: Thu, 6 Dec 2007 11:42:05 +0100 > From: Matthias Feichtinger <[EMAIL PROTECTED]> > Subject: Re: building LFS > To: LFS Support List <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="iso-8859-1" > > Am Donnerstag, 6. Dezember 2007 01:59 schrieb Randy McMurchy: > >> Dan Nicholson wrote these words on 12/05/07 18:42 CST: >> >>> That's a pretty good idea. It also might be nice if we placed a >>> pointer back to the introduction text before the first package >>> (binutils-pass1) since most people probably skim that section (or skip >>> it entirely) and miss a crucial piece of information. >>> >> Well, I suppose it couldn't hurt, but if someone is such a newbie >> that they don't know to unpack sources and cd into the working >> directory because they didn't bother reading the preface material, >> what makes you think they'll read anything but the actual commands? >> > > Well, most time one isn't studying the book line by line but using it just > for > searching. Not to wast too much time. And sometimes one can't do the > building in one time. So, if you don't read about cd-ing, not to do it might > happen =8O > > >> They're going to blindly subscribe >> to the mailing list and ask for help (probably without even consulting >> the faq). >> > > Right. > But! If the question is asked again and again? Isn't that a hint for > improvement? > > >> Just my thoughts. >> > > And mine added :-) > :wq > > > ------------------------------ > > Message: 6 > Date: Thu, 06 Dec 2007 13:46:06 +0000 > From: martin welsh <[EMAIL PROTECTED]> > Subject: Dyslexia - or worse. > To: [email protected] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > I am fumbling through and have now got to chapter 7 but not without some > bother with the instructions. > Early on you are told that you start by building the tools chain and > should start from $LFS/tools. > Next - mkdir build file > next - cd build file ok so far. > Then unpack source (to be built file) in build file. Still ok. > Next - possibly a preamble but more to the point ../configure 'the file > being built' possibly with qualifiers. > > This is not ok because ../configure needs to be ./configure. > > Again the way that patches work for me is that you put the patch in the > folder to be patched and then go for the patch instruction. > Ch 5.9.1Expect - excuse the pun. > > I am in $LFS/tools/expect(unpacked) and I have copied the patch into > expect(unpacked). > Next patch -Np1 -i ../expect............... > > This is not ok because again ../expect..... should be ./expect....... > > The same hiccup but a different flavour. > > As I have gone through the book I have tried to think of an elegant > solution which will ensure that future readers do not make the mistakes > that I have. > > The only solution I have thought of is to precede each chapter, the bit > where the user starts typing, with a simple statement saying what > folders should be where. > > > Perhaps $LFS/tools then mkdir -v build-folder > Unpack in $LFS/tools/build-folder > > It is a very good teacher that can place the words so that everybody > receives the same message. > It is a genius who does it for dyslexics. > > martin welsh > > > ------------------------------ > > Message: 7 > Date: Thu, 06 Dec 2007 08:47:29 -0600 > From: Randy McMurchy <[EMAIL PROTECTED]> > Subject: Re: building LFS > To: LFS Support List <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1 > > Matthias Feichtinger wrote these words on 12/06/07 04:42 CST: > >> Right. >> But! If the question is asked again and again? Isn't that a hint for >> improvement? >> > > As I answered before, "I suppose". It just seems weird to redundantly > give information out because we feel that folks won't read the book, > so the information needs to be repeated over and over. However, in > retrospect since so many have chimed in, it does indeed seem to be > a popular idea, that really doesn't hurt a thing. > > > >>> Just my thoughts. >>> >> And mine added :-) >> > > It is refreshing to see so many provide input about something on > one of the mailing lists. I hope this trend continues. And since > the consensus says that an additional note wouldn't hurt because > at one time or another most everyone has made the same mistake, > it now appears that we should do it. > > I'll create a ticket... Done! > > -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
