>From colleague:
Hello,
Are there any plans to expand the procfs implementation to provide an
interface that is more in line with the implementations on Unixware,
Solaris and AIX? I've been writing a simple debugger that would be
portable among those three platforms, and others, but it is based
As long as your program isn't overstepping memory boundaries nothing should
happen.
What were you expecting?
-Original Message-
From: Miguel Mendez [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 09, 2002 8:38 AM
To: [EMAIL PROTECTED]
Subject: Electric fence usage
Hi,
I've installe
The original Stroustrop AT&T C++ complier called cfront was a front-end C
compiler. They may have it available at research.att.com. It's missing some
things, though, like generic container classes.
-Original Message-
From: Rayson Ho [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 03, 20
What on Earth are you talking about?
> -Original Message-
> From: Rafael Gomez [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, March 17, 2000 07:10
> To: FreeBSD Hackers
> Subject: kERNEL
>
> Can any of you send me a copy of a text kernel file?
>
> Rafael Gomez
> [EMAIL PROTECTED]
> Pag
Get a copy of the 4.4BSD book and read the relevant
code along with the various topics.
"Of course you're the Messiah! I say you are and I should know,
I've followed a few!" -- John Cleese in "Life of Brian"
Matthew Alton
Computer Services - UNIX Systems Administration
(314)632-6644 [EMAIL
: Andrzej Bialecki [SMTP:[EMAIL PROTECTED]]
> Sent: Saturday, October 30, 1999 10:56 AM
> To: Alton, Matthew
> Subject: Re: BSD XFS Port & BSD VFS Rewrite
>
> On Thu, 5 Aug 1999, Alton, Matthew wrote:
>
> > I am currently conducting a thorough study of the VFS subsy
that it is desirable, if
not necessary, for the realtime throughput guarantee policy. Nes pas?
> -Original Message-
> From: Russell Cattelan [SMTP:catte...@thebarn.com]
> Sent: Thursday, August 19, 1999 1:01 AM
> To: Alton, Matthew
> Cc: 'hack...@freebsd.org&
n the
commercial realm. As for licensing issues, I am purely agnostic -- I trust that
any legal issues can be worked out after the fact by the proper people.
> -Original Message-
> From: Russell Cattelan [SMTP:catte...@thebarn.com]
> Sent: Thursday, August 19, 1999 12:41 AM
> To:
nd that it is desirable, if
not necessary, for the realtime throughput guarantee policy. Nes pas?
> -Original Message-
> From: Russell Cattelan [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, August 19, 1999 1:01 AM
> To: Alton, Matthew
> Cc: '[EMAIL PROTECTED]'; &#x
n the
commercial realm. As for licensing issues, I am purely agnostic -- I trust that
any legal issues can be worked out after the fact by the proper people.
> -Original Message-
> From: Russell Cattelan [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, August 19, 1999 12:41 AM
> To: Al
As I parse the SGI PR-speak, IRIX is to be folded into Linux over time in
one massive penguin love-in. This will take place at some point after
IRIX has been disencunbered of it's AT&T/Univel/SCO whatever... It
really is a good time to be alive.
-Original Message-
From: Terry Lambert [ma
As I parse the SGI PR-speak, IRIX is to be folded into Linux over time in
one massive penguin love-in. This will take place at some point after
IRIX has been disencunbered of it's AT&T/Univel/SCO whatever... It
really is a good time to be alive.
-Original Message-
From: Terry Lambert [m
mostly done.
> -Original Message-
> From: Julian Elischer [SMTP:jul...@whistle.com]
> Sent: Wednesday, August 11, 1999 5:36 PM
> To: Alton, Matthew
> Cc: 'hack...@freebsd.org'; 'f...@freebsd.org'
> Subject: Re: BSD-XFS Update
>
> s
mostly done.
> -Original Message-
> From: Julian Elischer [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, August 11, 1999 5:36 PM
> To: Alton, Matthew
> Cc: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]'
> Subject: Re: BSD-XFS Update
>
> s
SGI has released a portion of the XFS source code under the GPL:
http://oss.sgi.com/projects/xfs/download/
the source file is xfs_log.tar.gz.
Of greater interest at this stage are the documents in:
http://oss.sgi.com/projects/xfs/design_docs/
I am currently researching methods for implementing
SGI has released a portion of the XFS source code under the GPL:
http://oss.sgi.com/projects/xfs/download/
the source file is xfs_log.tar.gz.
Of greater interest at this stage are the documents in:
http://oss.sgi.com/projects/xfs/design_docs/
I am currently researching methods for implementin
be done so long as the modules
constitute a discrete "product." I will have my lawyer confirm this
when the details of the SGI license become public.
> -Original Message-
> From: Chris Csanady [SMTP:ccsan...@scl.ameslab.gov]
> Sent: Tuesday, August 10, 1999 12:38 PM
>
can be done so long as the modules
constitute a discrete "product." I will have my lawyer confirm this
when the details of the SGI license become public.
> -Original Message-
> From: Chris Csanady [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, August 10, 1999 12:38 PM
> To:
What is the approved method for getting ahold of 64 clean bits? I've
been using the GNU/c9x "unsigned long long" and #ifdef-ing all over
the place but this strikes me as substantially less than elegant.
Once we have the bits, what is the Right Way to get them into
network order?
> -Original M
What is the approved method for getting ahold of 64 clean bits? I've
been using the GNU/c9x "unsigned long long" and #ifdef-ing all over
the place but this strikes me as substantially less than elegant.
Once we have the bits, what is the Right Way to get them into
network order?
> -Original
I am currently conducting a thorough study of the VFS subsystem
in preparation for an all-out effort to port SGI's XFS filesystem to
FreeBSD 4.x at such time as SGI gives up the code. Matt Dillon
has written in hackers- that the VFS subsystem is presently not
well understood by any of the active k
I am currently conducting a thorough study of the VFS subsystem
in preparation for an all-out effort to port SGI's XFS filesystem to
FreeBSD 4.x at such time as SGI gives up the code. Matt Dillon
has written in hackers- that the VFS subsystem is presently not
well understood by any of the active
, 1999 9:20 PM
> To: Alton, Matthew
> Cc: 'Nik Clayton'; David E. Cross; freebsd-hackers@FreeBSD.ORG
> Subject: Re: RE: DOC volunteer WAS:RE: userfs help needed.
>
>
> :Anyway, Mr. Dillon, once I have a development box to smack around, I
> :intend to start with
I'll follow these guidelines. Thank you.
> -Original Message-
> From: Nik Clayton [SMTP:n...@nothing-going-on.demon.co.uk]
> Sent: Friday, July 30, 1999 6:47 PM
> To: Alton, Matthew
> Cc: 'Nik Clayton'; 'Matthew Dillon'; David E. Cross;
> fr
FS code is here.
What are the perceived shortcomings of the current VFS? What suggestions
are being considered for the new design? What are the principal design
objectives?
> -Original Message-
> From: Matthew Dillon [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, July 30, 1999 9:
I'll follow these guidelines. Thank you.
> -Original Message-
> From: Nik Clayton [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, July 30, 1999 6:47 PM
> To: Alton, Matthew
> Cc: 'Nik Clayton'; 'Matthew Dillon'; David E. Cross;
> [EMAIL PROTECTED]
ag
and drop right into the new model and build like the very wind.
Thanks
-Original Message-
From: Nik Clayton [mailto:n...@nothing-going-on.demon.co.uk]
Sent: Friday, July 30, 1999 05:09
To: Alton, Matthew
Cc: 'Matthew Dillon'; David E. Cross; freebsd-hackers@FreeBSD.
ag
and drop right into the new model and build like the very wind.
Thanks
-Original Message-
From: Nik Clayton [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 30, 1999 05:09
To: Alton, Matthew
Cc: 'Matthew Dillon'; David E. Cross; [EMAIL PROTECTED]
Subject: Re: DOC volunteer
I ran screaming into the woods last year from trying to grok VOP_foo. The
prospect of a rewrite fills me with warmth and fuzziness. I hereby volunteer
to maintain the VOP(9) man pages and to flesh out my notes into a big, beefy
FS-implementer's Guide to the new VOP_foo. All the coders have to do
I ran screaming into the woods last year from trying to grok VOP_foo. The
prospect of a rewrite fills me with warmth and fuzziness. I hereby volunteer
to maintain the VOP(9) man pages and to flesh out my notes into a big, beefy
FS-implementer's Guide to the new VOP_foo. All the coders have to do
If someone in the FS dept. would draw up a broad outline for FS implementation
I hereby volunteer to flesh it out thoroughly and donate the end-product docs to
the FreeBSD project. I am a professional UNIX (AIX/SOLARIS) programmer and
fairly clueful kernel source peruser and tweaker, fully capable
If someone in the FS dept. would draw up a broad outline for FS implementation
I hereby volunteer to flesh it out thoroughly and donate the end-product docs to
the FreeBSD project. I am a professional UNIX (AIX/SOLARIS) programmer and
fairly clueful kernel source peruser and tweaker, fully capabl
Yes, quite.
> -Original Message-
> From: Christoph Kukulies [SMTP:k...@gilberto.physik.rwth-aachen.de]
> Sent: Monday, June 07, 1999 10:59 AM
> To: hack...@freebsd.org
> Subject: linux and freebsd kernels conceptually different?
>
> Could one say that Linux vs. FreeBSD kernels are
Well, the serial devices are not typically used for TCP traffic, but you should
look at ioctl(3), read(3), write(3), socket(3), bind(3),
listen(3), send(3), recv(3) for starters. The tty devices are treated as files.
Remember, in UNIX everything is a file unless it isn't.
The ethernet cards, which
34 matches
Mail list logo
