I recently purchased a new laptop HDD, tossed three partitions onto
the drive (/, /usr, and swap), newfs'ed them with UFS2, mounted the
new drive as a umass device, copied files over (tar), and now when I
boot with my new drive, the kernel is having problems launching
/sbin/init. For the life of
I recently purchased a new laptop HDD, tossed three partitions onto
the drive (/, /usr, and swap), newfs'ed them with UFS2, mounted the
new drive as a umass device, copied files over (tar), and now when I
boot with my new drive, the kernel is having problems launching
/sbin/init. For the
On Fri, 28 Mar 2003, Sean Chittenden wrote:
I recently purchased a new laptop HDD, tossed three partitions onto
the drive (/, /usr, and swap), newfs'ed them with UFS2, mounted the
new drive as a umass device, copied files over (tar), and now when I
boot with my new drive, the kernel is
On Fri, 28 Mar 2003, Sean Chittenden wrote:
Ah! Figured it out after reading through init's src: /dev didn't
exist therefore the machine wouldn't start. No good. I may find
a place to stick this got'cha in the docs or add an mkdir() call
to init.
mkdir(2) on / is not going to
