Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've installed a copy of LFS on one of my hard disks partitions. I'd like to make a complete copy of the system to another partition and have done so with the 'cp -axv' command.
However when I reboot into the 'copied' system it halts halfway through booting complaining it is 'unable to open a console'.
Can anyone help me with this?
in general, you cannot copy a whole system using cp or similat commands. For starters, the boot process will not work because the boot loader will not know where to find the startup files. Depending on the configuration, there may also be code in the partition boot sector which does not get copied using cp.
What is on the system besides LFS?
What is the boot loader--eg GRUB, LILO, etc.?
Grub is installed on the MBR. Theres is a copy of GeeXboX and OpenSUSE 10 also on the system and all the kernels are installed into a seperate /boot partition of the hard drive.
I've altered menu.lst to add the relavent changes to include the 'copyed' system and altered the 'root' to point at the new system.
HMMM...
I'm assuming that the system works with strange things like all the kernels in a common /boot partition. (I can't quite picture how GRUB boots into "/boot" and then the system knows which "/" to go to.)
When you say that you altered 'root' to point at the copied system, how does that relate to the statement that all the kernels are in one /boot?
To go further, we should also see the output of "fdisk -l" and the contents of the grub config file: /boot/grub/menu.lst
Alternatively, how about doing all this in more conventional ways---eg make a new partition and install the OS to it.
HMMM...
I'm assuming that the system works with strange things like all the kernels in a common /boot partition. (I can't quite picture how GRUB boots into "/boot" and then the system knows which "/" to go to.)
When you say that you altered 'root' to point at the copied system, how does that relate to the statement that all the kernels are in one /boot?
Grub boot the kernel in the /boot partition and the kernel is told what partition to use for / with the root= option
eg:
Grub boot the kernel in the /boot partition and the kernel is told what partition to use for / with the root= option
eg:
Exactly - anyway the system is definately booting the kernel and trying to use the correct filesystem - it's just as the system starts to come up it's unable to access a console - could this be a /dev issue?
I want to keep the original system as it is - and use the copy as a testing system, but don't really want to have to compile all the packages again a second time just to do so.
It could be, you should check that everything in /dev/is ok & has the correct permissions.
An easier wat to copy the system is to do it from a liveCD because of pseudo file systems, /dev is one that has pseudo files and ones written to the HDD
Eg, I use hda3 for bleeding edge testing, but when nothing is mounted in it there are still files in /dev.
It could be, you should check that everything in /dev/is ok & has the correct permissions.
An easier wat to copy the system is to do it from a liveCD because of pseudo file systems, /dev is one that has pseudo files and ones written to the HDD
Eg, I use hda3 for bleeding edge testing, but when nothing is mounted in it there are still files in /dev.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.