Package: hurd
Version: N/A
Hi,
I hope I don't make fuss about nothing, in case I don't understand the code.
Anyway, it looks strange.
In isofs/lookup.c (diskfs_get_directs), there is the first for-loop, which
seems to check if there are enough entries available.
I want to draw your attention t
=?Windows-1252?Q?Jes=FAs_Torres?= <[EMAIL PROTECTED]> writes:
> I think that the Unicode support eradicate the problems with the characters
> set and do the exchange of information between users more easy.
I just want to point out that naive unicode support is dangerous. This
is because there ar
Marcus Brinkmann <[EMAIL PROTECTED]> writes:
> On Wed, Apr 26, 2000 at 07:54:33PM -0400, Olivier Galibert wrote:
> > On Wed, Apr 26, 2000 at 11:26:37PM +0200, Marcus Brinkmann wrote:
> > > Anyway, here is a patch.
> >
> > Well, I'm not (yet) a hurd hacker[1], but this patch strikes me as
> > fun
Roland McGrath <[EMAIL PROTECTED]> writes:
> > why is the code that allows for user EXECSERVERS commented out?
>
> You got me. It might just have been buggy, or there might have been a
> security concern that we weren't ready to think about hard enough. There
> might be some old mailing list a
Marcus Brinkmann <[EMAIL PROTECTED]> writes:
> 1. When are you supposed to call diskfs_check_readonly, and when are you
> supposed to check the value of diskfs_readonly directly?
You are always supposed to use diskfs_check_readonly. You should do
it before you actually change the disk, but avoi
