Re: with new system, how to run a test boot?
Bruce Dubbs wrote: Justin P. Mattock wrote: I like that idea, so you would have let's say 3 or 4 100mb test runs setup for multi booting. I like to use 10GB for the systems. 100MB is way too small. USe the 100MB partition for /boot as you have below. so a simple scheme would be like this: (using the system I have now I would do:) /dev/sda1 /boot(containing grub) /dev/sda2/ext3 (containing a x86_32 system) /dev/sda4/ext4 ( containing a x86_64 system). /dev/sda* Seems better to do a scheme like that. I thought I said that. However sda4 should be an extended partition so you can have logical partitions too. Also you may want a swap partition that can be shared by every system too. -- Bruce Yeah you did say that, I ended up writing what I was thinking.. and not thinking as I was sending. Aside from that 10G is probably more than enough. Justin P. Mattock -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
RE: with new system, how to run a test boot?
You can't boot into a sub-directory of a file system but you could do the following 1) Configure grub to boot the kernel in the /mnt/lfs directory with the current root file system as a the root directory 2) Boot grub and pass the command init=/mnt/lfs/bin/sh this will run the LFS bash shell instead of the current/host init. 3) Once the kernel has booted and you are dropped into the shell run; exec chroot /mnt/lfs exec /sbin/init. This will chroot into the /mnt/lfs system and start init as if the kernel started it at boot. NOTE: the exec is important because init -MUST- be run as PID 1. Russ Date: Sun, 16 Aug 2009 21:37:05 -0700 From: justinmatt...@gmail.com To: lfs-support@linuxfromscratch.org Subject: with new system, how to run a test boot? quick question, with a new fresh system in the /where directory is there a way to adjust grub on the host system to actually boot the new system, before moving the newly created system to / Justin P. Mattock -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page _ Use Windows Live Messenger from your Hotmail inbox Web IM has arrived! http://windowslive.ninemsn.com.au/article.aspx?id=823454-- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: with new system, how to run a test boot?
Nice, so it is possible to do this. I'll give this a try. Russell Stockhammer wrote: You can't boot into a sub-directory of a file system but you could do the following 1) Configure grub to boot the kernel in the /mnt/lfs directory with the current root file system as a the root directory 2) Boot grub and pass the command init=/mnt/lfs/bin/sh this will run the LFS bash shell instead of the current/host init. 3) Once the kernel has booted and you are dropped into the shell run; exec chroot /mnt/lfs exec /sbin/init. This will chroot into the /mnt/lfs system and start init as if the kernel started it at boot. NOTE: the exec is important because init -MUST- be run as PID 1. Russ Date: Sun, 16 Aug 2009 21:37:05 -0700 From: justinmatt...@gmail.com To: lfs-support@linuxfromscratch.org Subject: with new system, how to run a test boot? quick question, with a new fresh system in the /where directory is there a way to adjust grub on the host system to actually boot the new system, before moving the newly created system to / Justin P. Mattock -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page Web IM has arrived! Use Windows Live Messenger from your Hotmail inbox http://windowslive.ninemsn.com.au/article.aspx?id=823454 -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: with new system, how to run a test boot?
There's an LFS hint describing how to boot LFS without requiring a separate partition (i.e., in the same file system as another operating system). The trick is a special pre-init program that does a chroot early in the boot process (automatically, rather than manually as Russell Stockhammer suggests). See http://www.linuxfromscratch.org/hints/downloads/files/lfs_next_to_existing_systems.txt -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: with new system, how to run a test boot?
cool, thanks for the info. I'll have a look and see if I can do this. Robert A. Lerche wrote: There's an LFS hint describing how to boot LFS without requiring a separate partition (i.e., in the same file system as another operating system). The trick is a special pre-init program that does a chroot early in the boot process (automatically, rather than manually as Russell Stockhammer suggests). See http://www.linuxfromscratch.org/hints/downloads/files/lfs_next_to_existing_systems.txt -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: with new system, how to run a test boot?
On Monday 17 August 2009 15:15:39 Russell Stockhammer wrote: You can't boot into a sub-directory of a file system but you could do the following 1) Configure grub to boot the kernel in the /mnt/lfs directory with the current root file system as a the root directory 2) Boot grub and pass the command init=/mnt/lfs/bin/sh this will run the LFS bash shell instead of the current/host init. 3) Once the kernel has booted and you are dropped into the shell run; exec chroot /mnt/lfs exec /sbin/init. This will chroot into the /mnt/lfs system and start init as if the kernel started it at boot. NOTE: the exec is important because init -MUST- be run as PID 1. You can create a stub executable placed in anywhere: exec chroot /mnt/lfs exec /sbin/init save it and pass it to the init parameter at the kernel 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: with new system, how to run a test boot?
Michael Tsang wrote: On Monday 17 August 2009 15:15:39 Russell Stockhammer wrote: You can't boot into a sub-directory of a file system but you could do the following 1) Configure grub to boot the kernel in the /mnt/lfs directory with the current root file system as a the root directory 2) Boot grub and pass the command init=/mnt/lfs/bin/sh this will run the LFS bash shell instead of the current/host init. 3) Once the kernel has booted and you are dropped into the shell run; exec chroot /mnt/lfs exec /sbin/init. This will chroot into the /mnt/lfs system and start init as if the kernel started it at boot. NOTE: the exec is important because init -MUST- be run as PID 1. You can create a stub executable placed in anywhere: exec chroot /mnt/lfs exec /sbin/init save it and pass it to the init parameter at the kernel Cool. at the moment I never had a chance to try any of these procedures out.(don't worry I will) seems 2.6.31-rc6 is stuck during boot, spent most of the day trying to locate the commit that causes this stuckage. (seems to only affect x86_64, as my other system boots fine). Justin P. Mattock -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
with new system, how to run a test boot?
quick question, with a new fresh system in the /where directory is there a way to adjust grub on the host system to actually boot the new system, before moving the newly created system to / Justin P. Mattock -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: with new system, how to run a test boot?
Justin P. Mattock wrote: quick question, with a new fresh system in the /where directory is there a way to adjust grub on the host system to actually boot the new system, before moving the newly created system to / You don't give particulars but if you built on a separate partition, than you just set up that partition as root: title LFS 6.5 root (hd0,4) kernel /boot/linux-2.6.30.2 root=/dev/sda5 Personally, I like to set up a separate 100MB partition that is mounted as /boot and then all my builds put the kernels in the same place. Then the grub configuration looks like: itle LFS-dev-2.6.12.5-20051115 root (hd0,2) kernel /linux-2.6.12.5-20071115 root=/dev/sda5 title LFS-dev-2.6.22.5 root (hd0,2) kernel /linux-2.6.22.5 root=/dev/sda6 etc. In this case the /boot partition is sda3. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: with new system, how to run a test boot?
Bruce Dubbs wrote: Justin P. Mattock wrote: quick question, with a new fresh system in the /where directory is there a way to adjust grub on the host system to actually boot the new system, before moving the newly created system to / You don't give particulars but if you built on a separate partition, than you just set up that partition as root: title LFS 6.5 root (hd0,4) kernel /boot/linux-2.6.30.2 root=/dev/sda5 Personally, I like to set up a separate 100MB partition that is mounted as /boot and then all my builds put the kernels in the same place. Then the grub configuration looks like: itle LFS-dev-2.6.12.5-20051115 root (hd0,2) kernel /linux-2.6.12.5-20071115 root=/dev/sda5 title LFS-dev-2.6.22.5 root (hd0,2) kernel /linux-2.6.22.5 root=/dev/sda6 etc. In this case the /boot partition is sda3. -- Bruce I like that idea, so you would have let's say 3 or 4 100mb test runs setup for multi booting. so a simple scheme would be like this: (using the system I have now I would do:) /dev/sda1 /boot(containing grub) /dev/sda2/ext3 (containing a x86_32 system) /dev/sda4/ext4 ( containing a x86_64 system). /dev/sda* Seems better to do a scheme like that. Justin P. Mattock -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: with new system, how to run a test boot?
Justin P. Mattock wrote: I like that idea, so you would have let's say 3 or 4 100mb test runs setup for multi booting. I like to use 10GB for the systems. 100MB is way too small. USe the 100MB partition for /boot as you have below. so a simple scheme would be like this: (using the system I have now I would do:) /dev/sda1 /boot(containing grub) /dev/sda2/ext3 (containing a x86_32 system) /dev/sda4/ext4 ( containing a x86_64 system). /dev/sda* Seems better to do a scheme like that. I thought I said that. However sda4 should be an extended partition so you can have logical partitions too. Also you may want a swap partition that can be shared by every system too. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
