Tiny Core Linux

Tiny Core Base => TCB Q&A Forum => Topic started by: lumosy on November 22, 2011, 07:14:11 AM

Title: [SOLVED] VMWare HDD defined IDE - Why does TCL see it as /dev/sda?
Post by: lumosy on November 22, 2011, 07:14:11 AM

I have been very careful to follow the key points & guidelines in  http://wiki.tinycorelinux.net/wiki:vmware_installation (http://wiki.tinycorelinux.net/wiki:vmware_installation) , especially noting the need to define an IDE type drive (0:0).

But when I powered up TCL (4.1), it shows up as /dev/sda, not /dev/hda.

Why?

What am I doing wrong?

Title: Re: VMWare HDD defined IDE - Why does TCL see it as /dev/sda?
Post by: Rich on November 22, 2011, 07:17:52 AM

Hi lumosy
You are not doing anything wrong. The new version of the kernel replaced hd with sd.

Title: Re: VMWare HDD defined IDE - Why does TCL see it as /dev/sda?
Post by: lumosy on November 22, 2011, 08:46:24 AM

Quote from: Rich on November 22, 2011, 07:17:52 AM

The new version of the kernel replaced hd with sd.

Thanks for pointing this out.

I can confirm that as of TCL's latest release (4.1) the requirement for an IDE type (when using VMWare) remains, despite IDE HDDs being renamed to sd.

I wonder whether the boot options changed accordingly as well? (e.g. home={hda1|sda1})

Title: Re: VMWare HDD defined IDE - Why does TCL see it as /dev/sda?
Post by: Rich on November 22, 2011, 08:53:05 AM

Hi lumosy
Yes, all references to hd should become sd.

Title: Re: [SOLVED] VMWare HDD defined IDE - Why does TCL see it as /dev/sda?
Post by: genec on November 23, 2011, 10:30:48 PM

libata was used in the new TC kernel.  Unlike the old PATA driver set, libata unifies PATA and SATA drivers together so they all look more alike.