On Tue, 25 Jul 2000, OKUJI Yoshinori wrote:
Hello,
> > I don't said it is bad idea, but have also its pros/cons as have my
> > solution. With my solution is good, that the partion is always allocated
> > and accessible. Bad on my solution is that your partions overlap.
> > With your solutions is good that rules are not broken. The bad is that the
> > partion when is not mapped in partiton table is unaccessible, and all
> > partioning programs handles it as unalloccated space.
>
> Yes, exactly. My idea is also bad, because of the very reason that
> you pointed out. But if there is no other solution that doesn't
> violate any rule, it is still the best, isn't it?
It is. But why not let users to break the rules, when they accept that
it should be dangerous for them. In many cases breaking this rule want
cause any problems ? Also when some of programs are unhappy with it, you
can disable that mapping with "partid (hdx,y) 0x0" (I don't red partition
table specifications, so I am not sure if this is regular way to delete
partitions, but at least for me it works). Needles to say that when it is
in system which is booted this way, you have problem. But there are still
two partition table entries which can be used to install such opereating
system to regular area on disk.
> > Looks quite good. If nothing from this is implemented, I can try to
> > implement it when I will find some spare time.
>
> I'm looking forward to your contribution. :)
I will try to implement it till till next monday.
> > Btw. The command "parttype" is implemented in grub yet ? If I remember
> > well, I don't saw its definicion in builtin.c. If it is, I am duno, that I
> > spent time writing my own "partid" with same functionality.
>
> It doesn't exist. So I said that was a "virtual" example.
So, can you rename my partid to parttype and add it to grub ? I think I
saw such something in grub TODO list.
> BTW, you don't have to implement your own functions for
> interpretation of the device syntax or conversion from a string to an
> integer, since there are already set_device and safe_parse_maxint.
Ok. I am not very well accusstomed with grub code. It was last friday when
I saw it first time. I saw, that set_device() was using and modifying some
global variables, so I rather wrote my own function.
Best regards,
Stevo.
--
Stefan Ondrejicka <[EMAIL PROTECTED]>
Beethovenova 11, 917 08 Trnava, Slovakia
http://www.idata.sk/~ondrej/
