One of the things missing from mklinux right now that we're looking at ways to implement is the equivalent of 'fdisk'. The major utilisation for this would be to display the partition table for disk that is already formatted in order to get the partition names and types for mounting or hmounting, although the ability to change partition names/types/sizes would also be useful.
Would this be something appropriate for the hfstools? I notice that much of the library code necessary to scan the partition table is already in place, could a new command (or an option to hmount or hvol) easily use this to display the partition information?
Partition naming is O/S dependent, so the hfstools might require some knowledge about the O/S partition naming scheme. For information, mklinux uses standard linux device names, ie. /dev/sd followed by scsi device (a-h map to device ID 0-7) then partition number (0 is raw disk, 1 is hfs partition map, 2 is (often) a driver partition, 3 is (often) the first hfs partition, etc).
eg : /dev/sdc3 is scsi device 2 partition number 3.
Does anyone else have any thoughts on this? :-)
[ Nick ] -- Nick Stephen Web: http://www.gr.osf.org/~stephen OSF Research Institute Email: stephen@gr.osf.org 2, Avenue de Vignate Phone: +33 76 63 48 72 38610 Gieres - France Fax: +33 76 51 05 32
Nick STEPHEN wrote:
One of the things missing from mklinux right now that we're looking at ways to implement is the equivalent of 'fdisk'. The major utilisation for this would be to display the partition table for disk that is already formatted in order to get the partition names and types for mounting or hmounting, although the ability to change partition names/types/sizes would also be useful.
Hmm.. I am just now writing an fdisk for Linux/68k on Amiga. If I get information about it, I also could try one for Mac.
Partition naming is O/S dependent, so the hfstools might require some knowledge about the O/S partition naming scheme. For information, mklinux uses standard linux device names, ie. /dev/sd followed by scsi device (a-h map to device ID 0-7) then partition number (0 is raw disk, 1 is hfs partition map, 2 is (often) a driver partition, 3 is (often) the first hfs partition, etc).
eg : /dev/sdc3 is scsi device 2 partition number 3.
hfstools do not need about partition naming scheme. This needs to be implemented into the kernel, I think.
On Tue, 30 Jul 1996, Stefan Reinauer wrote:
Partition naming is O/S dependent, so the hfstools might require some knowledge about the O/S partition naming scheme. For information, mklinux uses standard linux device names, ie. /dev/sd followed by scsi device (a-h map to device ID 0-7) then partition number (0 is raw disk, 1 is hfs partition map, 2 is (often) a driver partition, 3 is (often) the first hfs partition, etc).
eg : /dev/sdc3 is scsi device 2 partition number 3.
hfstools do not need about partition naming scheme. This needs to be implemented into the kernel, I think.
They don't need to be implemented anywhere. The partitions are named when you name the device files, which could be named anything you want. I could make /dev/harddrive1 point to device 8, 0 (/dev/sda normally). If the utilities that manipulate device are written correctly (fdisk), the partitions should show up as:
/dev/harddrive11 /dev/harddrive12 /dev/harddrive13 ...
This isn't a function of hfstools or the kernel. It's just a commonly-followed convention.
-------- Got a Linux problem? Or can you help others solve them? Visit the Linux Common Problems page at http://vortex.cc.missouri.edu/~rhys/linux.html
Have you seen this computer: IBM ValuePoint 466DX2 S/N: 23AVPLT Stolen from MU campus December '94 from Mark Twain Hall. If seen, please send mail to ccthuryn@showme.missouri.edu.
Justin "Rhys Thuryn" McNutt wrote:
They don't need to be implemented anywhere. The partitions are named when you name the device files, which could be named anything you want. I could make /dev/harddrive1 point to device 8, 0 (/dev/sda normally). If the utilities that manipulate device are written correctly (fdisk), the partitions should show up as:
Yes, it should show up as this. But only, if the Kernel (Or mk) can understand the way how partitions are written to disk. (Partition Tabke Format). I came in contact with this stuff, when I tried to use a RDB-Harddisk from an Amiga 68k in my P100 System. Linux recognized /dev/hdc but not /dev/hdc1,hdc2,hdc3.
/dev/harddrive11 /dev/harddrive12 /dev/harddrive13
Stefan.
On Wed, 31 Jul 1996, Stefan Reinauer wrote:
Justin "Rhys Thuryn" McNutt wrote:
They don't need to be implemented anywhere. The partitions are named when you name the device files, which could be named anything you want. I could make /dev/harddrive1 point to device 8, 0 (/dev/sda normally). If the utilities that manipulate device are written correctly (fdisk), the partitions should show up as:
Yes, it should show up as this. But only, if the Kernel (Or mk) can understand the way how partitions are written to disk. (Partition Tabke Format). I came in contact with this stuff, when I tried to use a RDB-Harddisk from an Amiga 68k in my P100 System. Linux recognized /dev/hdc but not /dev/hdc1,hdc2,hdc3.
Granted, but that doesn't have anything to do with the *names*. My point was that although ~100% of Linux machines follow the /dev/{s,d}d[a-h][1-16] scheme for hard drives, this isn't mandatory. I could name them anything I want, and as long as the device works in the first place, it will continue to work with the new name.
-------- Got a Linux problem? Or can you help others solve them? Visit the Linux Common Problems page at http://vortex.cc.missouri.edu/~rhys/linux.html
Have you seen this computer: IBM ValuePoint 466DX2 S/N: 23AVPLT Stolen from MU campus December '94 from Mark Twain Hall. If seen, please send mail to ccthuryn@showme.missouri.edu.
-
Justin "Rhys Thuryn" McNutt -
Nick STEPHEN -
Stefan Reinauer