> I agree with the approach. But why write a simplistic volume manager
> when we already have vinum?
vinum is far from simplistic, but I suppose it might also do. :)
Still, it would someday be nice if you could use vinum as the very
powerful swiss-army knife that it currently is OR as a dull ax
> I agree with the approach. But why write a simplistic volume manager
> when we already have vinum?
vinum is far from simplistic, but I suppose it might also do. :)
Still, it would someday be nice if you could use vinum as the very
powerful swiss-army knife that it currently is OR as a dull axe
On Fri, 25 Jun 1999, Mike Smith wrote:
> >
> > > > static struct sockaddr_in servaddr;
> > >
> > > This needs to be a valid structure in USER space, not kernel.
> >
> > OK. I suspected as much. Question is: how do I open a connection from
> > KERNEL space?
>
> You don't.
>
> If you're rea
On Fri, 25 Jun 1999, Mike Smith wrote:
> >
> > > > static struct sockaddr_in servaddr;
> > >
> > > This needs to be a valid structure in USER space, not kernel.
> >
> > OK. I suspected as much. Question is: how do I open a connection from
> > KERNEL space?
>
> You don't.
>
> If you're real
Ville-Pertti Keinonen <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] (Mike O'Dell) writes:
> > we published the best Unix SMP paper I've ever seen in Computing
> > Systems - from the Amdahl guys who did an SMP version of the kernel
> > by very clever hacks on SPLx() macros to make them spin locks
Ville-Pertti Keinonen wrote:
> m...@servo.ccr.org (Mike O'Dell) writes:
> > we published the best Unix SMP paper I've ever seen in Computing
> > Systems - from the Amdahl guys who did an SMP version of the kernel
> > by very clever hacks on SPLx() macros to make them spin locks and
> > a bit of ot
On Fri, 25 Jun 1999 13:02:00 MST, Aaron Smith wrote:
> hey, that's a pretty neat feature. i confess i wasn't aware of that. out
> of curiosity, can old inetds read this without choking?
No, the extension would cause older inetd's to barf.
> agreed; what i was trying to get at is the mental d
On Fri, 25 Jun 1999 13:02:00 MST, Aaron Smith wrote:
> hey, that's a pretty neat feature. i confess i wasn't aware of that. out
> of curiosity, can old inetds read this without choking?
No, the extension would cause older inetd's to barf.
> agreed; what i was trying to get at is the mental di
[Format recovered--see http://www.lemis.com/email/email-format.html]
On Friday, 25 June 1999 at 18:22:19 -0700, Jordan K. Hubbard wrote:
>> to do actually it. Personally, I think it would be a doable
>> project if someone wanted to have a go at it - to allow a filesystem
>> to be gro
[Format recovered--see http://www.lemis.com/email/email-format.html]
On Friday, 25 June 1999 at 18:22:19 -0700, Jordan K. Hubbard wrote:
>> to do actually it. Personally, I think it would be a doable
>> project if someone wanted to have a go at it - to allow a filesystem
>> to be grow
Can anybody recommend a good Type I Compact Flash ethernet card that
has a driver for one or more of FreeBSD, NetBSD or OpenBSD?
Please note, I'm not asking for a PC Card, PCMCIA, or CardBus. I have
a device that has a Type I Compact Flash slot. All the CF Ethernet
cards I've seen have shared
Can anybody recommend a good Type I Compact Flash ethernet card that
has a driver for one or more of FreeBSD, NetBSD or OpenBSD?
Please note, I'm not asking for a PC Card, PCMCIA, or CardBus. I have
a device that has a Type I Compact Flash slot. All the CF Ethernet
cards I've seen have shared t
> to do actually it. Personally, I think it would be a doable
> project if someone wanted to have a go at it - to allow a filesystem
> to be grown or shrunk on a cylinder-by-cylinder basis. The only real
> complexity occurs when you are shrinking a filesystem - you have to locat
> to do actually it. Personally, I think it would be a doable
> project if someone wanted to have a go at it - to allow a filesystem
> to be grown or shrunk on a cylinder-by-cylinder basis. The only real
> complexity occurs when you are shrinking a filesystem - you have to locat
Can anyone please give me some clues as to how to build X with thread support
enabled. I think the right way to do it is to add the relevant options to
config/cf/FreeBSD.cf, something like
#define HasPosixThreads YES
#define ThreadedX YES
#define ThreadsLibraries-pt
Can anyone please give me some clues as to how to build X with thread support
enabled. I think the right way to do it is to add the relevant options to
config/cf/FreeBSD.cf, something like
#define HasPosixThreads YES
#define ThreadedX YES
#define ThreadsLibraries-pth
> On Fri, 25 Jun 1999 15:55:03 -0600
> Wes Peters <[EMAIL PROTECTED]> wrote:
>
> > Are there enough bytes available in the BIOS NVRAM? That would do
> > nicely as a place to store it.
>
> If you want this to be widely adoped across the free OS community
> (hell, even if you want both of Fr
> On Fri, 25 Jun 1999 15:55:03 -0600
> Wes Peters wrote:
>
> > Are there enough bytes available in the BIOS NVRAM? That would do
> > nicely as a place to store it.
>
> If you want this to be widely adoped across the free OS community
> (hell, even if you want both of FreeBSD's platforms to
> Matthew Jacob wrote:
> >
> > > > Whose BIOS NVRAM?
> > >
> > > The host system BIOS NVRAM. I thought we were looking for a per-host
> > > ID here, right?
> >
> > Yes, but this kind of NVRAM isn't available on an Alpha, or a Sparc.
>
> On the SPARC you can put it in the OpenBoot environment.
> Matthew Jacob wrote:
> >
> > > > Whose BIOS NVRAM?
> > >
> > > The host system BIOS NVRAM. I thought we were looking for a per-host
> > > ID here, right?
> >
> > Yes, but this kind of NVRAM isn't available on an Alpha, or a Sparc.
>
> On the SPARC you can put it in the OpenBoot environment.
Matthew Jacob wrote:
>
> > > Whose BIOS NVRAM?
> >
> > The host system BIOS NVRAM. I thought we were looking for a per-host
> > ID here, right?
>
> Yes, but this kind of NVRAM isn't available on an Alpha, or a Sparc.
On the SPARC you can put it in the OpenBoot environment. I dunno
about the
Matthew Jacob wrote:
>
> > > Whose BIOS NVRAM?
> >
> > The host system BIOS NVRAM. I thought we were looking for a per-host
> > ID here, right?
>
> Yes, but this kind of NVRAM isn't available on an Alpha, or a Sparc.
On the SPARC you can put it in the OpenBoot environment. I dunno
about the A
On Thu, 24 Jun 1999, Mike Smith wrote:
> > It's stupid to tune everything for performance except for the web
> > server -- they should be using Zeus, not Apache.
>
> The Zeus evaluation license prohibits its use for benchmarks, and the
> Zeus folks failed to respond to any of my attempts to com
On Thu, 24 Jun 1999, Mike Smith wrote:
> > It's stupid to tune everything for performance except for the web
> > server -- they should be using Zeus, not Apache.
>
> The Zeus evaluation license prohibits its use for benchmarks, and the
> Zeus folks failed to respond to any of my attempts to comm
On Fri, 25 Jun 1999 16:18:04 -0600
Wes Peters <[EMAIL PROTECTED]> wrote:
> > Whose BIOS NVRAM?
>
> The host system BIOS NVRAM. I thought we were looking for a per-host
> ID here, right?
I think Matt meant "which vendor's BIOS?"
-- Jason R. Thorpe <[EMAIL PROTECTED]>
To Unsubs
On Fri, 25 Jun 1999 15:55:03 -0600
Wes Peters <[EMAIL PROTECTED]> wrote:
> Are there enough bytes available in the BIOS NVRAM? That would do
> nicely as a place to store it.
If you want this to be widely adoped across the free OS community
(hell, even if you want both of FreeBSD's platform
On Fri, 25 Jun 1999 16:18:04 -0600
Wes Peters wrote:
> > Whose BIOS NVRAM?
>
> The host system BIOS NVRAM. I thought we were looking for a per-host
> ID here, right?
I think Matt meant "which vendor's BIOS?"
-- Jason R. Thorpe
To Unsubscribe: send mail to majord...@freebsd.o
On Fri, 25 Jun 1999 15:55:03 -0600
Wes Peters wrote:
> Are there enough bytes available in the BIOS NVRAM? That would do
> nicely as a place to store it.
If you want this to be widely adoped across the free OS community
(hell, even if you want both of FreeBSD's platforms to support it),
yo
> > Whose BIOS NVRAM?
>
> The host system BIOS NVRAM. I thought we were looking for a per-host
> ID here, right?
Yes, but this kind of NVRAM isn't available on an Alpha, or a Sparc.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
> > Whose BIOS NVRAM?
>
> The host system BIOS NVRAM. I thought we were looking for a per-host
> ID here, right?
Yes, but this kind of NVRAM isn't available on an Alpha, or a Sparc.
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the mess
Matthew Jacob wrote:
>
> > >
> > > I want it to persist until it's changed. Change doesn't mean a reboot.
> > >
> > > The Linux folks (mostly Ted) helped me clarify some thinking about this so
> > > that the basic original source of the seeded WWN doesn't have to come from
> > > first principles
Matthew Jacob wrote:
>
> > >
> > > I want it to persist until it's changed. Change doesn't mean a reboot.
> > >
> > > The Linux folks (mostly Ted) helped me clarify some thinking about this so
> > > that the basic original source of the seeded WWN doesn't have to come from
> > > first principles i
> >
> > I want it to persist until it's changed. Change doesn't mean a reboot.
> >
> > The Linux folks (mostly Ted) helped me clarify some thinking about this so
> > that the basic original source of the seeded WWN doesn't have to come from
> > first principles in hardware that can be read pri
> >
> > I want it to persist until it's changed. Change doesn't mean a reboot.
> >
> > The Linux folks (mostly Ted) helped me clarify some thinking about this so
> > that the basic original source of the seeded WWN doesn't have to come from
> > first principles in hardware that can be read prio
Matthew Jacob wrote:
>
> I want it to persist until it's changed. Change doesn't mean a reboot.
>
> The Linux folks (mostly Ted) helped me clarify some thinking about this so
> that the basic original source of the seeded WWN doesn't have to come from
> first principles in hardware that can be r
Matthew Jacob wrote:
>
> I want it to persist until it's changed. Change doesn't mean a reboot.
>
> The Linux folks (mostly Ted) helped me clarify some thinking about this so
> that the basic original source of the seeded WWN doesn't have to come from
> first principles in hardware that can be re
Aaron Smith wrote:
>
> On Thu, 24 Jun 1999 20:14:19 CDT, Alfred Perlstein writes:
> >I'm not sure what you mean by the refernce to malloc types, I just
> >thought something along the lines of mutex_t with an API
> >for trying, allocating, freeing and initializing them.
>
> i'd really like to imp
Aaron Smith wrote:
>
> On Thu, 24 Jun 1999 20:14:19 CDT, Alfred Perlstein writes:
> >I'm not sure what you mean by the refernce to malloc types, I just
> >thought something along the lines of mutex_t with an API
> >for trying, allocating, freeing and initializing them.
>
> i'd really like to impl
Yes, you want the WWN to stay constant. That doesn't mean it should
necessarily be the same physical box. Nor does it mean it should be a
system that comes with a WWN assigned to by the manufacturer.
I think I'm confusing myself and people. I have a WWN. By definition it
should be unique value.
Yes, you want the WWN to stay constant. That doesn't mean it should
necessarily be the same physical box. Nor does it mean it should be a
system that comes with a WWN assigned to by the manufacturer.
I think I'm confusing myself and people. I have a WWN. By definition it
should be unique value. A
In article <[EMAIL PROTECTED]> you write:
>
>Here's one possibility, it adds a a wrap/nowrap field that goes beside the
>wait/nowait field, so you would have:
>
>ftp stream tcp nowait wrap root /usr/libexec/ftpd ftpd -l
Breaking backwards compatability is evil. Do somethin
In article <199906242353.taa06...@smtp4.erols.com> you write:
>
>Here's one possibility, it adds a a wrap/nowrap field that goes beside the
>wait/nowait field, so you would have:
>
>ftp stream tcp nowait wrap root /usr/libexec/ftpd ftpd -l
Breaking backwards compatability is
> :anybody done any work on a utility for growing ufs filesystems?
> :
> :aaron
>
> It has been brought up a couple of times but nobody has tried
> to do actually it. Personally, I think it would be a doable
> project if someone wanted to have a go at it - to allow a filesystem
>
> :anybody done any work on a utility for growing ufs filesystems?
> :
> :aaron
>
> It has been brought up a couple of times but nobody has tried
> to do actually it. Personally, I think it would be a doable
> project if someone wanted to have a go at it - to allow a filesystem
>
:anybody done any work on a utility for growing ufs filesystems?
:
:aaron
It has been brought up a couple of times but nobody has tried
to do actually it. Personally, I think it would be a doable
project if someone wanted to have a go at it - to allow a filesystem
to be grown or
As Matthew Jacob wrote ...
> >
> > FYI: The Compaq HSG80 Fibrechannel RAID controllers have their
> > WWN in NVRAM. One is supposed to get the WWN from a label on the *cabinet*
> > into the HSG controller. This allows for easy hardware swap in case of
> > hardware grief.
>
> Yes, if you want th
:anybody done any work on a utility for growing ufs filesystems?
:
:aaron
It has been brought up a couple of times but nobody has tried
to do actually it. Personally, I think it would be a doable
project if someone wanted to have a go at it - to allow a filesystem
to be grown or s
As Matthew Jacob wrote ...
> >
> > FYI: The Compaq HSG80 Fibrechannel RAID controllers have their
> > WWN in NVRAM. One is supposed to get the WWN from a label on the *cabinet*
> > into the HSG controller. This allows for easy hardware swap in case of
> > hardware grief.
>
> Yes, if you want the
there are several
greg lehey has been collecting them.
julian
On Fri, 25 Jun 1999, Aaron Smith wrote:
> anybody done any work on a utility for growing ufs filesystems?
>
> aaron
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the mes
there are several
greg lehey has been collecting them.
julian
On Fri, 25 Jun 1999, Aaron Smith wrote:
> anybody done any work on a utility for growing ufs filesystems?
>
> aaron
>
>
> To Unsubscribe: send mail to majord...@freebsd.org
> with "unsubscribe freebsd-hackers" in the body of the
anybody done any work on a utility for growing ufs filesystems?
aaron
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
anybody done any work on a utility for growing ufs filesystems?
aaron
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
On Fri, 25 Jun 1999 20:12:01 BST, David Malone writes:
>This isn't so much a conf format change, as a conf format extension.
>It is the same type of extension as was added to support max child
>and max child per minute - which aren't a standard inetd feature.
>All old inetd.conf files remain valid
On Fri, 25 Jun 1999 20:12:01 BST, David Malone writes:
>This isn't so much a conf format change, as a conf format extension.
>It is the same type of extension as was added to support max child
>and max child per minute - which aren't a standard inetd feature.
>All old inetd.conf files remain valid.
> >
> > Really? Couldn't the Port WWN change and the Node WWN stay constant? I
> > mean, yes, for FC controllers that have WWN in the 0x2 range,
> > the Node WWN is 0x20... and the Port is 0x22... but it seems like this is
> > a soft relationship- you *could* have Port && Node unique
> >
> > Really? Couldn't the Port WWN change and the Node WWN stay constant? I
> > mean, yes, for FC controllers that have WWN in the 0x2 range,
> > the Node WWN is 0x20... and the Port is 0x22... but it seems like this is
> > a soft relationship- you *could* have Port && Node unique
On Fri, Jun 25, 1999 at 11:02:04AM -0700, Aaron Smith wrote:
> i have no problem with -w options, but i am still surprised that you want
> to go ahead with the conf format change.
This isn't so much a conf format change, as a conf format extension.
It is the same type of extension as was added to
On Fri, Jun 25, 1999 at 11:02:04AM -0700, Aaron Smith wrote:
> i have no problem with -w options, but i am still surprised that you want
> to go ahead with the conf format change.
This isn't so much a conf format change, as a conf format extension.
It is the same type of extension as was added to
On Tue, 22 Jun 1999, Aaron Smith wrote:
> (also see http://www.arctic.org/~aaron/tips/freebsd-serial-console)
Great page, thank you. One suggestion I have is that you make the
distinction between getting a login prompt on the com console and getting
the boot messages to display on the co
On Tue, 22 Jun 1999, Aaron Smith wrote:
> (also see http://www.arctic.org/~aaron/tips/freebsd-serial-console)
Great page, thank you. One suggestion I have is that you make the
distinction between getting a login prompt on the com console and getting
the boot messages to display on the com
>
> FYI: The Compaq HSG80 Fibrechannel RAID controllers have their
> WWN in NVRAM. One is supposed to get the WWN from a label on the *cabinet*
> into the HSG controller. This allows for easy hardware swap in case of
> hardware grief.
Yes, if you want the WWN to stay constant.
-matt
To Uns
As Matthew Jacob wrote ...
> Yes. The Solaris drivers use the 'localetheraddr' function, or's in 1<<60
> and then HBA instance # << 48 to make a NAA_IEEE port identifier.
>
> >
> > The main issue, I think, is that of persistence. How persistent do
> > you want it? I'd bet that no matter wha
>
> FYI: The Compaq HSG80 Fibrechannel RAID controllers have their
> WWN in NVRAM. One is supposed to get the WWN from a label on the *cabinet*
> into the HSG controller. This allows for easy hardware swap in case of
> hardware grief.
Yes, if you want the WWN to stay constant.
-matt
To Unsu
As Matthew Jacob wrote ...
> Yes. The Solaris drivers use the 'localetheraddr' function, or's in 1<<60
> and then HBA instance # << 48 to make a NAA_IEEE port identifier.
>
> >
> > The main issue, I think, is that of persistence. How persistent do
> > you want it? I'd bet that no matter what
Lemme explain my situation.
I have a FreeBSD box sitting behind a Microsoft Proxy Server. I want the
FreeBSD box to be able to reach the internet via SOCKS. I have downloaded,
installed, and played a great deal with this software. I can't seem to get
it to work. Could someone help me out? Po
Lemme explain my situation.
I have a FreeBSD box sitting behind a Microsoft Proxy Server. I want the
FreeBSD box to be able to reach the internet via SOCKS. I have downloaded,
installed, and played a great deal with this software. I can't seem to get
it to work. Could someone help me out? Pos
First of all, I would like to thank everyone who helped me with my NIS
problems(A few days back). It is up and running now. For anyone else
attempting to set up NIS, what really helped me was this website:
http://www.realtime.net/sculpture/nis-startup.html
For all those questioning the security
First of all, I would like to thank everyone who helped me with my NIS
problems(A few days back). It is up and running now. For anyone else
attempting to set up NIS, what really helped me was this website:
http://www.realtime.net/sculpture/nis-startup.html
For all those questioning the security
On Fri, 25 Jun 1999 16:05:05 +0200, Sheldon Hearn writes:
>We'll also end up with an inetd that _can_ wrap if it's told to (-w
>and -ww). So we end up offering a better super-server than we had
>before, with no backward compatibility problems, and no additional
>incompatibilities with other system
On Fri, 25 Jun 1999 16:05:05 +0200, Sheldon Hearn writes:
>We'll also end up with an inetd that _can_ wrap if it's told to (-w
>and -ww). So we end up offering a better super-server than we had
>before, with no backward compatibility problems, and no additional
>incompatibilities with other systems
> On Thu, 24 Jun 1999, Matthew Jacob wrote:
>
> > Specifically in this case a Node WWN for fibre channel fabrics that does
> > not depend upon an assigned WWN in any particular Fibre Channel card
> > (multipathing might make it desirable to have a synthetic Node WWN that
> > can also be passed t
> On Thu, 24 Jun 1999, Matthew Jacob wrote:
>
> > Specifically in this case a Node WWN for fibre channel fabrics that does
> > not depend upon an assigned WWN in any particular Fibre Channel card
> > (multipathing might make it desirable to have a synthetic Node WWN that
> > can also be passed to
Hi,
I believe someone working on NEWBUS-ifying ISA-PnP.
How will they implement it?
I think current framework is like this.
++ ++
...|ISA DEV | |ISA-hint|<-This device provides
++ ++ what device is connected
| ||
Hi,
I believe someone working on NEWBUS-ifying ISA-PnP.
How will they implement it?
I think current framework is like this.
++ ++
...|ISA DEV | |ISA-hint|<-This device provides
++ ++ what device is connected
| ||
> On Thu, 24 Jun 1999 23:41:34 -0700 (PDT)
> Matthew Jacob <[EMAIL PROTECTED]> wrote:
>
> > More generally a system unique identifier available early (pre mountroot)
> > could be useful for a number of things. Why're you asking?
>
> The intended usage:
>
> (1) Could influence where it
> On Thu, 24 Jun 1999 23:41:34 -0700 (PDT)
> Matthew Jacob wrote:
>
> > More generally a system unique identifier available early (pre mountroot)
> > could be useful for a number of things. Why're you asking?
>
> The intended usage:
>
> (1) Could influence where it is stored.
Yes.
>
On Fri, 25 Jun 1999, Eduardo E. Horvath wrote:
>We've been hashing this issue out quite a bit. Since a Fibre Channel card
>is by definition a fibre channel controller, each card should have a
>unique WWN that is used for the node WWN. If you swap a controller, the
>node WWN should change.
I've
On Fri, 25 Jun 1999, Eduardo E. Horvath wrote:
>We've been hashing this issue out quite a bit. Since a Fibre Channel card
>is by definition a fibre channel controller, each card should have a
>unique WWN that is used for the node WWN. If you swap a controller, the
>node WWN should change.
I've
>
> > > static struct sockaddr_in servaddr;
> >
> > This needs to be a valid structure in USER space, not kernel.
>
> OK. I suspected as much. Question is: how do I open a connection from
> KERNEL space?
You don't.
If you're really desperate to do this, you'll have to patch _all_ of
the s
>
> > > static struct sockaddr_in servaddr;
> >
> > This needs to be a valid structure in USER space, not kernel.
>
> OK. I suspected as much. Question is: how do I open a connection from
> KERNEL space?
You don't.
If you're really desperate to do this, you'll have to patch _all_ of
the sy
On Fri, 25 Jun 1999, Ladavac Marino wrote:
> > -Original Message-
> > From: Dan Seguin [SMTP:[EMAIL PROTECTED]]
> > Sent: Friday, June 25, 1999 5:26 PM
> > To: Brian F. Feldman
> > Cc: FreeBSD Hackers
> > Subject:Re: Connect and so on..
> > As I said earlier in this pos
On Fri, 25 Jun 1999, Ladavac Marino wrote:
> > -Original Message-
> > From: Dan Seguin [SMTP:d...@texar.com]
> > Sent: Friday, June 25, 1999 5:26 PM
> > To: Brian F. Feldman
> > Cc: FreeBSD Hackers
> > Subject:Re: Connect and so on..
> > As I said earlier in this post, I
> -Original Message-
> From: Dan Seguin [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, June 25, 1999 5:26 PM
> To: Brian F. Feldman
> Cc: FreeBSD Hackers
> Subject: Re: Connect and so on..
>
> As I said earlier in this post, I need to open a connection to the
> outside
> (presumably) f
> -Original Message-
> From: Dan Seguin [SMTP:d...@texar.com]
> Sent: Friday, June 25, 1999 5:26 PM
> To: Brian F. Feldman
> Cc: FreeBSD Hackers
> Subject: Re: Connect and so on..
>
> As I said earlier in this post, I need to open a connection to the
> outside
> (presumably) from
On Wed, 23 Jun 1999, Brian F. Feldman wrote:
> On Wed, 23 Jun 1999, Dan Seguin wrote:
>
> >
[snip]
> > I use the calling proc's table as it is passed to the system call, and am
> > trying to call socket and connect as if the user process originally called
> > them one by one (from userland s
On Wed, 23 Jun 1999, Brian F. Feldman wrote:
> On Wed, 23 Jun 1999, Dan Seguin wrote:
>
> >
[snip]
> > I use the calling proc's table as it is passed to the system call, and am
> > trying to call socket and connect as if the user process originally called
> > them one by one (from userland sy
On Fri, Jun 25, 1999 at 04:05:05PM +0200, Sheldon Hearn wrote:
>
> On Fri, 25 Jun 1999 09:31:26 -0400, Keith Stevenson wrote:
>
> > What is possible now that wasn't possible with tcpd from the ports
> > collection? Why incorporate libwrap (and make our inetd functionally
> > different from ever
On Fri, Jun 25, 1999 at 04:05:05PM +0200, Sheldon Hearn wrote:
>
> On Fri, 25 Jun 1999 09:31:26 -0400, Keith Stevenson wrote:
>
> > What is possible now that wasn't possible with tcpd from the ports
> > collection? Why incorporate libwrap (and make our inetd functionally
> > different from every
On Fri, 25 Jun 1999 09:31:26 -0400, Keith Stevenson wrote:
> What is possible now that wasn't possible with tcpd from the ports
> collection? Why incorporate libwrap (and make our inetd functionally
> different from everyone else's) instead of bringing tcpd into the base
> system?
If we _don'
On Fri, 25 Jun 1999 09:31:26 -0400, Keith Stevenson wrote:
> What is possible now that wasn't possible with tcpd from the ports
> collection? Why incorporate libwrap (and make our inetd functionally
> different from everyone else's) instead of bringing tcpd into the base
> system?
If we _don't
On Fri, Jun 25, 1999 at 02:50:34PM +0200, Sheldon Hearn wrote:
>
> On Fri, 25 Jun 1999 05:44:06 MST, Aaron Smith wrote:
>
> > could you please restate the argument for this? i still haven't heard a
> > decent reason for this sort of conf format perturbation.
>
> I'm so tempted to say "me too".
On Fri, Jun 25, 1999 at 02:50:34PM +0200, Sheldon Hearn wrote:
>
> On Fri, 25 Jun 1999 05:44:06 MST, Aaron Smith wrote:
>
> > could you please restate the argument for this? i still haven't heard a
> > decent reason for this sort of conf format perturbation.
>
> I'm so tempted to say "me too". :
Couple of notes:
o Taavi has done work on the FreeBSD port
o The driver at ftp://ftp.wheaton.edu has several bugs
in it which I think both Soren and Taavi have adjuste for.
johnh...
Quoting "Soren S. Jorvang" <[EMAIL PROTECTED]>:
> On Fri, Jun 25, 1999 at 09:18:53AM +0200, Jesper Skriver wrote
Couple of notes:
o Taavi has done work on the FreeBSD port
o The driver at ftp://ftp.wheaton.edu has several bugs
in it which I think both Soren and Taavi have adjuste for.
johnh...
Quoting "Soren S. Jorvang" :
> On Fri, Jun 25, 1999 at 09:18:53AM +0200, Jesper Skriver wrote:
> > On Thu, Jun 24
On Fri, 25 Jun 1999 05:44:06 MST, Aaron Smith wrote:
> could you please restate the argument for this? i still haven't heard a
> decent reason for this sort of conf format perturbation.
I'm so tempted to say "me too". :-)
John Baldwin has suggested that he had functionality with inetd + tcpd
On Fri, 25 Jun 1999 05:44:06 MST, Aaron Smith wrote:
> could you please restate the argument for this? i still haven't heard a
> decent reason for this sort of conf format perturbation.
I'm so tempted to say "me too". :-)
John Baldwin has suggested that he had functionality with inetd + tcpd
t
On Fri, 25 Jun 1999 10:14:48 +0200, Sheldon Hearn writes:
>I think I prefer the suggestion I saw from someone else, which would
>allow
>
>ftpstream tcp nowait/10/10/wrap root ...
>
>This can be done in such a way as to be backward compatible. Looks like
>something for the week-end, if I
On Fri, 25 Jun 1999 10:14:48 +0200, Sheldon Hearn writes:
>I think I prefer the suggestion I saw from someone else, which would
>allow
>
>ftpstream tcp nowait/10/10/wrap root ...
>
>This can be done in such a way as to be backward compatible. Looks like
>something for the week-end, if I c
hello all ~
I never posted to this list - maybe once, but I learned. I follow
threads of brilliant minds at work and I read - and I am amazed by
creative and complex issues which are resolved by a group of geeky
greats. So - before I begin to drag this out - I wanted to share in
agreement with M
hello all ~
I never posted to this list - maybe once, but I learned. I follow
threads of brilliant minds at work and I read - and I am amazed by
creative and complex issues which are resolved by a group of geeky
greats. So - before I begin to drag this out - I wanted to share in
agreement with Mr
1 - 100 of 122 matches
Mail list logo
