On Fri, 23 Jan 2004, Andrew Clausen wrote:
> This is one of my favourite stories!
Talking about favourites, here is my "favourite" challange. Since earlier
ntfsresize could resize only if there weren't data after the new size,
many people made the compromise "ok, let's shrink here now and more later
on when/if I need/can" and some ended up in this situation:
hda1 primary NTFS
hda2 primary linux
hda3 primary linux
hda4 extended
hda5 logical linux
...
Where could they put the space gained at the end of hda1 _without_
changing and renumbering hda2, hda3, hda5? AFAIS nowhere. What would be
the least pain for them? Merging the free space with hda2 but that's not
supported (it could also break Linux boot, e.g. LILO used and hda2 has the
kernel).
> > - better logging of errors (probably should be to a file) and
>
> Which file? Where could it be saved? Maybe syslog?
Syslog seems overkill, probably not everywhere available, a bunch of
unrelated messages, harder to get the info to recreate a problem
(basically user defined format).
But opening a file should work everywhere. Well, 'write' maybe not but
most should have at least one read/write directory, probably /tmp.
So it could be in /tmp or current directory or in /var/log or ... and make
sure the user takes steps, if it's needed, the file won't get lost when
the box is rebooted.
> > Of course I agree. "If you can reproduce this bug with the latest version
> > found at .... please send the 'parted.log' file.... ". Etc.
>
> Perhaps a better solution would be to create some kind of hash
> of the bug report message (which includes version number), and they
> can type that hash in to see if a problem matching that description
> has been fixed.
I thought about this also ("Etc" above :) The simplest implementation
would be the 'Parted FAQ'.
> PS: I just registered an alioth project for Parted. Waiting for approval...
Cool :)
Cheers,
Szaka
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
