Re: wormcontrol write speed

[Soren Schmidt]

It seems Luigi Rizzo wrote:
> > Anyhow, I have some changes to the worm stuff, it needs to be dealt with
> > to handle modern HW, and to deal with all the possible block formats
> > thats possible on a CD nowadays. It will probably mean the death of
> > the worm stuff as is now, but I'm the last user anyways so
> 
> NO! There is me as well

For what ?? -stable ?? I wont touch that one...
If its for the old wd driver, it'll ofcause stay around until that is
gone too :)

Or have I missed something ??

-Soren


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: wormcontrol write speed

[Luigi Rizzo]

> Anyhow, I have some changes to the worm stuff, it needs to be dealt with
> to handle modern HW, and to deal with all the possible block formats
> thats possible on a CD nowadays. It will probably mean the death of
> the worm stuff as is now, but I'm the last user anyways so

NO! There is me as well

cheers
luigi

---+-
  Luigi RIZZO, [EMAIL PROTECTED]  . Dip. di Ing. dell'Informazione
  http://www.iet.unipi.it/~luigi/  . Universita` di Pisa
  TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy)

  http://www.iet.unipi.it/~luigi/ngc99/
  First International Workshop on Networked Group Communication  
---+-


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: what is devfs?

[Warner Losh]

In message <[EMAIL PROTECTED]> Wes Peters writes:
: Interrupt, DMA, I/O settings, promiscuous operation, baud rate and parity,
: etc.  Any little thing a device driver might desire...

I had been specifically thinking of things more obscure like the
WNETID for wavelan cards, the frequency ranges for the bktr cards, the
frequency pattern for an ibm lan entry driver I never finished, the
preferred media type for ethernet drivers, the calibrated frequency
for clock boards/parts, the mixer settings from sound drivers, etc,
etc, etc.

These things are closely related to the more prosaic things like I/O
range, IRQ, DRQ, etc.  I'm not sure that the differences between
"configuration" data and other attributes not necessarily common to a
bus are significant enough to warrant special treatment.  I gotta find 
some time to get into this more deeply.  Maybe after pccard has grown
cardbus support :-).

And the sysctl mechanism might not be a bad one to make persistant.
However, there are some issues with having multiple instances of
sysctls that would need to be generically solved at the same time.

There, the whole problem of the persistant parts of devfsd has been
reduced to basically /etc/rc.sysctl which should make the "we don't
need devfsd to do persitance" folks happy. :-)

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: wormcontrol write speed

[Soren Schmidt]

It seems Daniel O'Connor wrote:
> 
> On 22-Sep-99 Soren Schmidt wrote:
> > > Are there any way to make wormcontrol burns cds at 4x speed?
> 
> >  Not directly, but your driver _should_ use the max speed as default.
> >  You could ad a command to force the drive to max speed in the driver
> >  though...
> 
> IMHO there should be a way to force it..
> 
> You can get 8x drives and 6x media.. Not a good idea put them together unless
> you change the write speed.

Right, but all the drives I've seen falls back from max speed if the medium
is crappy, that is not to say that they chose the right speed though :)

Anyhow, I have some changes to the worm stuff, it needs to be dealt with
to handle modern HW, and to deal with all the possible block formats
thats possible on a CD nowadays. It will probably mean the death of
the worm stuff as is now, but I'm the last user anyways so

-Soren


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: what is devfs?

[Wes Peters]

Warner Losh wrote:
> 
> In message <[EMAIL PROTECTED]> Wes Peters writes:
> : Is there any possibility of creating a database of devfs perms that gets
> : loaded into kernel-accessible data space by the loader before boot?  Once
> : the system is up, devfsd could take over, monitoring and updating the
> : state of devfs and this database, and the perms would come up as they were
> : last set, modulo the cycle time of devfsd.
> 
> Hmmm.  That's an interesting possibility.  If we could load this
> database from the boot loader, then we could have a good snapshot of
> the user's desired persistance.  This would allow the kernel to have a
> template for the permissions as the devices are coming up...
> Interesting possibilities here.  This sounds a lot like the notion
> that I've had for a while of having a Xdefaults-like database to pass
> parameters to device instances.  This would be just another
> parameter...  Might not even need a devfsd in a case like this, if you
> don't mind your /dev tree being configured in a manner that is
> different than in prior versions.
> 
> Or in other words, why stop with just the owner, group, flags and
> permission bits.  Why not save other things as well...

Interrupt, DMA, I/O settings, promiscuous operation, baud rate and parity,
etc.  Any little thing a device driver might desire...

-- 
"Where am I, and what am I doing in this handbasket?"

Wes Peters Softweyr LLC
[EMAIL PROTECTED]   http://softweyr.com/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: wormcontrol write speed

[Daniel O'Connor]

On 22-Sep-99 Soren Schmidt wrote:
> > Are there any way to make wormcontrol burns cds at 4x speed?

>  Not directly, but your driver _should_ use the max speed as default.
>  You could ad a command to force the drive to max speed in the driver
>  though...

IMHO there should be a way to force it..

You can get 8x drives and 6x media.. Not a good idea put them together unless
you change the write speed.

---
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: wormcontrol write speed

[Soren Schmidt]

It seems Paulo Fragoso wrote:
> Hi,
> 
> I'm using one atapi-cdrw (CREATIVE CD-RW RW4224E/1.36) and works fine but
> I don't know change speed to 4x, now I'm burning at double speed (I'm
> spending 37min to burn one full cd). I've got other unit (YAMAHA-SCSI)
> which spends 17min for a full cd but using cdrecord speed=4.
> 
> Are there any way to make wormcontrol burns cds at 4x speed?

Not directly, but your driver _should_ use the max speed as default.
You could ad a command to force the drive to max speed in the driver
though...

-Soren


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: missing files with NFSv3 and Solaris2.7 machine...

[Matthew Dillon]

:As I recall, we had two alternatives. First, knowingly not comply to
:the spec, because Solaris doesn't handle it. Second, change the way
:we read directories so we can avoid doing things in the way Solaris
:can't handle. The latter is a very sore spot, and not trivial.
:
:I was under the impression, though, that Matthew Dillon had done
:something about it.

I haven't done anything about it yet.  I haven't been able to figure
out whether the server can safely ignore checking the file revision
(which is what is causing it to report NFSERR_BAD_COOKIE).

Just for kicks, try the patch below.  What I'm not sure about is whether
the VOP_READDIR() call the server makes can get out of sync with what
was reported to the client in the past when a file is created or deleted
in the directory.  What I mean by 'out of sync' here is whether it
can create a situation where it reports directory entries in one directory
block that had previously been reported in another.

The other case I'm not sure about is what happens when the directory
on the server has a white-out directory entry at the very beginning
of a block, causing it to report a cookie that occurs a little later
in the block, and then a file is created on the server which converts 
that white-out entry with a real entry.  If the client re-requests
the directory block it will give the server the cookie for what is now
the second file in the directory block, not the first file.   The server
then ignores the directory entry in that directory block that had
just been created (that used to be white-out), and generates a reply
to the client that is no longer in sync for that directory block with
what the server would report if the entire directory was rescanned.

-Matt
Matthew Dillon 
<[EMAIL PROTECTED]>

Index: nfs/nfs_serv.c
===
RCS file: /home/ncvs/src/sys/nfs/nfs_serv.c,v
retrieving revision 1.85
diff -u -r1.85 nfs_serv.c
--- nfs_serv.c  1999/09/17 05:57:57 1.85
+++ nfs_serv.c  1999/09/22 03:51:36
@@ -3032,11 +3032,13 @@
nqsrv_getl(vp, ND_READ);
if (v3) {
error = getret = VOP_GETATTR(vp, &at, cred, procp);
+#if 0
/*
 * XXX This check may be too strict for Solaris 2.5 clients.
 */
if (!error && toff && verf && verf != at.va_filerev)
error = NFSERR_BAD_COOKIE;
+#endif
}
if (!error)
error = nfsrv_access(vp, VEXEC, cred, rdonly, procp, 0);
@@ -3312,11 +3314,13 @@
goto nfsmout;
}
error = getret = VOP_GETATTR(vp, &at, cred, procp);
+#if 0
/*
 * XXX This check may be too strict for Solaris 2.5 clients.
 */
if (!error && toff && verf && verf != at.va_filerev)
error = NFSERR_BAD_COOKIE;
+#endif
if (!error) {
nqsrv_getl(vp, ND_READ);
error = nfsrv_access(vp, VEXEC, cred, rdonly, procp, 0);


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

RE: SMP motherboards

[Daniel O'Connor]

On 22-Sep-99 Mark Newton wrote:
>  Has anyone had any problems running FreeBSD-SMP on Intel GX-chipset
>  motherboards?

I ran 3.2-RELEASE on a friends GX board. It was an Asus board, and had 5 PCI
slots, an inbuilt 7896 and onboard 10/100 ethernet. (I can't remember the model
number, I can find out if you want to know)

It seemed to work perfectly (SMP enabled etc etc).. I did a build world and ran
X on it.

---
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

SMP motherboards

[Mark Newton]

Has anyone had any problems running FreeBSD-SMP on Intel GX-chipset
motherboards?

Conversely, does anyone have any recommendations for other motherboards
to buy?

- mark


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: IPv6 on 3.2 STABLE ?

[Daniel C. Sobral]

stefan parvu wrote:
> 
> Hello,
> 
> Last night I worked to port some code to FreeBSD 3.2 Stable.
> I was curious about one fact: on  there is no any in6_addr
> support for IPv6. Am I wrong ? FreeBSD does not support IPv6 ?

Sure it does. It just doesn't come out of the box with it because
there were too many choices. There were three IPv6 stacks with
FreeBSD versions, and the core team decided to wait until one of
these stacks came out the "winner" before committing it to the tree.
It should be clear that committing to any one too soon would
stagnate FreeBSD development for the others.

Meanwhile, anyone could just grab the source for any of these stacks
and install it.

Alas, they finally decided to join their efforts, which goes to show
that the core team decision was on the mark. It's my impression that
we'll have IPv6 stack on -stable for the next release.

--
Daniel C. Sobral(8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]

"Thus, over the years my wife and I have physically diverged. While
I have zoomed toward a crusty middle-age, she has instead clung
doggedly to the sweet bloom of youth. Naturally I think this unfair.
Yet, if it was the other way around, I confess I wouldn't be happy
either."




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: IPv6 on 3.2 STABLE ?

[Ollivier Robert]

According to Andy Doran:
> FWIW, the KAME implementation was integrated into NetBSD-current around
> the start of July.

Thanks for the correction ! Nice to ehar that.
-- 
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED]
FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep  9 00:20:51 CEST 1999



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: missing files with NFSv3 and Solaris2.7 machine...

[Daniel C. Sobral]

"David E. Cross" wrote:
> 
> Count me as one of the ones who do not accept this answer.  I realize that

It was not the "answer" which was not accepted. Someone actually
argued it could not be an NFS protocol bug because the Solaris stack
was the reference implementation, ergo it does not have bugs. Are
you party to that line of thought? :-)

> the Sun code may very well have bugs in it.  I also know that what we have
> right now "doesn't work" with sun clients.  I believe that we have made
> modifications to our TCP/IP stack  code to deal with windows machines who
> are not to spec, could we not do the same for sun and NFS?

As I recall, we had two alternatives. First, knowingly not comply to
the spec, because Solaris doesn't handle it. Second, change the way
we read directories so we can avoid doing things in the way Solaris
can't handle. The latter is a very sore spot, and not trivial.

I was under the impression, though, that Matthew Dillon had done
something about it.

> Alternately, we have a sun support contract, and if someone could detail to
> me exactly how they are not compliant I will try to file a bug report.

I think that would be desirable. It's in the archives, of course,
but I cannot recall even on which mailing list, or who originated
the thread. Matthew Dillon was in it, but he is in a lot of threads,
and they tend to be long threads. Better just wait until Dillon
shows up and comment on this.

--
Daniel C. Sobral(8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]

"Thus, over the years my wife and I have physically diverged. While
I have zoomed toward a crusty middle-age, she has instead clung
doggedly to the sweet bloom of youth. Naturally I think this unfair.
Yet, if it was the other way around, I confess I wouldn't be happy
either."




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: what is devfs?

[Warner Losh]

In message <[EMAIL PROTECTED]> Wes Peters writes:
: Is there any possibility of creating a database of devfs perms that gets
: loaded into kernel-accessible data space by the loader before boot?  Once
: the system is up, devfsd could take over, monitoring and updating the
: state of devfs and this database, and the perms would come up as they were
: last set, modulo the cycle time of devfsd.

Hmmm.  That's an interesting possibility.  If we could load this
database from the boot loader, then we could have a good snapshot of
the user's desired persistance.  This would allow the kernel to have a 
template for the permissions as the devices are coming up...
Interesting possibilities here.  This sounds a lot like the notion
that I've had for a while of having a Xdefaults-like database to pass
parameters to device instances.  This would be just another
parameter...  Might not even need a devfsd in a case like this, if you 
don't mind your /dev tree being configured in a manner that is
different than in prior versions.

Or in other words, why stop with just the owner, group, flags and
permission bits.  Why not save other things as well...

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: how to shut down a TCP connection

[Brian Dean]

> :Does anyone know how I can manually shutdown the above connection on
> :'vger' short of waiting a really long time or rebooting?
> :
> :Thanks,
> :-Brian
> :-- 
> :Brian Dean   [EMAIL PROTECTED]
> 
> Turn on keepalives and set the parameters really low so the connection
> times out after a couple of minutes.  Experiment.  Remember that the
> below will effect all your TCP connections, so don't make the timeout
> too low.
> 
>   sysctl -w net.inet.tcp.always_keepalive=1
>   sysctl -w net.inet.tcp.keepintvl=60
>   sysctl -w net.inet.tcp.keepinit=60
>   sysctl -w net.inet.tcp.keepidle=300
> 
> If the FreeBSD side is still in the ESTABLISHED state, it is not
> getting a FIN or not getting a proper FIN.
> 
>   -Matt
>   Matthew Dillon 
>   <[EMAIL PROTECTED]>

The above settings did some odd things to my existing connections but
I get the idea.  I think the values for some of those parameters are
expected in milliseconds, but I think you intended seconds.  I will
adjust them accordingly and experiment as needed.  Thanks for the
idea.

Too bad we don't have a command, though, that would do something like:

inetadm shutdown tcp:5000

which would initiate a shutdown of tcp port 5000.  I know ... patches :)

Thanks again,
-Brian
-- 
Brian Dean  [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: nawk vs gawk? (was Re: GNU GLOBAL)

[Pedro Fernando Giffuni]

The three of them are on the ports tree. mawk and gawk are GPL'd, nawk
is not. 
I'm not sure if nawk is fully POSIX compliant but it is the "new" awk
described in Kernighans' book. 
Yes mawk is the fastest of the three, but I'm not sure if speed is the
most important feature in a scripting language. Gawk has more features,
but I saw a test somewhere that showed a bug in the FreeBSD version. I
can dig it up if someone is really interested.


Pedro.


[EMAIL PROTECTED] wrote:
> 
> Pedro Fernando Giffuni wrote:
> 
> >Yes, I know that gawk is faster, but isn't nawk the one true (new) awk?
> 
> >From my experience, the awk downloadable from Kernighan's web page
> (should be "nawk", shouldn't it?) is a little bit faster on average
> than gawk.  Probably not much that it would really matter anyways.
> I've heard that another implementation, Mawk is still faster but
> I haven't tried it yet.
> 
> mkb


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: Infrared trackball diffs available

[Kazutaka YOKOTA]

>A few days ago I was at Office Max and bought an InterAct "Web.Remote
>professional".  For those of you who don't know, its an infrared
>remote control which contains a trackball, two trackball buttons, and
>an 18-key keypad.  It was a pretty good deal for $17US.
>
>My ultimate goal is to use it to control my mp3 playing FreeBSD server.
>
>As a result, I spent time this weekend figuring out the protocol it uses
>and modified moused to work with it.  It's a completely non-standard
>6-byte-per-packet protocol, but was fairly easy to integrate into the 
>existing moused daemon.
>
>If anyone would like the diffs to the daemon, please let me know and
>I'd be happy to send them out.
>
>The current moused supports up to 31 buttons on a device.  However, the
>level 1 sysmouse protocol only supports 10.  As a result, I'm still
>trying
>to decide how to handle the keypad on the remote.
>
>I'm probably going to follow the x10netremote example, but would
>appreciate any suggestions that people have.

Probably moused is getting too bloat nowadays.

I rather think we had better start thinking about creating a new
daemon for remote control devices, including X10Remote and this
Web.Remote.  I expect this would be more logical, as these remotes may
use proprietary packet formats, which may not comfortably fit into the
way moused processes mouse data stream.

We can use MOUSE_XXX ioctl commands to feed mouse/trackball part of
data from the remotes to the console driver (and subsequently make it
available via /dev/sysmouse).  Key data can be made available to
application programs (and the X server and client programs, perhaps)
via FIFO, like x10remote does, or in any other means.

I don't think overloading additional data from the remote control onto
mouse data so that it would go through MOUSE_XXX ioctl commands and
/dev/sysmouse (thus we don't need the second data channel) is too
much; sooner or later we shall encounter a new remote control device about 
which we can no longer pretend it is a mouse-like device this way.

Ok, the application program will read data of the remote control
device from two separate channels: mouse/trackball data via
/dev/sysmouse and key data, and other additional info from something
else.  Will that be a problem?  No, I wouldn't think so.  The
mouse/trackball part of the remote should act like the ordinary
pointing device :-)

If the mouse/trackball part performs more than the
pointing-device-like function, such data should go through the second
channel together with key data and else, as it will probably need to
be parsed/interpreted together with the data from other parts of the
device.

The `remote' daemon would be able to share code with or copy some code
from the existing moused if necessary.

Kazu



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: how to shut down a TCP connection

[Matthew Dillon]

:Hi,
:
:I'm doing TCP development on a custom operating system that I've
:written and am using my FreeBSD box for testing my TCP stack.  I'm in
:the early stages right now and I have a lot of bugs.  One of my bugs
:is that I shut down a connection on my end but I'm doing something
:wrong and the connection on the FreeBSD side stays up, i.e.:
:
:[bsd@vger]:/net- netstat
:Active Internet connections
:Proto Recv-Q Send-Q Local Address Foreign Address   (state)
:tcp0  0 vger.telnet   bos.5000  ESTABLISHED
:
:'vger' is my FreeBSD machine and 'bos' is my experimental OS.  The
:connecton on 'bos' at this point is actually closed.
:
:Does anyone know how I can manually shutdown the above connection on
:'vger' short of waiting a really long time or rebooting?
:
:Thanks,
:-Brian
:-- 
:Brian Dean [EMAIL PROTECTED]

Turn on keepalives and set the parameters really low so the connection
times out after a couple of minutes.  Experiment.  Remember that the
below will effect all your TCP connections, so don't make the timeout
too low.

sysctl -w net.inet.tcp.always_keepalive=1
sysctl -w net.inet.tcp.keepintvl=60
sysctl -w net.inet.tcp.keepinit=60
sysctl -w net.inet.tcp.keepidle=300

If the FreeBSD side is still in the ESTABLISHED state, it is not
getting a FIN or not getting a proper FIN.

-Matt
Matthew Dillon 
<[EMAIL PROTECTED]>


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: nawk vs gawk? (was Re: GNU GLOBAL)

[token]

Pedro Fernando Giffuni wrote:

>Yes, I know that gawk is faster, but isn't nawk the one true (new) awk?

>From my experience, the awk downloadable from Kernighan's web page
(should be "nawk", shouldn't it?) is a little bit faster on average
than gawk.  Probably not much that it would really matter anyways.
I've heard that another implementation, Mawk is still faster but
I haven't tried it yet.

mkb


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: what is devfs?

[Wes Peters]

Warner Losh wrote:
> 
> Devices must failsafe from a security point of view in the absense of
> a devfsd.  Otherwise there will extreme opposition from the security
> officer.  This means 0600 or more restrictive permissions.  While it
> doesn't happen often, it must be designed for.  Otherwise you've
> replaced a secure, predictible system with an insecure one, which is
> not acceptible at all in the base FreeBSD product.
> 
> How permissions are saved, devices are given out for use I don't care
> too much about so long as it is secure.
> 
> In general, it is very hard to secure a system where things aren't
> predictable.

Is there any possibility of creating a database of devfs perms that gets
loaded into kernel-accessible data space by the loader before boot?  Once
the system is up, devfsd could take over, monitoring and updating the
state of devfs and this database, and the perms would come up as they were
last set, modulo the cycle time of devfsd.

-- 
"Where am I, and what am I doing in this handbasket?"

Wes Peters Softweyr LLC
[EMAIL PROTECTED]   http://softweyr.com/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: IPv6 on 3.2 STABLE ?

[Andy Doran]

On Wed, 22 Sep 1999, Ollivier Robert wrote:

> NetBSD & OpenBSD has decided to use one of the last two for themselves
> (although I always forgot who took what -- I think NetBSD took INRIA and
> OpenBSD NRL but I could be wrong).

FWIW, the KAME implementation was integrated into NetBSD-current around
the start of July.

- ad



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: IPv6 on 3.2 STABLE ?

[Ollivier Robert]

According to stefan parvu:
> I was curious about one fact: on  there is no any in6_addr
> support for IPv6. Am I wrong ? FreeBSD does not support IPv6 ?

Our Japanese friends are working to integrate IPv6 into current. For -STABLE,
you have at least 3 implementations that works fairly well (although I've
tried only the first two):

- KAME IPv6 (with IPsec and soon Mobile/IPv6)
  
  This is the one that will be in CURRENT. I use it on 3.1 and it is my
  connection to the 6BONE.

- INRIA IPv6 (with authentication part of IPsec and Mobile/IPv6)
  
  Works fine, especially with mobility.

- NRL IPv6 / IPsec. I haven't tried it but I heard it works well.

NetBSD & OpenBSD has decided to use one of the last two for themselves
(although I always forgot who took what -- I think NetBSD took INRIA and
OpenBSD NRL but I could be wrong).

KAME will become the unified-IPv6 for *BSD.

One of the goals for 4.0 _is_ having IPv6 as standard. For -STABLE it is very
easy to get and install it.
-- 
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED]
FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep  9 00:20:51 CEST 1999



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

how to shut down a TCP connection

[Brian Dean]

Hi,

I'm doing TCP development on a custom operating system that I've
written and am using my FreeBSD box for testing my TCP stack.  I'm in
the early stages right now and I have a lot of bugs.  One of my bugs
is that I shut down a connection on my end but I'm doing something
wrong and the connection on the FreeBSD side stays up, i.e.:

[bsd@vger]:/net- netstat
Active Internet connections
Proto Recv-Q Send-Q Local Address Foreign Address   (state)
tcp0  0 vger.telnet   bos.5000  ESTABLISHED

'vger' is my FreeBSD machine and 'bos' is my experimental OS.  The
connecton on 'bos' at this point is actually closed.

Does anyone know how I can manually shutdown the above connection on
'vger' short of waiting a really long time or rebooting?

Thanks,
-Brian
-- 
Brian Dean  [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: The -o port=xxx option in NFS

[Doug]

On Tue, 21 Sep 1999, Zhihui Zhang wrote:

> 
> On Tue, 21 Sep 1999, Zhihui Zhang wrote:
> 
> > 
> > The mount_nfs manual says I can use -o port= to specify
> > a port number for NFS requests.  Which port number should I use: the port
> > number of the portmapper (111), the port number of the mountd daemon, or
> > the port number of the nfsd daemon?  I also suppose I can use the
> > following command:
> > 
> > # mount -o port=xxx host:directory directory
> > 
> > and the -o port=xxx part will be passed onto the mount_nfs.  Is this
> > right?
> > 
> In answering myself, the port number should be 2049.

Why do you want to specify the port? If you have no need to do
that, just leave the option out.

Good luck,

Doug
-- 
"My mama told me, my mama said, 'don't cry.' She said, 'you're too young a man
to have as many women you got.' I looked at my mother dear and didn't even
crack a smile. I said, 'If women kill me, I don't mind dyin!'" 

- John Belushi as "Joliet" Jake Blues, "I Don't Know"



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: kernel config and sysctl

[Peter Jeremy]

On Tue, 21 Sep 1999 10:17:26 -0400 (EDT), [EMAIL PROTECTED] wrote:
>I've always had the impression that the sysctls available on a system are
>dependent on the kernel configuration, but have never been able to verify
>this.

This is true.  They also depend on the KLDs (a KLD can add new sysctl
variables and/or trees).

>  What are some kernel options that carry
>along their own sysctl trees, if this is the case?

This is not as easy to answer, and the following relates to -current.
Merging the set of files that define sysctl valiables (via the
SYSCTL_...() macros) with the generic and architecture-dependent
configuration files produces a list of the following options (some of
which are architecture-dependent): apm, bktr, bridge, card, ccd, cd,
compat_linux, cs, dgb, dgm, dummynet, ether, ext2fs, ffs, fla, inet,
ipfilter, ipfirewall, ipx, loran, ncr, nfs, nsio, nullfs, pci,
profiling-routine, si, sio, smp, tun, umapfs, userconfig, vlan and wl.
(I have a list of the 58 actual files if you're interested).

In addition, the following modules define sysctl variables: bktr,
if_tun, ipfw, linux, nfs, null and umap.  (Based on objdump reporting
a .set.sysctl_??? section_).

Peter


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

How to get amd to use /sbin/mount_null for host=localhost ?

[Julian Stacey]

Hi all,
I'm stuck trying to figure out an amd.map to invoke 
/sbin/mount_null by hand, (no problem with the normal nfs).

I have a bunch of machines that use AMD to access one large pseudo-common tree 
containing, to give a simplified example:
/usr/public/3.2/src --> /host/flip/usr/src
obj ... ports ... packages etc .
/usr/public/3.3/src --> /host/park/usr/src
.

Problem is sometimes when I'm already on EG host park, & a shell script
descends into a tree it ends up automounting
/a/park/usr/src 
which is pretty silly & inefficient as in this particular case, a straight
/usr/src 
on park would do, (but the scripts are designed to run equally on all machines,
so building in local host awareness is precisely what I do Not want to do).

What I want is an /etc/amd.map that would achieve this (EG for host park):
  /host/parkcauses mount_null of park:/ on /a/park
  /host/wallcauses mount_nfs of wall:/ on /a/wall
  /host/a.n.other.host  causes mount_nfs of other.host:/ on /a/other.host:/

Please can someone suggest an appropriate amd.map syntax to me ?

PS what I'm using now, that nfs mounts everything, even local host, is
rc.conf:
amd -p -k i386 -l syslog /host /etc/amd.map
mad.map:
/defaults   type:=host;fs:=${autodir}/${rhost};rhost:=${key}
*   opts:=rw,grpid,resvport,nfsv2,nosuid,nodev

Julian H. Staceyhttp://www.freebsd.org/~jhs/
   FreeBSD: Free system software with 2500 free packages, Linux compatible.
   British government wants to criminalise privacy via encryption:
   get your free encryption software from http://www.ifi.uio.no/pgp/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: GNU GLOBAL

[Peter da Silva]

> Tradition counts.  GLOBAL isn't quite sendmail.

On the other hand, sendmail is easier to extract and isolate (there are
no sendmail-specific patches to nvi, for example), and there are several
alternative packages (postfix, exim, qmail, smail, etc) that one might
want to *replace* sendmail with that provide basically the same interface.

I have mixed feelings about the idea of trimming the "core" to exclude
traditional UNIX components. On the one hand, you can take it too far...
I'd hate to see FreeBSD turn into Linux... but on the other there are
arguably things that really should be optional these days, like UUCP
and sendmail, or that are updated externally out of sync with FreeBSD,
like sendmail or bind.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

wormcontrol write speed

[Paulo Fragoso]

Hi,

I'm using one atapi-cdrw (CREATIVE CD-RW RW4224E/1.36) and works fine but
I don't know change speed to 4x, now I'm burning at double speed (I'm
spending 37min to burn one full cd). I've got other unit (YAMAHA-SCSI)
which spends 17min for a full cd but using cdrecord speed=4.

Are there any way to make wormcontrol burns cds at 4x speed?

Thanks,
Paulo Fragoso.

--
"  ... Overall we've found FreeBSD to excel in performace, stability,
technical support, and of course price. Two years after discovering
FreeBSD, we have yet to find a reason why we switch to anything else"
-David Filo, Yahoo!



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: GNU GLOBAL

[W Gerald Hicks]

Tradition counts.  GLOBAL isn't quite sendmail.

Cheers,

Jerry Hicks
[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: IPv6 on 3.2 STABLE ?

[Wes Peters]

stefan parvu wrote:
> 
> Well and more details from mailing list is that there is no "standard"
> for IPv6 yet.
> Somebody could explain a little bit here what really means this when
> DEC, HP they have already on the TCP stack the newest IP ?

Search for ipv6 in the FreeBSD mailing list archives at

http://www.freebsd.org/search/

There is NO reason to rehash all of it here.

-- 
"Where am I, and what am I doing in this handbasket?"

Wes Peters Softweyr LLC
[EMAIL PROTECTED]   http://softweyr.com/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: what is devfs?

[Warner Losh]

Devices must failsafe from a security point of view in the absense of
a devfsd.  Otherwise there will extreme opposition from the security
officer.  This means 0600 or more restrictive permissions.  While it
doesn't happen often, it must be designed for.  Otherwise you've
replaced a secure, predictible system with an insecure one, which is
not acceptible at all in the base FreeBSD product.

How permissions are saved, devices are given out for use I don't care
too much about so long as it is secure.

In general, it is very hard to secure a system where things aren't
predictable.

Warner



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: Mylex RAID controllers.

[Mike Smith]

> 
> I was wondering if anybody was currently working on support for any Mylex
> RAID controllers.  We're unfortunately a generation behind on the DPTs and
> particular vendor that I work with only sells Mylex with their machines.

I'm working on it at the moment.  It doesn't help that Mylex have three 
different and incompatible software interfaces, and their firmware 
interacts extremely badly with our loader.

-- 
\\  The mind's the standard   \\  Mike Smith
\\  of the man.   \\  [EMAIL PROTECTED]
\\-- Joseph Merrick   \\  [EMAIL PROTECTED]




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: The -o port=xxx option in NFS

[Zhihui Zhang]

On Tue, 21 Sep 1999, Zhihui Zhang wrote:

> 
> The mount_nfs manual says I can use -o port= to specify
> a port number for NFS requests.  Which port number should I use: the port
> number of the portmapper (111), the port number of the mountd daemon, or
> the port number of the nfsd daemon?  I also suppose I can use the
> following command:
> 
> # mount -o port=xxx host:directory directory
> 
> and the -o port=xxx part will be passed onto the mount_nfs.  Is this
> right?
> 
In answering myself, the port number should be 2049.

-Zhihui



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: Infrared trackball diffs available

[Doug White]

On Mon, 20 Sep 1999, Douglas Pokorny wrote:

> A few days ago I was at Office Max and bought an InterAct "Web.Remote
> professional".  For those of you who don't know, its an infrared
> remote control which contains a trackball, two trackball buttons, and
> an 18-key keypad.  It was a pretty good deal for $17US.
> 
> My ultimate goal is to use it to control my mp3 playing FreeBSD server.

Toss this to [EMAIL PROTECTED], we have support for other remotes.

Doug White   
Internet:  [EMAIL PROTECTED]| FreeBSD: The Power to Serve
http://gladstone.uoregon.edu/~dwhite| www.freebsd.org



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: Crunching pkg_add ?

[Doug White]

On Mon, 20 Sep 1999, Johan Kruger wrote:

> I've been playing with picobsd ( the router option ) and have been
> adding stuff to crunch - no problem, untile i wanted to add pkg_add to
> crunch. The problem is is that libinstall.a uses cleanup that is defined
> elsewhere. I get the following : look at attachment ?

cleanup is in src/usr.sbin/pkg_install/add/perform.c.  Do you have the
whole pkg_install source checked out?

Doug White   
Internet:  [EMAIL PROTECTED]| FreeBSD: The Power to Serve
http://gladstone.uoregon.edu/~dwhite| www.freebsd.org



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

PCweek article

[Christopher T. Griffiths]

He everyone,

PCweek is sponsoring another hacking contest against Linux and WinNT.  

Here is the URL:

http://www.hackpcweek.com/

They have a post area and I have made the suggestion that they test
freebsd against these two os's and see how we fair.  I have to say the
freebsd is by far a much more stable and if configured correctly a much
more secure option to linux and WinNT.  Anyway check it out.

Chris

Christopher T. Griffiths
Senior Network/Systems Administrator
Quansoo Group Inc.
[EMAIL PROTECTED]
Phone:   (302) 777-4141
Fax: (302) 777-4142
Mobile:  (302) 521-3436



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: kernel config and sysctl

[Doug]

On Tue, 21 Sep 1999 [EMAIL PROTECTED] wrote:

> Can anyone confirm/deny this?  What are some kernel options that carry
> along their own sysctl trees, if this is the case?

IPFW for sure, if it's installed you have:

net.inet.ip.fw.debug: 1
net.inet.ip.fw.one_pass: 1
net.inet.ip.fw.verbose: 1
net.inet.ip.fw.verbose_limit: 2000

which are not present if there is no IPFW. Can't help you much beyond
that, but hopefully that'll give you a place to start. 

Doug
-- 
"My mama told me, my mama said, 'don't cry.' She said, 'you're too young a man
to have as many women you got.' I looked at my mother dear and didn't even
crack a smile. I said, 'If women kill me, I don't mind dyin!'" 

- John Belushi as "Joliet" Jake Blues, "I Don't Know"



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Mylex RAID controllers.

[Chuck Youse]

I was wondering if anybody was currently working on support for any Mylex
RAID controllers.  We're unfortunately a generation behind on the DPTs and
particular vendor that I work with only sells Mylex with their machines.

Chuck Youse 
Director of Engineering
[EMAIL PROTECTED]




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: what is devfs?

[Ben Rosengart]

On Tue, 21 Sep 1999, Julian Elischer wrote:

> > I often change perms on the bpf device so that members of the wheel
> > group can read it.
> 
> do you do this in /etc/rc.local?
> any reason you couldn't still do this?

I do it by hand, but I see no reason why it couldn't be done in rc.local.

--
 Ben Rosengart

UNIX Systems Engineer, Skunk Group
StarMedia Network, Inc.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: what is devfs?

[Julian Elischer]

On Tue, 21 Sep 1999, Ben Rosengart wrote:

> On Tue, 21 Sep 1999, Peter Wemm wrote:
> 
> > Matthew Dillon wrote:
> > > I think devfs is really cool.  I don't think it needs to have
> > > fancy persistence in order to be useful.
> > 
> > Likewise.  I find myself never needing to change device permissions.
> 
> I often change perms on the bpf device so that members of the wheel
> group can read it.

do you do this in /etc/rc.local?
any reason you couldn't still do this?

> 
> 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: missing files with NFSv3 and Solaris2.7 machine...

[David E. Cross]

> > We have a number of solaris 2.78 machines (I am in the process of installing
> > them now), and I notice that if I ls a directory that is mounted NFSv3/UDP from
> > a FreeBSD server to a Solaris 2.7 client there are a number of files that
> > show up missing.  This is most intreaging with a large untar as I can do
> > 'ls | wc -l' in a directory and watch the numbers dance:
> 
> ...
> > 
> > Any ideas what isn't working correctly?
> 
> This looks like something that was discussed maybe a couple of
> months ago. It turned out to be a bug in the Solaris implementation,
> which is something some people did not accept because the Solaris
> implementation is the reference implementation (yeah, I'll call all
> my programs "reference implementation" from now on :). FreeBSD is
> working according to NFS specs, but Solaris isn't.

Count me as one of the ones who do not accept this answer.  I realize that
the Sun code may very well have bugs in it.  I also know that what we have
right now "doesn't work" with sun clients.  I believe that we have made
modifications to our TCP/IP stack  code to deal with windows machines who
are not to spec, could we not do the same for sun and NFS?

Alternately, we have a sun support contract, and if someone could detail to
me exactly how they are not compliant I will try to file a bug report.

--
David Cross   | email: [EMAIL PROTECTED] 
Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd 
Rensselaer Polytechnic Institute, | Ph: 518.276.2860
Department of Computer Science| Fax: 518.276.4033
I speak only for myself.  | WinNT:Linux::Linux:FreeBSD


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: what is devfs?

[Chuck Robey]

Can everybody please remember that the argument about whether persistence
is good, or the devil's invention, has already been totally beaten to
death, and it's in the mail archives.

Most of you have been working towards defining an acceptable compromise,
but if your post gives your opinion about persistence, please save it,
you're doing us no service!  We don't need more heat on the question, we
need a path to solution.



Chuck Robey| Interests include C programming, Electronics,
213 Lakeside Dr. Apt. T-1  | communications, and signal processing.
Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and
(301) 220-2114 |   jaunt.mat.net : FreeBSD-current(Alpha)




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: what is devfs?

[Warner Losh]

In message <[EMAIL PROTECTED]> Tony Finch writes:
: Why not just do a one-off checkpoint at shutdown time? Why do you need
: to track the changes as they happen?

Power failures.

Also, if the device is new, it might be nice to have commands that run 
when they arrive in the tree (think pccard).

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: Out of swap handling and X lockups in 3.2R

[Matthew Dillon]

:where SIZE was 4 MB in this case. I ran it on the console (I've got 64 MB
:of RAM and 128 MB of swap) until the swap pager went out of space and
:my huge process was eventually killed as expected. Fine. But when I ran 
:it under X Window, the system eventually killed the X server (SIZE ~20 MB,
:RES ~14 MB -- the biggest RES size) instead of my big process (SIZE ~100
:MB, RES 0K). 
:
:My question is: Why was the X server killed ? Was it because the 'biggest'
:process is the one with the biggest resident memory size ?
:And if so, why not take into account the total size of processes ?

The algorithm is pretty dumb.  In fact, it would not be too difficult
to actually calculate the amount of swap being used by a process and
add that to the RSS when figuring out who to kill.

:This leads me to another (not related to swap) question:
:
:When the X server is killed, the machine simply hangs without any
:reaction to Ctrl-Alt-F1 or even Ctrl-Alt-Del. Is that the normal
:behaviour ? (I think it should get the user back to the console ?!)
:Is there any workaround ?
:
:TIA,
:
:Ivan

The X server wasn't killed nicely, it couldn't take you out of the
video mode.

-Matt
Matthew Dillon 
<[EMAIL PROTECTED]>


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

The -o port=xxx option in NFS

[Zhihui Zhang]

The mount_nfs manual says I can use -o port= to specify
a port number for NFS requests.  Which port number should I use: the port
number of the portmapper (111), the port number of the mountd daemon, or
the port number of the nfsd daemon?  I also suppose I can use the
following command:

# mount -o port=xxx host:directory directory

and the -o port=xxx part will be passed onto the mount_nfs.  Is this
right?

Thanks for any help.

--
Zhihui Zhang.  Please visit http://www.freebsd.org
--



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: what is devfs?

[Ben Rosengart]

On Tue, 21 Sep 1999, Peter Wemm wrote:

> Matthew Dillon wrote:
> > I think devfs is really cool.  I don't think it needs to have
> > fancy persistence in order to be useful.
> 
> Likewise.  I find myself never needing to change device permissions.

I often change perms on the bpf device so that members of the wheel
group can read it.

--
 Ben Rosengart

UNIX Systems Engineer, Skunk Group
StarMedia Network, Inc.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: what is devfs?

[Chuck Robey]

On Mon, 20 Sep 1999, Julian Elischer wrote:

> > POLA!  if we have persisten permissions and ownership, and we allow
> > renaming, then renaming should also be persistant...  after the mount
> > again, da0c either no longer exists, or is no longer ttyd1... which
> > neither is an acceptable solution...
> 
> I think at this stage you've gone overboard..

Gee, I'd have to agree on this one.

> part of the definition of devfs is that a device shows up on mount
> with it's canonical name.. On each new mount every time, even if you've
> mounted it in 10 different places.

Absolutely correct, canonical names only, why don't you try to rename
files in /proc?  You've taken this one too far this time.



Chuck Robey| Interests include C programming, Electronics,
213 Lakeside Dr. Apt. T-1  | communications, and signal processing.
Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and
(301) 220-2114 |   jaunt.mat.net : FreeBSD-current(Alpha)




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

kernel config and sysctl

[mwlucas]

Well, I tried -questions, and met with a resounding silence.  jkh tells me
that you folks here are the only ones with the expertise to answer this
sort of question, so here you go.

I'm preparing a series of articles on FreeBSD's sysctl interface -- not
the inner workings, merely "What is sysctl, what is it good for, and how
can it solve my problems?"  The magazine editor specifically asked for it,
so I'm pretty sure it'll see print.  ;)

I've always had the impression that the sysctls available on a system are
dependent on the kernel configuration, but have never been able to verify
this.  I've gone through a variety of kernel source, but there's so much
of it I can't be sure I have a definitive answer.  I've also sat down a
couple times and built a variety of kernels, trying to verify this with
different combinations of options.  Either I've been picking the wrong
options, or the sysctls on a system are fixed.

Can anyone confirm/deny this?  What are some kernel options that carry
along their own sysctl trees, if this is the case?

Thanks,
Michael

-- 
Michael Lucas   |
Exceptionet, Inc.   |   www.exceptionet.com
"Exceptional Networking"|


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: what is devfs?

[Brian Beattie]

On Tue, 21 Sep 1999, John-Mark Gurney wrote:

> Julian Elischer scribbled this message on Sep 20:
> > > POLA!  if we have persisten permissions and ownership, and we allow
> > > renaming, then renaming should also be persistant...  after the mount
> > > again, da0c either no longer exists, or is no longer ttyd1... which
> > > neither is an acceptable solution...
> > 
> > I think at this stage you've gone overboard..
> > 
> > part of the definition of devfs is that a device shows up on mount
> > with it's canonical name.. On each new mount every time, even if you've
> > mounted it in 10 different places.
> 
> I didn't flat out state it, but I think persistant should NOT be done
> via an underlying node, but via a daemon... and then this would be a
> moot point as you'd just configure the daemon to do what you need to
> do, or run an /etc/rc.devfs script which sets the permission properly..
>
I distrust the complexity of daemons in this case, for something as
important as device permissions.
 
> that is all I'm looking for... anything else is stupid or complex...
>
Stupid, is that a technical term?
 
> hell, a daemon could be something as simple as a script that constantly
> sees if a device has root:wheel 0600 permissions, and set them correctly
> if they don't...
> 
Security controlled by a script, Yikes!

> persitance is stupid UNLESS it is complete persitance... and you've said
Why?  Is this a technical judgment, or personal prejudice?

> that complete persitance is to complex, so lets go w/ no persitance, and
> default secure premissions...
> 
Because initial security (boot time) is important, and complex solutions
are prone to holes.  Another daemon, is yet one more process, sucking up
resources, prone to attack.  If I can hack your devfsd, I can give myself
permissions to do anything to your system.

Brian Beattie| The only problem with
[EMAIL PROTECTED]  | winning the rat race ...
www.aracnet.com/~beattie | in the end you're still a rat



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Out of swap handling and X lockups in 3.2R

[Ivan]

Hi,

I have a couple of questions about the way 'out of swap' situations are
handled in FreeBSD. Not that my system often runs out of swap, I'm just 
being curious:

When the system runs out of swap space, it is supposed to kill the
'biggest' process to regain some space.
I wrote a little program to test this behaviour, basically something like

/* gradually ask for memory at each key stroke */
while (getchar())
{
  a = malloc(SIZE);
  assert(a);
  memset(a,0,SIZE);
}

where SIZE was 4 MB in this case. I ran it on the console (I've got 64 MB
of RAM and 128 MB of swap) until the swap pager went out of space and
my huge process was eventually killed as expected. Fine. But when I ran 
it under X Window, the system eventually killed the X server (SIZE ~20 MB,
RES ~14 MB -- the biggest RES size) instead of my big process (SIZE ~100
MB, RES 0K). 

My question is: Why was the X server killed ? Was it because the 'biggest'
process is the one with the biggest resident memory size ?
And if so, why not take into account the total size of processes ?

This leads me to another (not related to swap) question:

When the X server is killed, the machine simply hangs without any
reaction to Ctrl-Alt-F1 or even Ctrl-Alt-Del. Is that the normal
behaviour ? (I think it should get the user back to the console ?!)
Is there any workaround ?

TIA,

Ivan



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: GNU GLOBAL

[Shigio Yamaguchi]

Peter Wemm wrote:
> Will you be assigning the copyright to the FSF?  (ie: you'll never be able
> to change your mind?  50 years is a long time...)

I will keep the right.
Thank you for your advice.
--
Shigio Yamaguchi - Tama Communications Corporation
Mail: [EMAIL PROTECTED], WWW: http://www.tamacom.com


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: GNU GLOBAL

[Shigio Yamaguchi]

Mats Lofkvist wrote:
> But bugfixes and/or developments needed by the core FreeBSD tools
> will have to be done on the BSD licensed version of global
> (since the core system isn't supposed to depend on ports),
> isn't this going to lead to the split of the global development
> in two?

You are right.
But I believe if I make improvements on GNU/GLOBAL then people will
replace BSD/GLOBAL with it. It depends on my developping power.
Of course, I'll keep fixing bugs about BSD/GLOBAL.
--
Shigio Yamaguchi - Tama Communications Corporation
Mail: [EMAIL PROTECTED], WWW: http://www.tamacom.com


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

subscribe

[Nicholas Edward Cave]

__
Get Your Private, Free Email at http://www.hotmail.com


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

RE: Help - Fasttrak eide raid host adapter and FreeBSD

[Richard Uren]

> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Soren Schmidt
> Sent: Tuesday, 21 September 1999 4:30
> To: [EMAIL PROTECTED]
> Cc: 'Ward R Goodwin'; [EMAIL PROTECTED];
> [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Help - Fasttrak eide raid host adapter and FreeBSD
> 
> 
> It seems Richard Uren wrote:
> > Ward,
> > 
> > I purchased one last week - A FastTrak66
> > (which is perhaps not the 'FastTrack' you mentioned.
> > 
> > Its detects as a 'PCI - Mass Storage Controller' 
> > (in the Bios startup) and unless there is some 
> > 'emulate an IDE drive' mode that I missed it 
> > won't work.
> 
> If you use the 'ata' driver in -current it should be detected and
> usable uptil UDMA33. I have a patch that might make it work in UDMA66
> mode but I havn't gotten my hand on one to test yet..
> 
> -Soren

Excellent - I'll give it a try.

Cheers
Richard



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: GNU GLOBAL

[Peter Wemm]

"Daniel C. Sobral" wrote:
> Jamie Bowden wrote:
> > 
> > On Sun, 19 Sep 1999, Peter Wemm wrote:
> > 
> > :Will you be assigning the copyright to the FSF?  (ie: you'll never be able
> > :to change your mind?  50 years is a long time...)
> > 
> > 70 now I believe.  Changed to be compatible with the euros, who are all 70
> > years apparently.
> 
> Actually, I rather believe it changed so Mickey Mouse doesn't enter
> public domain.

Heh, well, it's too late here (in .au).  All the old pre-1949 warner bros/
disney/etc stuff is public domain now and available quite cheaply on video.

Cheers,
-Peter



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: what is devfs?

[Peter Wemm]

Matthew Dillon wrote:
> I think devfs is really cool.  I don't think it needs to have
> fancy persistence in order to be useful.

Likewise.  I find myself never needing to change device permissions.

I do wish however that there were some sort of "template" options for
classes of names.

The way I imagine it would work would be like this:

By default, all devices start out as root:wheel, 0600.

We can then change the default permissions by "class".  For example, devices
may be grouped something like this:  disk, tape, tty, cua, pty, vty, etc.

Then, we could change the default permissions by class, with something like
this in a rc.* script:

sysctl -w devfs.template.mode.cua=0660
sysctl -w devfs.template.owner.cua=`id -u uucp`
sysctl -w devfs.template.group.cua=`id -g dialer`
sysctl -w devfs.template.mode.disk=0620
sysctl -w devfs.template.group.disk=`id -g operator`
sysctl -w devfs.template.mode.pty=0666
sysctl -w devfs.template.group.pty=`id -g tty`
... and so on.

For this to work well, devices should track their "template" until they are
explicitly given their own modes.  For example, doing a chmod on /dev/rst0
will seperate it from the "tape" class.  Until that point, it's modes change
every time the template is changed.  This allows us to boot with reasonable
defaults and explicitly give permissions in bulk and still DTRT with devices
appearing (eg: usb devices).

An alternative to abusing sysctl might be to have some pseudo devices in
(say) /dev/template/{pty,disk,tape,} that can be directly tweaked with
chmod/chown/etc..

Cheers,
-Peter




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: L440GX+ Server Board

[Luiz Morte da Costa Junior]

Hi list,

My problem is solved. Since I changed my SCSI to a Quantum, I haven't have
more problem with performance.

I recompiled the pwd_mkdb.c program using more RAM memory and the
performance became better. Before compilation the "delete user" operation
takes 3 minutes, and now the same operation takes 11 seconds (whe have
about 12000 usernames - thanks Pedro Vazquez ;).

[]s,

Luiz Morte da Costa Junior
Analista de RedesE-mail: [EMAIL PROTECTED]
Telefone: +55 19 754-2532Fax: +55 19 255-7576
CorreioNet - Correio Popular Campinas - SP - Brazil


On Mon, 13 Sep 1999, Luiz Morte da Costa Junior wrote:
> 
> Hi list,
> 
> I can't solve the problem yet.
> 
> When I runnig the dmesg command, I have:
> 
> ---
> da0 at ahc0 bus 0 target 0 lun 0
> da0:  Fixed Direct Access SCSI-2 device 
> da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing
> Enabled
> da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C)
> da1 at ahc0 bus 0 target 1 lun 0
> da1:  Fixed Direct Access SCSI-2 device 
> da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing
> Enabled
> da1: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C)
> ---
> 
> I did a test, changing only the SCSI disk, using the same motherboard
> (L440GX+). I ran the dmesg command again and I received:
> 
> --
> da0 at ahc0 bus 0 target 0 lun 0
>  da0:  Fixed Direct Access SCSI-2 device 
>  da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing
> Enabled
>  da0: 8683MB (17783250 512 byte sectors: 255H 63S/T 1106C)
> --
> 
> 
> I realized that the quantum disk have a 80.000MB/s transfers.
> Does someone use a SEAGATE ST39140LW disk and have I/O problems?
> 
> Regards,
> Luiz Morte.
> 
> PS:
> Someone told me that vipw doens't have much I/O disk, but when I run it
> with 12000 accounts, my disk have a lot off access.
> 
> On Sun, 22 Aug 1999, Luiz Morte da Costa Junior wrote:
> > 
> > Hi all,
> > 
> > I have a problem with a server running a FreeBSD 3.2.
> > 
> > My Server has a L440GX+ Serber Board (intel), with network card 10/100,
> > SCSI AIC 7896 (80MB/s), 2 SCSI disk with 9GB (80MB/s), 2 pentium III
> > 450Mhz (not overclocked). The NIC and SCSI are onboard.
> > 
> > I recompiled a kernel to SMP, and it worked. The server is ok, but when
> I
> > run a comand with disk access (whith vipw or mysql), the performance of
> > server goes down. My server stays very very very slow. If I use pine to
> > read my messages, it doesn't work. When the comand finishes, the server
> > stays "ok" again.
> > 
> > I recompiled the kernel with "maxusers 128", but it doesn't work.
> > 
> > My SCSI cable has a terminator and the scsi setup is ok (I think :) ).
> > 
> > The dmesg command output is in attchmnt.
> > 
> > I appreciate any help.
> 
> []s,
> 
> Luiz Morte da Costa Junior
> Analista de RedesE-mail: [EMAIL PROTECTED]
> Telefone: +55 19 754-2532Fax: +55 19 255-7576
> CorreioNet - Correio Popular Campinas - SP - Brazil
> 

[]s,

Luiz Morte da Costa Junior
Analista de RedesE-mail: [EMAIL PROTECTED]
Telefone: +55 19 754-2532Fax: +55 19 255-7576
CorreioNet - Correio Popular Campinas - SP - Brazil




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: IPv6 on 3.2 STABLE ?

[stefan parvu]

Well and more details from mailing list is that there is no "standard"
for IPv6 yet.
Somebody could explain a little bit here what really means this when
DEC, HP they have already on the TCP stack the newest IP ?

Stef

stefan parvu wrote:
> 
> Hello,
> 
> Last night I worked to port some code to FreeBSD 3.2 Stable.
> I was curious about one fact: on  there is no any in6_addr
> support for IPv6. Am I wrong ? FreeBSD does not support IPv6 ?
> 
> Regards,
> Stef
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-questions" in the body of the message


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: IPv6 on 3.2 STABLE ?

[stefan parvu]

Hi,

Well, on Linux 2.2 IPv6/IPng it is already supported. I don't remember
exactly starting with what version of Linux they have already support
IPv6 but for instance BSDI also is supporting.
So I think we must support quite soon IPv6/IPng for a lot of
Client-Server application which will gonna be build for IPv6.

Some hints in this way ?
Stef

"f.johan.beisser" wrote:
> 
> well, i hate to tell ya, no, currently FBSD does not support IPv6/IPng.
> 
> but, there are a couple packages where you can get it to support it.
> do a search for KAME, and download that.
> 
> now, as to why it's not rolled in already?
> 
> my guess is that it's due to IPng/IPv6 still being under development.
> 
> rumour has it that IPv6 support is going to be fully rolled in "relativly
> soon." how accurate that rumour is, i don't know. any one else know?
> 
> -- jan
> 
> On Tue, 21 Sep 1999, stefan parvu wrote:
> 
> > Hello,
> >
> > Last night I worked to port some code to FreeBSD 3.2 Stable.
> > I was curious about one fact: on  there is no any in6_addr
> > support for IPv6. Am I wrong ? FreeBSD does not support IPv6 ?
> >
> >
> > Regards,
> > Stef
> >


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message