On Fri, Feb 06, at 11:21 Anthony Price wrote:
Portability
Host system Ubuntu 8.10
Book 6.4
I am experiencing problems moving a working installation between machines.
Here's how I built the system:
On machine A
Partition disk unstall Ubuntu
Remove disk and install on machine B
Portability
Host system Ubuntu 8.10
Book 6.4
I am experiencing problems moving a working installation between machines.
Here's how I built the system:
On machine A
Partition disk unstall Ubuntu
Remove disk and install on machine B
Build LFS
Make this bootable
Machine B is now dual boot
*** Move this disk back to Machine A (not B as in the original post) ***
Ubuntu boots ok
You probably need to recompile the kernel to include the correct driver
for your controller in machine A.
In the 2.6.27 kernel series this should be included under the following
menu:
Device
Agathoklis D. Hatzimanikas wrote:
On Fri, Feb 06, at 11:21 Anthony Price wrote:
Portability
Host system Ubuntu 8.10
Book 6.4
I am experiencing problems moving a working installation between machines.
Here's how I built the system:
On machine A
Partition disk unstall Ubuntu
On Fri, Feb 6, 2009 at 6:56 AM, support supp...@expertrepair.co.uk wrote:
*** Move this disk back to Machine A (not B as in the original post) ***
Ubuntu boots ok
You probably need to recompile the kernel to include the correct driver
for your controller in machine A.
In the 2.6.27 kernel
support wrote:
*** Move this disk back to Machine A (not B as in the original post) ***
Ubuntu boots ok
You probably need to recompile the kernel to include the correct driver
for your controller in machine A.
In the 2.6.27 kernel series this should be included under the
Ryan Isaacs wrote:
I thought modules were just some
compiled code, which likely sits as a binary file on the disk
somewhere. They are loaded into RAM when needed (user using insmod, or
system doing it automatically). So, how does the ramdisk fit in?
This ought to turn the light bulb on for
On Fri, Feb 6, 2009 at 11:20 AM, Randy McMurchy lfs.u...@mcmurchy.com wrote:
Ryan Isaacs wrote:
I thought modules were just some
compiled code, which likely sits as a binary file on the disk
somewhere. They are loaded into RAM when needed (user using insmod, or
system doing it automatically).
