fdisk on a new hdd

[mauro]

Well, it seems that YDL, needs absolutely a previous MacOs installation to
be installed in a HD.
So, you should Create a small (at least 2GB but can be much more if you want
use both the OSs) mac os partition, installing there a basical (or full)
OS9. Then you must set the OS9 to start the installation of YDL, putting the
right files in the right folders of the "file system" (YDL calls in this way
the Mac Installation). Then i advice you to choose in BootX the kernel
"vmlinux-2.4.20-8dBOOT" with the "use ramdisk button" checked, it will drive
you with anaconda (a nice and simple graphical installer) throug the
installation, and (due to the large size of the HD) you can choose
 to do an automatic partition or a graphical manual one.
The bootloader (lilo), will be installed into the first 1024 cilinder of the
master slave, otherwise how you could choose the OSs to use? But every
Distro do it automatically, asking before... heh.
Another way is to partition all the disk before in at least 4 partition: 1=
mac extended (for the file system and to use BootX) 2 = swap  / 3 = root / 4
= home (swap could be small, as 256 MB). The best way is to partition with
the utility HDT, cause the mac's Drive Setup doesn't works that fine for
Linux partition.
But with anaconda, you can leave it to do the job for you... do a choose and
good look.

> just installed a new 80gb ata drive in my
> machine--it's the slave to the existing 6gb drive.
> linux seems to recognize it as i can do an fdisk on
> /dev/hdb and it looks about the right size. but it
> gives me this everytime i run fdisk, even if i make a
> partition:
> 
> <snip>
> Device contains neither a valid DOS partition table,
> nor Sun, SGI or OSF disklabel
> Building a new DOS disklabel. Changes will remain in
> memory only,
> until you decide to write them. After that, of course,
> the previous
> content won't be recoverable.
> 
> 
> The number of cylinders for this disk is set to
> 155061.
> There is nothing wrong with that, but this is larger
> than 1024,
> and could in certain setups cause problems with:
> 1) software that runs at boot time (e.g., old versions
> of LILO)
> 2) booting and partitioning software from other OSs
> (e.g., DOS FDISK, OS/2 FDISK)
> </snip>
> 
> OK, well sometimes it actually saves the partition
> table and i can run fdisk and it says i have a single
> 80gb partition on there, but when i try to mount the
> drive as ext2 or ext3 it tells me that isn't the
> filesystem on there...(i set it to 83/Linux in fdisk)
> 
> help me? i've got a stack of cds waiting to hop on
> this disk...
> 
> 
> 
> =====
> <i am not bradley martin>
> 
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Search - Faster. Easier. Bingo.
> http://search.yahoo.com
> _______________________________________________
> yellowdog-newbie mailing list
> yellowdog-newbie@lists.terrasoftsolutions.com
> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-newbie