Heh, that's funny. Another solution is to start using devfs. Devfs
creates a /proc like filesystem, under /dev (it can be shared with your
current /dev) and in there all you devices show up, but only those you
actually have. So you would have something like
/dev/disks/disk0/{part1, part2...partn}. Very usefull, I'm not sure
why distributors are soooo slow to pick up this wonderful feature.
Le Jeudi, 3 octo 2002, � 21:29 Canada/Mountain, Ian Bruseker a �crit :
> On Thu, 2002-10-03 at 17:21, Stanley A. Schultz wrote:
>>
>> So, I checked /dev for all the listing that it had for hda*. Guess
>> what?
>> The highest number was hda16. That immediately suggests that the Linux
>> developers weren't expecting me (or anyone else for that matter) to
>> use
>> more than 16 partitions on hard disk 'a.'
> <snip>
>> A lengthy search of HOWTOs and FAQs for MAKEDEV again proved largely
>> fruitless. There were lots, but none of them gave detailed, itemized
>> instructions with an example or 2.
>>
>> So, I "winged it." I downloaded MAKEDEV-3.??.rpm and installed it,
>> moved
>> to /dev and entered the following series of commands:
>>
>> ./MAKEDEV /hda17
>> ./MAKEDEV /hda18
>> ./MAKEDEV /hda19
>> ./MAKEDEV /hda20
>> ./MAKEDEV /hda21
>> ./MAKEDEV /hda22
>>
>> and BINGO! I could mount the partitions by hand and read their
>> contents
>> just fine.
>>
> Ha. Hahahahaha. Sorry, but I really did laugh out loud at your
> solution. Why? Because it's so simple. Because I should have known
> that. I've been there before (with sound devices, not hard drives, but
> devices files are devices files after all). Really a simple solution
> to
> the problem, considering all the suggestions (including my own) that
> have flown around the list about this. Good for you, Stan.
>
>> I haven't tried it yet after rebooting (the acid test!), but I'm
>> pretty
>> sure it'll work.
>>
> Please, keep us informed. It sounds like you got it though. It sounds
> like a good solution to me.
>
> Ian
