Re: ~/.login_conf disabling exact reasons wanted
On Sat, Sep 22, 2001 at 03:17:52PM +0400, Andrey A. Chernov wrote: > Only "me" class can be defined in ~/.login_conf, anything else ignored > there. And "me" class picked up only when permissions are set to user > mode, at the end of setusercontext(). And "copyright" and "welcome" are > not overwriteable from "me" class in any case. I was able to overwrite the settings for the `default' class, which happens to be my login class, and was able to get master.passwd to print... This was 4.x though, not CURRENT, so maybe this is something that wasn't affected in CURRENT, and that's what you're referring to, or something. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Headsup! KSE Nay-sayers speak up!
On Tue, Aug 28, 2001 at 09:55:13AM -0700, Julian Elischer wrote: > Joseph Mallett wrote: > > > > On Mon, Aug 27, 2001 at 09:34:06AM -0700, John Baldwin wrote: > > > Just to get this out in the public: I for one think 5.x has enough changes in > > > it and would like for KSE to be postponed to 6.0-current and 6.0-release. I > > > > I definitely agree about this, 5.x is going to be enough of a major change as > > it is, and confusing _everything_ with even more big changes can't do any > > good in the short term, and would probably make KSE (and other things) a big > > hassle to the point of where they wouldn't be of any use until 6.x anyway. > > > > But that's just my opinion, and I'm sure I'll get smacked for it. > > > > /joseph > > > *smack* Note that I wasn't really posting this comment this late in the thread, but my MTA decided to queue it for an obscenely long time. Sorry. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Headsup! KSE Nay-sayers speak up!
On Mon, Aug 27, 2001 at 09:34:06AM -0700, John Baldwin wrote: > Just to get this out in the public: I for one think 5.x has enough changes in > it and would like for KSE to be postponed to 6.0-current and 6.0-release. I I definitely agree about this, 5.x is going to be enough of a major change as it is, and confusing _everything_ with even more big changes can't do any good in the short term, and would probably make KSE (and other things) a big hassle to the point of where they wouldn't be of any use until 6.x anyway. But that's just my opinion, and I'm sure I'll get smacked for it. /joseph To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bash in /usr/local/bin?
On Mon, Aug 13, 2001 at 07:23:26PM -0500, Jim Bryant wrote: > DOD/DFAS, as well as DOD/DISA. > > I find it amazing that the CIA has a more lax policy than DFAS and DISA. > The only person I've ever talked to from the CIA was in charge of network security to some degree, and according to him they can't even use FreeBSD, OpenBSD, or NetBSD internally. Everything must come from a central vendor and be supported by a real company, not by mailing lists. I'd call that less lax. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: vm_mtx
Those who dial will know its meaning: 6545666,555,666,654555654 On Tue, 24 Apr 2001, Julian Elischer wrote: > Poul-Henning Kamp wrote: > > > > > I'm sure you are fully aware of the implications of the strategically > > placed "supposed" in your own sentence. I have never heard anybody > > get Mach code multithreaded yet. > > Mach has successfully run in multiprocessor multithreadded > systems since 1991. Yep. Distributed processing, too. > > > > -- > __--_|\ Julian Elischer > / \ [EMAIL PROTECTED] > ( OZ) World tour 2000-2001 > ---> X_.---._/ > v > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > -- [ Joseph Mallett] [ xMach Core Team xMach: Proactively Unbloated Microkernel BSD ] [ Proud Open/Free/Net/4.4BSD User; C Programmer; Mad ] [ www.xMach.org ] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
