Re: Making a Rescue cdrom
brown wrap wrote:
In 8.4.1 there is a procedure to build a rescue floppy. The procedure
uses grub-mkrescue which would support a cdrom if genisoimage. Has
anyone figured out a way to make a rescue cdrom?
I download a copy of KNOPPIX and burn a disc. I also like sysrecuecd.
Mike
--
p=p=%c%s%c;main(){printf(p,34,p,34);};main(){printf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This message made from 100% recycled bits.
You have found the bank of Larn.
I speak only for myself, and I am unanimous in that!
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: lose data on shutdown?
Kyle Rush wrote:
I have a livecd 6.3 and book 6.3. the computer I am installing it on is
somewhat old, and thus 1 SBU = about one hour. I can't figure out how to
shut down the machine without losing everything i was working on. I do not
know if this was covered in the book; i don't think it was. if i am wrong,
say so and i will go back to reading the book. please help.
There is a hint written about that. I used the same CD-ROM you
are using to build 6.5 successfully a couple of times.
I don't recall the entire URL, but I have a copy of that, and
the file name is
stages-stop-and-resume.txt
I'm sure if you look in the hints section of the web site you
can find it. If you have troubles, then I can shoot you a copy
via separate e-mail.
First, you can't really just shutdown whenever you like. You
have to let any given build complete. You don't have to do
an install, however.
Second, when all activity has stopped, and a build has successfully
completed, you certainly can shut down. I *highly* recommend that
you write down exactly what you were doing, and what the next step
needs to be, on a piece of paper, and conserve it with the machine
where it will not get lost, or put it into a text file on the
file system you need to mount. It's surprising how long you can
put a build aside, thinking you'll be back at it next day, and
then find out two weeks later, when you finally get back to it,
that you can't remember just where you were.
Third, in order to restart, you have to do some maintenance stuff.
You have to mount your partitions, and set up some shell variables,
like $LFS. This initial setup can be put into a little shell script
in the top level of your mounted build file system. Later, you'll
want to add another to enter the chroot environment, and then another
which can be run inside the chroot to set up what you need. The
scripts are not necessary, but are very helpful.
That said, it is easier not to have to reboot, if you can avoid it.
Mike
--
p=p=%c%s%c;main(){printf(p,34,p,34);};main(){printf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This message made from 100% recycled bits.
You have found the bank of Larn.
I speak only for myself, and I am unanimous in that!
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: lose data on shutdown?
On Fri, February 12, 2010 4:48 am, Mike McCarty wrote:
Kyle Rush wrote:
I have a livecd 6.3 and book 6.3. the computer I am installing it on is
somewhat old, and thus 1 SBU = about one hour. I can't figure out how to
shut down the machine without losing everything i was working on. I do
not
know if this was covered in the book; i don't think it was. if i am
wrong,
say so and i will go back to reading the book. please help.
There is a hint written about that. I used the same CD-ROM you
are using to build 6.5 successfully a couple of times.
I don't recall the entire URL, but I have a copy of that, and
the file name is
stages-stop-and-resume.txt
I'm sure if you look in the hints section of the web site you
can find it. If you have troubles, then I can shoot you a copy
via separate e-mail.
First, you can't really just shutdown whenever you like. You
have to let any given build complete. You don't have to do
an install, however.
Second, when all activity has stopped, and a build has successfully
completed, you certainly can shut down. I *highly* recommend that
you write down exactly what you were doing, and what the next step
needs to be, on a piece of paper, and conserve it with the machine
where it will not get lost, or put it into a text file on the
file system you need to mount. It's surprising how long you can
put a build aside, thinking you'll be back at it next day, and
then find out two weeks later, when you finally get back to it,
that you can't remember just where you were.
Third, in order to restart, you have to do some maintenance stuff.
You have to mount your partitions, and set up some shell variables,
like $LFS. This initial setup can be put into a little shell script
in the top level of your mounted build file system. Later, you'll
want to add another to enter the chroot environment, and then another
which can be run inside the chroot to set up what you need. The
scripts are not necessary, but are very helpful.
That said, it is easier not to have to reboot, if you can avoid it.
Mike
--
p=p=%c%s%c;main(){printf(p,34,p,34);};main(){printf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This message made from 100% recycled bits.
You have found the bank of Larn.
I speak only for myself, and I am unanimous in that!
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
OK thanks, but I'm losing EVERYthing. not just partitions, but everything.
users, files, builds...when i restart, it's just what's on the livecd.
NOTHING else. am i doing someting wrong?
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: lose data on shutdown?
On 12/02/10 12:14, Kyle Rush wrote: I have a livecd 6.3 and book 6.3. the computer I am installing it on is somewhat old, and thus 1 SBU = about one hour. I can't figure out how to shut down the machine without losing everything i was working on. If you've made a partition on your hard drive to work on then when you unmount it all that you've compiled will be saved there. The problem is when you resume work you need to make sure things are set up properly. In chapter 5 that just means su - lfs but in chapter 6 you need to make sure that you've mounted /proc, /sys and /dev Andy -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: lose data on shutdown?
On Fri, February 12, 2010 5:15 am, Andrew Benton wrote: On 12/02/10 12:14, Kyle Rush wrote: I have a livecd 6.3 and book 6.3. the computer I am installing it on is somewhat old, and thus 1 SBU = about one hour. I can't figure out how to shut down the machine without losing everything i was working on. If you've made a partition on your hard drive to work on then when you unmount it all that you've compiled will be saved there. The problem is when you resume work you need to make sure things are set up properly. In chapter 5 that just means su - lfs but in chapter 6 you need to make sure that you've mounted /proc, /sys and /dev that's the problem. I'm in chap.5 and su - lfs doesn't work. says error:user does not exist. I have set up the user lfs as instructed. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: lose data on shutdown?
On Fri, 12 Feb 2010 13:14:37 +0100, Kyle Rush k...@cyber-rush.org wrote: I have a livecd 6.3 and book 6.3. the computer I am installing it on is somewhat old, and thus 1 SBU = about one hour. I can't figure out how to shut down the machine without losing everything i was working on. I do not know if this was covered in the book; i don't think it was. if i am wrong, say so and i will go back to reading the book. please help. If I understand you right, you want to shutdown the computer while installing LFS and resume the installation later? There is a hint for this here: http://www.linuxfromscratch.org/hints/downloads/files/stages-stop-and-resume.txt It is kind of old, but the basics should still apply for newer versions of the book. However, I have lost track of all the changes that were made in the past months, so I would not entirely rely on the information. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: saving info on livecd?
On Fri, Feb 12, 2010 at 6:19 AM, Mike McCarty mike.mcca...@sbcglobal.net wrote: Jordan Peters wrote: i'm using the ubuntu linux livecd to make my 6.5 lfs install and i'm wondering how to save the variables and such i make during the book. like is there a way to save the info created during section 4.4 while setting up .bash_profile and .bashrc and save the lfs user in the end of 4.3? You got two pretty good replies, neither of which described what I used for that. I did basically the same thing you are, but with the LFS 6.3 LiveCD. However, I used another technique. I wrote a little script file which I put into the topmost level of the new file system, which did all the setup. Later, when I needed it, I wrote another which also reentered the chroot environment. Both of your scripts could be figured out. The second one probably a lot easier and faster then the first, but would you be willing to share the details of those scripts especially the first one? Like maybe post it some where so any one that wants to take a look can. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Booting problems
brown wrap wrote: I finshed compiling everything but can't boot. Here's my problem. I have two internal disks and one external: /dev/sda /dev/sdb /dev/sdc In reading the book, it said to set aside a partition for LFS. I did, it was the 2nd partition of sdc, sdc2 So as one of my last steps I set up grub, but it was installed on sdc2. I then realized it was the new grub, or grub2. I tried to modify my existing grub, the old grub, to add a new entry. I was able to select the new entry, but not boot. So here is my question. If I move the external drive inside and make it the first drive, will I be able to boot, even though LFS is on the 2nd partiton? I don't want to, but I could move everyting over to the first partition, but I'd have to wipe it out, which I don't want to do. I thought as I was going through the book, this would be a problem since I never encountered a warning that it had to be on the first partition. Did you follow the instructions and boot GRUB2 from GRUB Legacy to test it out before updating the MBR? -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Booting problems
Did you follow the instructions and boot GRUB2 from GRUB Legacy to test it out before updating the MBR? -- Bruce I must have missed them. I will go back and look. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Booting problems
On 12/02/10 17:07, brown wrap wrote: I finshed compiling everything but can't boot. Here's my problem. I have two internal disks and one external: /dev/sda /dev/sdb /dev/sdc In reading the book, it said to set aside a partition for LFS. I did, it was the 2nd partition of sdc, sdc2 So as one of my last steps I set up grub, but it was installed on sdc2. I then realized it was the new grub, or grub2. I tried to modify my existing grub, the old grub, to add a new entry. I was able to select the new entry, but not boot. So what was the error? Was this second entry to try to boot grub2 on sdc2? Did grub2 load or did it quit with an error? Did grub2 fail to boot the kernel? Andy -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: lose data on shutdown?
Kyle Rush wrote:
On Fri, February 12, 2010 4:48 am, Mike McCarty wrote:
[get]
stages-stop-and-resume.txt
I'm sure if you look in the hints section of the web site you
can find it. If you have troubles, then I can shoot you a copy
via separate e-mail.
[...]
OK thanks, but I'm losing EVERYthing. not just partitions, but everything.
users, files, builds...when i restart, it's just what's on the livecd.
NOTHING else. am i doing someting wrong?
If you're following the book properly, you are losing nothing.
You do have to go through the setup again, and remount your
file system(s). Are you pretty much UNIX savvy, and understand
the concept of a mount and what it does?
Mike
--
p=p=%c%s%c;main(){printf(p,34,p,34);};main(){printf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This message made from 100% recycled bits.
You have found the bank of Larn.
I speak only for myself, and I am unanimous in that!
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: saving info on livecd?
stosss wrote:
Both of your scripts could be figured out. The second one probably a
lot easier and faster then the first, but would you be willing to
share the details of those scripts especially the first one? Like
maybe post it some where so any one that wants to take a look can.
Well, during the initial setup, you have to be able to do a few
things completely manually, unless you put them on a floppy, I
guess. I don't have easy access at the moment. Really, they were
only about five or ten lines each. The next time I fire up the
machine they are on, I'll copy them out and shoot them to you.
Mike
--
p=p=%c%s%c;main(){printf(p,34,p,34);};main(){printf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This message made from 100% recycled bits.
You have found the bank of Larn.
I speak only for myself, and I am unanimous in that!
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: Booting problems
brown wrap wrote: So what was the error? Was this second entry to try to boot grub2 on sdc2? Did grub2 load or did it quit with an error? Did grub2 fail to boot the kernel? Andy -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page The first time I tried to modify the old grub.conf, I just add the lines created by the new grub.cfg, must made them adhere to the format used in grub.conf. That attempted boot, resulted in no such partition. So I changed the grub.conf to: title GNU/Linux, with Linux 2.6.32.7-lfs-6.6-rc1 root (hd2,1) kernel /vmlinux-2.6.32.7-lfs-6.6-rc1 root=/dev/sdc2 That just brought up an empty menu with no selection at all. Because the syntax is wrong. See the example in the book. Also, the kernel line is probably wrong if you didn't set up a separate /boot partition. It's really hard maintain patience when users ask questions without trying to do some research, like reading the book, on their own. It's also hard to help when the information supplied is basically It doesn't work with virtually no details. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Booting problems
On Fri, Feb 12, 2010 at 2:08 PM, brown wrap gra...@yahoo.com wrote: The first time I tried to modify the old grub.conf, I just add the lines created by the new grub.cfg, must made them adhere to the format used in grub.conf. That attempted boot, resulted in no such partition. So I changed the grub.conf to: title GNU/Linux, with Linux 2.6.32.7-lfs-6.6-rc1 root (hd2,1) kernel /vmlinux-2.6.32.7-lfs-6.6-rc1 root=/dev/sdc2 That just brought up an empty menu with no selection at all. Did you read this in the book: GRUB uses its own naming structure for drives and partitions in the form of (hdn,m), where n is the hard drive number and m is the partition number, both starting from zero. For example, partition hda1 is (hd0,0) to GRUB and hdb3 is (hd1,2). In contrast to Linux, GRUB does not consider CD-ROM drives to be hard drives. For example, if using a CD on hdb and a second hard drive on hdc, that second hard drive would still be (hd1). -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Openssh chapter 19
On Fri, Feb 12, 2010 at 2:31 PM, Mike McCarty mike.mcca...@sbcglobal.net wrote: stosss wrote: svn-20100203 from the 02-10-2010 archive The last sentence in the paragraph between make and make test. _To run the test suite, first copy the scp program to /usr/bin, making sure that you back up any existing copy first._ This is probably enough for some one who has done this before and knows what to look for and where to look and understands the risk of why to back up any existing copy. Not complaining, just pointing out what is probably obvious. :) With a fresh LFS install with only the minimal BLFS stuff done, like reading through chapter 1, 2 and doing chapter 3 and openssl in chapter 4 and the only other things being GPM and WGET installed, there probably isn't any existing copy of scp. Once I have run make, where will the scp program be? Would the make install move it to the replace? That depends upon how you configure your build. I suggest you read the section in the book The /usr Versus /usr/local Debate I don't understand what the sentence is saying. How is reading the /usr VS /usr/local debate again going to help me? Not complaining just suggesting, It would be nice if there was more information then just that sentence. :) It's in the book. What is in the book and where? Any volunteers willing to help make that sentence a little clearer? Hopefully, that did. It's under your control, so nobody here can tell you where you put it. Yes I know I am in control of what I do to and how I do my system. But no I am sorry your reply is no help. Apparently you understand what the sentence says. I don't so your suggestions are completely meaningless to me. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Booting problems
Because the syntax is wrong. See the example in the book. Also, the kernel line is probably wrong if you didn't set up a separate /boot partition. It's really hard maintain patience when users ask questions without trying to do some research, like reading the book, on their own. It's also hard to help when the information supplied is basically It doesn't work with virtually no details. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page If you don't want to answer a question, simply ignore it. I read the book and was replying to someone who asked what was the error. I supplied information the first time I asked the question. When I supply to much I hear 'trim you entries'. As far as supplying the details, read the book contains no details at all. The syntax is wrong, contains no details as well. You don't need any patience, if you don't like the question, just delete it. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Booting problems
Because the syntax is wrong. See the example in the book. Also, the kernel line is probably wrong if you didn't set up a separate /boot partition. It's really hard maintain patience when users ask questions without trying to do some research, like reading the book, on their own. It's also hard to help when the information supplied is basically It doesn't work with virtually no details. If you don't want to answer a question, simply ignore it. I read the book and was replying to someone who asked what was the error. I supplied information the first time I asked the question. When I supply to much I hear 'trim you entries'. No one will complain if you give verbose information as it relates to the problem. What we don't like is when you leave all the quoted junk that is no relevant to the on going conversation. As for the way you ask your questions and the information you give initially and even when asked for more, you don't give enough, you make it appear as though you either did not read the book or you cherry picked what you wanted to read. If you deviate from the book and don't say so or tell how you deviated no can help you. As far as supplying the details, read the book contains no details at all. The syntax is wrong, contains no details as well. You don't need any patience, if you don't like the question, just delete it. When people respond like this it is because they are pissed off and don't like what the poster said. You really should be careful how you respond to some one who knows this stuff like the back of their hand and who is directly responsible for what is in the book. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Booting problems
Did you read this in the book: GRUB uses its own naming structure for drives and partitions in the form of (hdn,m), where n is the hard drive number and m is the partition number, both starting from zero. For example, partition hda1 is (hd0,0) to GRUB and hdb3 is (hd1,2). In contrast to Linux, GRUB does not consider CD-ROM drives to be hard drives. For example, if using a CD on hdb and a second hard drive on hdc, that second hard drive would still be (hd1). Yes, sorry I screwed that up. I had even ran the command: grub-mkdevicemap --device-map=device.map Which yielded: (hd0) /dev/sda (hd1) /dev/sdb (hd2) /dev/sdc (hd3) /dev/sdh Thank you, I missed that. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Booting problems
brown wrap wrote:
Did you read this in the book:
[...]
Thank you, I missed that.
First step when having a problem is re read the relevant section,
slowly, carefully, and look for typos, mistakes, spelling errors,
etc.
Mike
--
p=p=%c%s%c;main(){printf(p,34,p,34);};main(){printf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This message made from 100% recycled bits.
You have found the bank of Larn.
I speak only for myself, and I am unanimous in that!
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: Openssh chapter 19
On Fri, Feb 12, 2010 at 3:14 PM, Mike McCarty mike.mcca...@sbcglobal.net wrote: stosss wrote: [where's my stuff?] On Fri, Feb 12, 2010 at 2:31 PM, Mike McCarty mike.mcca...@sbcglobal.net wrote: [...] That depends upon how you configure your build. I suggest you read the section in the book The /usr Versus /usr/local Debate I don't understand what the sentence is saying. How is reading the /usr VS /usr/local debate again going to help me? If you read it, you'd understand better why you'd understand. For example, this sentence from the book might help ) What is the BLFS position on this? ) ) All of the BLFS instructions install programs in /usr with optional ) instructions to install into /opt for some specific packages. That sentence, along with the information pertaining to the exact package, and the actions you took when you built should tell you where to look. I see where the problem is now. I understand the /usr - /usr/local I use /usr for everything. During the build process executable binaries should go in /usr/bin. The sentence says copy it there. If it is not there already then where is it? Does it not get put there until make install? Because the same paragraph says it needs to be there before running make test, which is done before make install. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[no subject]
I am working from book 6.5 I am up to the stage of building Glibc from within the system proper, chap ter 6 section 9.1 This command: DL=3D$(readelf -l /bin/sh | sed -n 's...@.*interpret.*/tools\(.*\)]...@\1@p') produces the following output: bash: command substitution: line 35: syntax error near unexpected token `) ' bash: command substitution: line 35: `readelf -l /bin/sh | sed -n 's...@.*int erpret.*/tools\(.*\)]...@\1@p')' Any ideas? -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re:
bchaf...@programmer.net wrote: I am working from book 6.5 I am up to the stage of building Glibc from within the system proper, chap ter 6 section 9.1 This command: DL=3D$(readelf -l /bin/sh | sed -n 's...@.*interpret.*/tools\(.*\)]...@\1@p') ^^ Extra characters. produces the following output: bash: command substitution: line 35: syntax error near unexpected token `) ' bash: command substitution: line 35: `readelf -l /bin/sh | sed -n 's...@.*int erpret.*/tools\(.*\)]...@\1@p')' Whenever you get this type of error, try to break it down: readelf -l /bin/sh readelf -l /bin/sh | sed -n 's...@.*interpret.*/tools\(.*\)]...@\1@p' See if those work. Then go back and analyze the original line didn't work. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Booting problems
linux fan wrote:
On 2/12/10, brown wrap gra...@yahoo.com wrote:
So I changed the grub.conf to:
title GNU/Linux, with Linux 2.6.32.7-lfs-6.6-rc1
root (hd2,1)
kernel /vmlinux-2.6.32.7-lfs-6.6-rc1 root=/dev/sdc2
I think Grub2 wants it to say:
root (hd2,2)
linux /vmlinux-2.6.32.7-lfs-6.6-rc1 root=/dev/sdc2
for the second partition on the third drive,
and I think they changed 'kernel' to 'linux'
Sigh.
That may or may not be the problem.
1. The syntax is:
menuentry GNU/Linux, Linux 2.6.30.2-lfs65 {
insmod ext2
set root=(hd0,2)
linux /boot/vmlinux-2.6.32.7-lfs-SVN-201002011 root=/dev/sda2 ro
}
Note the quotes around the title. Note the braces. Is that so hard?
2. The command is 'set root', not 'root'. The 'set root' command points
to the drive where GRUB should look for the kernel. If it's a
dedicated partition, the linux line should not have /boot because the
partition is mounted *after booting* at /boot.
If its not a dedicated partition, it should be /boot/vmlinux...
That may not be so obvious, but it is explained in the book.
3. Is the kernel name really 'vmlinux...' That depends on what the
user did after the kernel build. We don't know from what has been
posted. What is the output from `ls /boot`
4. What is the filesystem for /dev/sdc2? That is, from the host
system, what is the result of `blkid | grep /dev/sdc2`?
5. What was the full grub.cfg file?
6. Was the test procedure in the book run? At a minimum GRUB2 should
have come up and offered the user a chance to go to the command prompt.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: Booting problems again
brown wrap wrote: Let me start over and maybe I can make things clear. I built the LFS using Centos 5.4, running with the old GRUB. Here is my system layout: /dev/sda has Centos with its swap being the 2nd partiton. /dev/sdb I use to download files and store things. /dev/sdc is two partitions, sdc1 and sdc2 I've seen some people try to do this with LVM. That requires an initrd and is not directly supported in LFS. That's why I asked for the partition type. In reading the book, it said to set aside a partiton for LFS, that was /dev/sdc2 That should be OK, but if its a very large drive, there are some problems, especially by GRUB Legacy, starting deep into the drive. I built it, step-by-step, and didn't realize until it was built that there was a new GRUB. So I followed the instruction for the new GRUB, but of course that was installed on /dev/sdc2. That's OK. So When I boot up, its using the legacy GRUB And the book tells you how to test GRUB2 starting from GRUB Legacy. Go to GRUB Lgacy's command line and: grub root (hd2,1) grub kernel /boot/grub/core.img grub boot Not that this is GRUB Legacy syntax. GRUB2's configuration should come up. Alternatively, change the kernel line to boot lfs directly. and I tried to modify that so it would see the 3rd drive and its 2nd partition, sdc2. Why didn't you try using grub's command line? You mentioned grub.cfg. GRUB Legacy uses menu.lst. At this point I could remove sda and put sdc in its place, but LFS would still be on the 2nd partition, but I hope to avoid this. It's probably OK as is. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re:
Bruce Dubbs wrote:
bchaf...@programmer.net wrote:
I am working from book 6.5
I am up to the stage of building Glibc from within the system proper,
chap
ter 6 section 9.1
This command:
DL=3D$(readelf -l /bin/sh | sed -n
's...@.*interpret.*/tools\(.*\)]...@\1@p')
^^
Extra characters.
Possibly not. It's possible (likely) that this is an encoded =.
=xx
is used to encode the 8 bit character with hex code xx.
Since 0x3D is the code for =, then =3D is the code
for =. These substitutions are sometimes made by mailers
or even by machines in between.
Mike
--
p=p=%c%s%c;main(){printf(p,34,p,34);};main(){printf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This message made from 100% recycled bits.
You have found the bank of Larn.
I speak only for myself, and I am unanimous in that!
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: lose data on shutdown?
On Fri, 12 Feb 2010 05:22:24 -0800 Kyle Rush k...@cyber-rush.org wrote: On Fri, February 12, 2010 5:15 am, Andrew Benton wrote: On 12/02/10 12:14, Kyle Rush wrote: I have a livecd 6.3 and book 6.3. the computer I am installing it on is somewhat old, and thus 1 SBU = about one hour. I can't figure out how to shut down the machine without losing everything i was working on. If you've made a partition on your hard drive to work on then when you unmount it all that you've compiled will be saved there. The problem is when you resume work you need to make sure things are set up properly. In chapter 5 that just means su - lfs but in chapter 6 you need to make sure that you've mounted /proc, /sys and /dev that's the problem. I'm in chap.5 and su - lfs doesn't work. says error:user does not exist. I have set up the user lfs as instructed. Have you set it up after resuming? As I have understood it, you booted the livecd, made the preparations, built, stoped, rebooted (or whatev) and now you can't resume. It's simple - the root filesystem of the livecd lives in RAM and goes away with the power. What's on the HDD (/mnt/lfs) does not, ofcourse. So, when you boot the livecd, make a new user and build, then all that happens above /mnt/lfs is volatile. Upon rebooting, you just have to redo ALL the enviroment setting-up. Mike and others have already explained the details. The scripts they mention should be put somewhere under /mnt/lfs, so that they themselves are not in volatile memmory. Upon rebooting, run them. But make sure you do it properly - if your script is like this: # Begin my_script.sh export LFS=/mnt/lfs export FOO=blabla Then simle `bash my_script.sh' won't help becouse the bash you just ordered will fork a totally new process which will run my_script.sh, set its own enviroment and then die. You should do: `source my_script.sh'. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Booting problems again
A little more. I didn't list the size of the disks because I didn't think it was important, but since the legacy GRUB may not be able to handle them: sda is small, I am not at the machine until Sunday or Monday. sdb is one TB that I just store stuff on. sdc is the disk with LFS on it. It is 1.5 TB. I partitioned it right down the middle and LFS is on the 2nd partition /dev/sdc2. I wasn't aware that the old grub, the only grub I knew about up to now, had problems with large disks. but then again, all of the system I've set up had small boot disks. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Booting problems again
brown wrap wrote: A little more. I didn't list the size of the disks because I didn't think it was important, but since the legacy GRUB may not be able to handle them: sda is small, I am not at the machine until Sunday or Monday. sdb is one TB that I just store stuff on. sdc is the disk with LFS on it. It is 1.5 TB. I partitioned it right down the middle and LFS is on the 2nd partition /dev/sdc2. I wasn't aware that the old grub, the only grub I knew about up to now, had problems with large disks. but then again, all of the system I've set up had small boot disks. That may be a problem for GRUB Legacy. I'm not sure. GRUB2 can handle it though. IMO, 750G is way too big for an LFS partition. I store my BLFS sources on /usr/src which is a separate partition (50G, 50% full) and of course /home and /boot (100M) are separate so I can share them across multiple builds. Some people have /tmp and /opt as separate partitions too. I've been using the same main system since 2005. I have my LFS partition 8G (70% full) and really haven't had much problem with that. It does have most of BLFS built, but most of the bigger packages (kde, qt, mysql, gnome, etc) go on /opt (20G, 40% full). Multiple partitions give a lot more flexibility. I make my newer LFS partitions 10G. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Booting problems again
On Fri, 2010-02-12 at 20:48 -0600, Bruce Dubbs wrote: IMO, 750G is way too big for an LFS partition. Well, not *too* big, in the sense of causing problems. Unnecessarily big might be a better wording, and I'd agree. Separating data from applications is practically a necessity when it comes to upgrading / reinstalling things in future, and 20Gb is more than enough for applications. Simon. signature.asc Description: This is a digitally signed message part -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Booting problems again
I wanted to install LFS on a fresh partition and this was the only unused SATA drive I had. I had small IDE drives, but this computer doesn't have an IDE interface. And when it comes to cost now $40 gets you double this size. I could repartition the drive, but I am trying to avoid it. I installed a ZFS filesystem on the first partition and I'd hate to get rid of it, but I can. Anyway, I can't do anything with it right now. I'm not near the machine. --- On Fri, 2/12/10, Simon Geard delga...@ihug.co.nz wrote: From: Simon Geard delga...@ihug.co.nz Subject: Re: Booting problems again To: lfs-support@linuxfromscratch.org Date: Friday, February 12, 2010, 7:32 PM On Fri, 2010-02-12 at 20:48 -0600, Bruce Dubbs wrote: IMO, 750G is way too big for an LFS partition. Well, not *too* big, in the sense of causing problems. Unnecessarily big might be a better wording, and I'd agree. Separating data from applications is practically a necessity when it comes to upgrading / reinstalling things in future, and 20Gb is more than enough for applications. Simon. -Inline Attachment Follows- -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Booting problems again
brown wrap wrote: I wanted to install LFS on a fresh partition and this was the only unused SATA drive I had. I had small IDE drives, but this computer doesn't have an IDE interface. And when it comes to cost now $40 gets you double this size. I could repartition the drive, but I am trying to avoid it. I installed a ZFS filesystem on the first partition and I'd hate to get rid of it, but I can. I wasn't suggesting changing your drives, but I would suggest rethinking your partitioning. I don't know how much data you have on your zfs partition, but I'd suggest tarring up the LFS partition to another location and resize the lfs partition. Anyway, I can't do anything with it right now. I'm not near the machine. At this point, these are just suggestions. It is your system and you can do whatever you want. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Booting problems
brown wrap schrieb: [...] So here is my question. If I move the external drive inside and make it the first drive, will I be able to boot, even though LFS is on the 2nd partiton? I don't want to, but I could move everyting over to the first partition, but I'd have to wipe it out, which I don't want to do. First of all, does your machine support booting from an external device? I tried booting from an external USB HDD, and failed miserably although the mainboard claimed to support that. To have clarity here, test booting with something on external drive which usually boots. I have a working installation on a second _internal_ disk, but I didn't reinstall the bootloader on first disk. Instead I followed the instructions at http://www.linuxfromscratch.org/lfs/view/stable/chapter08/grub.html in the Warning box, and linked the boot entry via chainloader. The only minor obstacle for me was the broken naming: my disks were called sda and hda instead of sda and sdb, due to a legacy driver for my internal Promise TX133 PATA controller. When installing grub on sdb2 (in my case) on the host system, it wrote sdb2 to /boot/grub/menu.lst, but when booting the device should have been hda2. Can be fixed easily, because you can enter the grub shell on boot and then use setup (hdTAB) to see what devices are there. Then edit the entry appropriately and have fun. Cheers, Jan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
