s
have named forks (or streams, or whatever you wish to call them)
associated with them.
Read the archives on this issue :)
Mo.
- --
Mo McKinlay [EMAIL PROTECTED] http://ekto.org
Read http://www.ietf.org/rfc/rfc18
named forks (or streams, or whatever you wish to call them)
associated with them.
Read the archives on this issue :)
Mo.
- --
Mo McKinlay [EMAIL PROTECTED] http://ekto.org
Read http://www.ietf.org/rfc/rfc1855.txt
le to ftp but
> (sometimes) show with their `ls`, and never with nlist.
> Maybe you can still download stuff if you are running from a
> Web Crawler, but it doesn't work with `ftp` anymore.
We've had no problem reports, and it works fine for me.
Mo.
- --
Mo McKinlay -- GNU Webmaste
EA
> vop_eattr_serialize - export all the EAs as a stream of entries.
>
> Thoughts? You mught want to refer back to the paper to get the whole EAs
> proposal...
I shall, and get back to you this evening (workworkworkwork... :)
Mo.
- --
Mo McKinlay
[EMAIL PROTECTED]
- -
ughts? You mught want to refer back to the paper to get the whole EAs
proposal...
I shall, and get back to you this evening (workworkworkwork... :)
Mo.
- --
Mo McKinlay
[EMAIL PROTECTED]
- -
GnuPG/PGP Key: pub 1024D/76A
lways uses the same inode number
> (11), but I don't know if that is anywhere enforced.
I seem to recall e2fsck complaining when I renamed lost+found, but that
may well be a consistency check. Don't quote me on this, though.
Mo.
- --
Mo McK
same inode number
(11), but I don't know if that is anywhere enforced.
I seem to recall e2fsck complaining when I renamed lost+found, but that
may well be a consistency check. Don't quote me on this, though.
Mo.
- --
Mo McKinlay
[EMAIL
ng thy next line ..
> now I know why I never read the bible.
..or Monty Python...
- --
Mo McKinlay
[EMAIL PROTECTED]
- -
GnuPG/PGP Key: pub 1024D/76A275F9 2000-07-22
-BEGIN PGP SIGNATURE-
Version: Gn
read the bible.
..or Monty Python...
- --
Mo McKinlay
[EMAIL PROTECTED]
- -
GnuPG/PGP Key: pub 1024D/76A275F9 2000-07-22
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Today, Linus Torvalds ([EMAIL PROTECTED]) wrote:
> Just wait. My crystal ball is infallible.
One of these days, that line will be your downfall :-)
*grins*
Mo.
- --
Mo McKinlay
[EMAIL PROTEC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Today, Linus Torvalds ([EMAIL PROTECTED]) wrote:
Just wait. My crystal ball is infallible.
One of these days, that line will be your downfall :-)
*grins*
Mo.
- --
Mo McKinlay
[EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Today, Michael Rothwell ([EMAIL PROTECTED]) wrote:
> Mo McKinlay wrote:
>
> > Nono, that's not what I mean - each of the filesystems fails if it
> > doesn't support what you're trying to do, that's given - but having
nd of inconsistency.
Mo.
- --
Mo McKinlay
[EMAIL PROTECTED]
- -
GnuPG/PGP Key: pub 1024D/76A275F9 2000-07-22
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see h
ame you to high heaven for that last suggestion if he was
paying much attention to this thread :-)
- --
Mo McKinlay
[EMAIL PROTECTED]
- -
GnuPG/PGP Key: pub 1024D/76A275F9 2000-07-22
-BEGIN PGP SIGNATURE-
Version: G
as it stands would break in that situation
(assuming I've not missed something :)
Mo.
- --
Mo McKinlay
[EMAIL PROTECTED]
- -
GnuPG/PGP Key: pub 1024D/76A275F9 2000-07-22
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.4 (GNU
eam() then returns an
fd which can be read/written/sendfiled/closed as the programmer wishes.
How daft does this sound?
Apart from the additional of a new open()-type call, your paper seems to
be fairly solid.
Mo.
- --
Mo McKinlay
[EMAIL PROTECTED]
- -
ally there? (Pretty much why I'm more in favour of a specific API
for reading streams, extended attributes and whatnot, over any of the
other solutions thus suggested).
Mo.
- --
Mo McKinlay
[EMAIL PROTECTED]
- -
GnuPG/PGP Key
(Pretty much why I'm more in favour of a specific API
for reading streams, extended attributes and whatnot, over any of the
other solutions thus suggested).
Mo.
- --
Mo McKinlay
[EMAIL PROTECTED]
- -
GnuPG/PGP Key: pub 1024D
an be read/written/sendfiled/closed as the programmer wishes.
How daft does this sound?
Apart from the additional of a new open()-type call, your paper seems to
be fairly solid.
Mo.
- --
Mo McKinlay
[EMAIL PROTECTED]
- -
Gnu
ould break in that situation
(assuming I've not missed something :)
Mo.
- --
Mo McKinlay
[EMAIL PROTECTED]
- -
GnuPG/PGP Key: pub 1024D/76A275F9 2000-07-22
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: Fo
igh heaven for that last suggestion if he was
paying much attention to this thread :-)
- --
Mo McKinlay
[EMAIL PROTECTED]
- -
GnuPG/PGP Key: pub 1024D/76A275F9 2000-07-22
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.4
onsistency.
Mo.
- --
Mo McKinlay
[EMAIL PROTECTED]
- -
GnuPG/PGP Key: pub 1024D/76A275F9 2000-07-22
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Today, Michael Rothwell ([EMAIL PROTECTED]) wrote:
Mo McKinlay wrote:
Nono, that's not what I mean - each of the filesystems fails if it
doesn't support what you're trying to do, that's given - but having a
different delimeter
concise
portable API for accessing streams (even if it *started out*
Linux-specific) - without imposing silly semantics on existing
applications which currently ignore streams anyway.
Mo.
- --
Mo McKinlay
[EMAIL PROTECTED]
- ---
for accessing streams (even if it *started out*
Linux-specific) - without imposing silly semantics on existing
applications which currently ignore streams anyway.
Mo.
- --
Mo McKinlay
[EMAIL PROTECTED]
- -
GnuPG/PGP Key: pub 1024D
s it is already used for this purpose --
apart from the fact that POSIX already allows applications to use it in
filenames).
- --
Mo McKinlay
[EMAIL PROTECTED]
- -
GnuPG/PGP Key: pub 1024D/76A275F9 2000-07-22
already allows applications to use it in
filenames).
- --
Mo McKinlay
[EMAIL PROTECTED]
- -
GnuPG/PGP Key: pub 1024D/76A275F9 2000-07-22
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.4 (GNU
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Today, David Lang ([EMAIL PROTECTED]) wrote:
> On Thu, 4 Jan 2001, Mo McKinlay wrote:
>
> > > The off button need not and _does not_ remove power instantly (if at
> > > all) on many appliances.
> >
&g
it so that it's acceptable?
- --
Mo McKinlay
[EMAIL PROTECTED]
- -
GnuPG/PGP Key: pub 1024D/76A275F9 2000-07-22
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnu
> > > > > it's essential for embedded devices.
Answer your question?
- --
Mo McKinlay
[EMAIL PROTECTED]
- -
GnuPG/PGP Key: pub 1024D/76A275F9 2000-07-22
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.4 (GN
for embedded devices.
Answer your question?
- --
Mo McKinlay
[EMAIL PROTECTED]
- -
GnuPG/PGP Key: pub 1024D/76A275F9 2000-07-22
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http
acceptable?
- --
Mo McKinlay
[EMAIL PROTECTED]
- -
GnuPG/PGP Key: pub 1024D/76A275F9 2000-07-22
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Today, David Lang ([EMAIL PROTECTED]) wrote:
On Thu, 4 Jan 2001, Mo McKinlay wrote:
The off button need not and _does not_ remove power instantly (if at
all) on many appliances.
Indeed - but unplugging your VCR from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> does anyone other than me think that the pm code is *way* too agressive about
> spinning down the hard drive? my 256mb laptop (2.2.16) will only spin down the
> disk for about 30 seconds before it decides it's got something else it feels
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
does anyone other than me think that the pm code is *way* too agressive about
spinning down the hard drive? my 256mb laptop (2.2.16) will only spin down the
disk for about 30 seconds before it decides it's got something else it feels
get the current maestro open driver to recognize the chip
> at least the mixer will start to work.
Aha - Many thanks! I shall go and experiment, then :)
--
Mo McKinlay
[EMAIL PROTECTED]
-
GnuPG/PGP Key: pub 1024D/7
miserably :/]
Any hints/clues/etc welcome.
Many thanks,
Mo.
--
Mo McKinlay
[EMAIL PROTECTED]
-
GnuPG/PGP Key: pub 1024D/76A275F9 2000-07-22
-
To unsubscribe from this list: send the line "unsubscribe linux-k
miserably :/]
Any hints/clues/etc welcome.
Many thanks,
Mo.
--
Mo McKinlay
[EMAIL PROTECTED]
-
GnuPG/PGP Key: pub 1024D/76A275F9 2000-07-22
-
To unsubscribe from this list: send the line "unsubscribe linux-k
open driver to recognize the chip
at least the mixer will start to work.
Aha - Many thanks! I shall go and experiment, then :)
--
Mo McKinlay
[EMAIL PROTECTED]
-
GnuPG/PGP Key: pub 1024D/76A275F9 2000-07-22
ir mail servers
properly and close those damned open relays. THAT is who MAPS should be
putting pressure on, not the innocent end-users.
My serveral cents,
Mo [who is now praying that his ISP's mail server has decided to work
today :P]
--
Mo McKinlay Chief Sof
amned open relays. THAT is who MAPS should be
putting pressure on, not the innocent end-users.
My serveral cents,
Mo [who is now praying that his ISP's mail server has decided to work
today :P]
--
Mo McKinlay Chief Software Architect inter
nd 500mb HDs as
routers/NAT boxes - I've had no downtime in about 18 months on any of the
machines. Each one runs 2.0.36 as RedHat patched it for their 5.2 release
(I've never had to recompile the kernel for any of them, so I don't know
who much this may vary from stock 2.0.36).
HTH,
Mo.
--
t; perfectly legitimate, tested clean as a whistle, and fully anti-spam compliant
etc. We
> shouldn't have to pay because someone else has decided our city has a con artist
> somewhere.
If you're on a fixed IP, I can relay for you, if that helps.
Mo.
--
Mo McKinlay Chief
, tested clean as a whistle, and fully anti-spam compliant
etc. We
shouldn't have to pay because someone else has decided our city has a con artist
somewhere.
If you're on a fixed IP, I can relay for you, if that helps.
Mo.
--
Mo McKinlay Chief Software Architect inter
44 matches
Mail list logo