Re: rtfree panic() (fwd)

[CC: to peter, could you MFC this??] [Charset X-UNKNOWN unsupported, skipping...] ARGHH > Hmmm. Judging from the last CVS log entry for route.c (See r1.59), this > problem can manifest itself in -current as well. I´m cross posting on the > initial send, but please, when replying, redirect

Re: Should jail treat ip-number?

> > >-Jail(2) specify "ip_number" and/or "ip6_number" into the kernel. > > > > Well, I guess we want it to be "and", right ? Will people want to > > bind both a IPv4 and IPv6 address (does it make sense to do so ?) > > or will people only need to bind one of them ? > > I also think it is "and",

Re: Should jail treat ip-number?

> Poul-Henning Kamp wrote: > > >-Jail(2) specify "ip_number" and/or "ip6_number" into the kernel. > > > > Well, I guess we want it to be "and", right ? Will people want to > > bind both a IPv4 and IPv6 address (does it make sense to do so ?) > > or will people only need to bind one of them ? >

Re: about jail

[CC: trimmied to -hackers, long lines wrapped, and much content deleted] > there is a simplistic way to create chrooted/jailed virtual servers for > many clients > domains... without getting into the nasty of bsd code i do it daily > with one small > program.. and have all services available

Re: How to prevent motd including os info

> "Rodney W. Grimes" wrote: > > > > > [moving to -hackers] > > [I'm going to loose the rest of this thread since I am not on hackers :-(] > > Shame on you. :) The volume of mail became too high for my time a long while ago. :-( > &

Re: How to prevent motd including os info

> "Rodney W. Grimes" wrote: > > > > > [moving to -hackers] > > [I'm going to loose the rest of this thread since I am not on hackers :-(] > > Shame on you. :) The volume of mail became too high for my time a long while ago. :-( > > &g

Re: How to prevent motd including os info

> "Rodney W. Grimes" <[EMAIL PROTECTED]> writes: > > > One thing I'd like very much, though, would be to have the output of > > > fsck -p logged somehow [...] > > Actually I would like _all_ the output from /etc/rc* to be avaliable > > after

Re: How to prevent motd including os info

> "Rodney W. Grimes" writes: > > > One thing I'd like very much, though, would be to have the output of > > > fsck -p logged somehow [...] > > Actually I would like _all_ the output from /etc/rc* to be avaliable > > after boot. It should be in th

Re: How to prevent motd including os info

> [moving to -hackers] [I'm going to loose the rest of this thread since I am not on hackers :-(] > > "Rodney W. Grimes" <[EMAIL PROTECTED]> writes: > > So when can we see this commited > > Already done (-CURRENT only). I've had requests (not

Re: How to prevent motd including os info

> [moving to -hackers] [I'm going to loose the rest of this thread since I am not on hackers :-(] > > "Rodney W. Grimes" writes: > > So when can we see this commited > > Already done (-CURRENT only). I've had requests (notably from Yan > Koum)