Re: Junior Annoying Hacker Task

2002-02-01 Thread Matt Heckaman
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 1 Feb 2002, Terry Lambert wrote: ... : Determining "source-ability" by sourcing is dangerous. Well, you said make sure it's "sourcable" -- not "source it" :) : You would need to do a "chroot", or run it as a non-priviledged user, : for the p

Re: firewall_enable

2002-02-01 Thread David Syphers
On Friday 01 February 2002 11:56 pm, M. Warner Losh wrote: > Actually, there's a simple way around this that is failsafe. > > firewall_enable=YES What it deos now > =NOWide open > =FAILSAFE Defaults to wired down. Before the discussion on -stable degenera

Re: panic in vfs_syscalls

2002-02-01 Thread Michael Nottebrock
Alfred Perlstein wrote: > > I've just committed a fix, please let me know if it works for > you. Yes, everything's fine now. Thanks again! :) -- Michael Nottebrock To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

firewall_enable

2002-02-01 Thread M. Warner Losh
Actually, there's a simple way around this that is failsafe. firewall_enable=YESWhat it deos now =NOWide open =FAILSAFE Defaults to wired down. /etc/defaults/rc.conf firewall_enable=FAILSAFE That way, people that say firewall_enable=NO get what

Re: *_enable="YES" behavior is bogus

2002-02-01 Thread M. Warner Losh
In message: Garance A Drosihn <[EMAIL PROTECTED]> writes: : In this discussion, there have been two suggestions as to how : 'firewall_enable=no' should behave. : 1) if the firewall is compiled in the kernel, then "=no" :means that the

Re: Junior Annoying Hacker Task

2002-02-01 Thread Brian T . Schellenberger
On Friday 01 February 2002 08:38 pm, Terry Lambert wrote: > "Brian T.Schellenberger" wrote: > > - There is not a single point of failure for all progams; it only > > controls basic system functions and services, it does not control > > applications, so if it fails, your applications aren't all sc

uhub detach causes page fault --- workaround

2002-02-01 Thread FUJIMOTO Kou
After cvsup at 2002/01/29, I met kernel page fault when detaching USB hub. My USB configuration is same as I reported once in -current ML message id <[EMAIL PROTECTED]>. With vmcore and gdb I found the page fault occurs at usb_add_event() in /sys/dev/usb/usb.c(1.53 2002/01/28), line 690:

Re: Junior Annoying Hacker Task

2002-02-01 Thread Terry Lambert
Matt Heckaman wrote: > On Fri, 1 Feb 2002, Terry Lambert wrote: > : There's not even a "virc" equivalent to "vipw", that can do a > : consistency check on the file to make sure it's "sourceable" by a shell > : script, before permitting the edits to replace the valid contents, and > : keep a backup

Re: Junior Annoying Hacker Task

2002-02-01 Thread Matt Heckaman
On Fri, 1 Feb 2002, Terry Lambert wrote: ... : There's not even a "virc" equivalent to "vipw", that can do a : consistency check on the file to make sure it's "sourceable" by a shell : script, before permitting the edits to replace the valid contents, and : keep a backup of the previous file for y

Re: lock reversal in fdalloc()

2002-02-01 Thread Terry Lambert
Alfred Perlstein wrote: > There's a bunch of bogosity in the ordering of allocation of > slots in the filedesc versus filling out the struct file and > insertion into the list that I need to work out. I should be > able to take a swipe at it in a couple of weeks hopefully. It's very tempting to

Re: Junior Annoying Hacker Task

2002-02-01 Thread Terry Lambert
"Brian T.Schellenberger" wrote: > > Does someone want to write a "registry editor" program? > > Yuch. Why? Clearly, you are not a "Junior Annoying Hacker". > > The point of the program would be to edit the "FreeBSD > > Registry", rc.conf, and make it look just like the Windows > > Registry in

Re: Latest binutils import breaks Alpha cross compiles

2002-02-01 Thread Terry Lambert
Giorgos Keramidas wrote: > This still *is* -CURRENT, right? If it doesn't break, once in a > while, how will new things be tested by the -CURRENT userbase? A "make world" before commit? Is this a trick question? > Instead of whining about "you broke it, and haven't fixed it" it would > be a fa

Re: AMD AGP Bug

2002-02-01 Thread Terry Lambert
Erik Trulsson wrote: > > The Athlon rewriting same value to cacheable memory under the knees of > > programmers looks a severe issue to me if it is true. Not only AGP memory > > can be affected. What about SMP, MMIO (if some cacheable mapping exists), > > etc...? > > I am not familiar with the ac

Re: lock reversal in fdalloc()

2002-02-01 Thread Alfred Perlstein
* Terry Lambert <[EMAIL PROTECTED]> [020201 17:02] wrote: > Bruce Evans wrote: > > > basically it seems to get pissy if it doesn't get the file slot it asks > > > for, so if another thread wins the race here, we'll panic. this problem > > > seems to also exist for 4.x and previous versions of fre

Re: lock reversal in fdalloc()

2002-02-01 Thread Terry Lambert
Bruce Evans wrote: > > basically it seems to get pissy if it doesn't get the file slot it asks > > for, so if another thread wins the race here, we'll panic. this problem > > seems to also exist for 4.x and previous versions of freebsd. > > > > I'd like to get this fixed. Any suggestions? I thi

Re: Junior Annoying Hacker Task

2002-02-01 Thread Brian T . Schellenberger
On Friday 01 February 2002 07:26 pm, Terry Lambert wrote: > > >> foo_enable="NO" > > > > > > ipfilter_enable="YES" > > > firewall_enable="NO" > > > > natd_enable="NO" > > natd_interface="fxp0" > > inetd_enable="NO" > > inetd_program="/usr/sbin/inetd" > >

Re: Junior Annoying Hacker Task

2002-02-01 Thread Bosko Milekic
On Fri, Feb 01, 2002 at 04:26:13PM -0800, Terry Lambert wrote: > Who is a GTK hacker? > > Does someone want to write a "registry editor" program? > > The point of the program would be to edit the "FreeBSD > Registry", rc.conf, and make it look just like the Windows > Registry in the editor, usi

Re: Latest binutils import breaks Alpha cross compiles

2002-02-01 Thread Giorgos Keramidas
On 2002-01-30 23:22, Terry Lambert wrote: > Peter Wemm wrote: > > I dont suppose you actually thought to go and have a look and see what the > > problem is yourself, rather than assigning the work to somebody else? > > Nope, sorry. > > I hear the latest binutils break Alpha cross compilation. M

Junior Annoying Hacker Task

2002-02-01 Thread Terry Lambert
> >> foo_enable="NO" > > ipfilter_enable="YES" > > firewall_enable="NO" > natd_enable="NO" > natd_interface="fxp0" > inetd_enable="NO" > inetd_program="/usr/sbin/inetd" > foo_enable="YES/NO" > foo_enable="NO" Who is a GTK hacker? Does someone

Re: Login failures ...

2002-02-01 Thread David W. Chapman Jr.
On Fri, Feb 01, 2002 at 03:06:17PM -0800, Bokyung Wang wrote: > Hello, > > I faced Login Fail problem when I upgrade to FreeBSD 5.0 Current. > > Error messages are > login: PAM unable to dlopen(/usr/lib/pam_login_access.so) > login: PAM[dlerror: Cannot open "/usr/lib/pam_login+access.so"] > logi

Re: How is maintaining ipsec SADB code?

2002-02-01 Thread Kris Kennaway
On Fri, Feb 01, 2002 at 08:49:15AM -0500, Ilmar S. Habibulin wrote: > > I'm trying to implement the use of SA sensitivity labels. While looking > through the code, i've founded some unclear operations, so I want to ask > some questions about them. This code comes from KAME: you can reach the dev

Login failures ...

2002-02-01 Thread Bokyung Wang
Hello, I faced Login Fail problem when I upgrade to FreeBSD 5.0 Current. Error messages are login: PAM unable to dlopen(/usr/lib/pam_login_access.so) login: PAM[dlerror: Cannot open "/usr/lib/pam_login+access.so"] login: PAM adding faulty moule: /usr/log/pam_login_access.so Does anybody know ho

Re: *_enable="YES" behavior is bogus

2002-02-01 Thread Garance A Drosihn
At 4:52 PM -0500 2/1/02, Garance A Drosihn wrote: >It *is* reasonable for them to assume the same >behavior would be true for network_enable=no. I meant "firewall_enable=no" here! If the option *was* called "network_enable=no", then it would be VERY reasonable to expect the machine to be locked

RE: *_enable="YES" behavior is bogus

2002-02-01 Thread Garance A Drosihn
At 5:16 PM -0500 2/1/02, Benjamin P. Grubin wrote: > > I understand the first "error" (where the machine ends up completely >> open) is not desirable. It is very very bad. However, I >> think we can write some code to help out that user. That >> user is extremely likely to be sitting at the

RE: *_enable="YES" behavior is bogus

2002-02-01 Thread Benjamin P. Grubin
Hello, I'm usually but a lurker, though I'd like to toss in my $.02 on this... > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On Behalf Of > Garance A Drosihn > Sent: Friday, February 01, 2002 4:52 PM > To: Erik Trulsson; Paul Fardy > Cc: [EMAIL PROTECTED];

Re: AMD AGP Bug

2002-02-01 Thread Gérard Roudier
On Fri, 1 Feb 2002, Erik Trulsson wrote: > On Thu, Jan 31, 2002 at 09:32:48PM +0100, Gérard Roudier wrote: > > > > > > On Thu, 31 Jan 2002, Jason Evans wrote: > > > > > On Wed, Jan 30, 2002 at 11:14:48PM +0100, Gérard Roudier wrote: > > > > > > > > Linux can be fixed, but the useless writes of

Re: *_enable="YES" behavior is bogus

2002-02-01 Thread Garance A Drosihn
At 6:36 PM +0100 2/1/02, Erik Trulsson wrote: >Consider that the actual code in the various rc* start scripts is >in most cases of the form: > >if foo_enable==yes > do stuff >else > do nothing Let me approach this from a different angle. Several people have tried to argue this by proposing v

Re: *_enable="YES" behavior is bogus

2002-02-01 Thread Garance A Drosihn
At 6:36 PM +0100 2/1/02, Erik Trulsson wrote: >Consider that the actual code in the various rc* start scripts is >in most cases of the form: > >if foo_enable==yes > do stuff >else > do nothing The RC scripts are starting up in a "known" environment (loosely speaking). Enough is known about t

Re: AMD AGP Bug

2002-02-01 Thread Erik Trulsson
On Thu, Jan 31, 2002 at 09:32:48PM +0100, Gérard Roudier wrote: > > > On Thu, 31 Jan 2002, Jason Evans wrote: > > > On Wed, Jan 30, 2002 at 11:14:48PM +0100, Gérard Roudier wrote: > > > > > > Linux can be fixed, but the useless writes of the existing Athlons from > > > the very fast cache to th

Re: lock reversal in fdalloc()

2002-02-01 Thread Bruce Evans
On Fri, 1 Feb 2002, Alfred Perlstein wrote: > It's actually safe... however dup2 thinks that we won't race > for the file slot: > > if (new >= fdp->fd_nfiles) { > if ((error = fdalloc(td, new, &i))) { > FILEDESC_UNLOCK(fdp); >

Re: AMD AGP Bug

2002-02-01 Thread Gérard Roudier
On Thu, 31 Jan 2002, Terry Lambert wrote: > "Cameron, Frank" wrote: > > From what was posted on the linux-kernel list the problem is the OS > > doing the wrong thing not the hardware. I originally asked the > > question (albeit not worded as clearly as I should have) because if > > Microsoft a

Re: Recent -Current & KDE problems

2002-02-01 Thread David O'Brien
On Fri, Feb 01, 2002 at 01:51:54PM -0500, Alan Eldridge wrote: > Is "ld --version" a reliable indicator? Should be. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

[no subject]

2002-02-01 Thread Schaller Christoph
auth 7d989b2b unsubscribe freebsd-current [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: AMD AGP Bug

2002-02-01 Thread Gérard Roudier
On Thu, 31 Jan 2002, Jason Evans wrote: > On Wed, Jan 30, 2002 at 11:14:48PM +0100, Gérard Roudier wrote: > > > > Linux can be fixed, but the useless writes of the existing Athlons from > > the very fast cache to the relatively very slow memory cannot. And all > > Athlon users may well pay this

Re: lock reversal in fdalloc()

2002-02-01 Thread Alfred Perlstein
* Alfred Perlstein <[EMAIL PROTECTED]> [020131 10:48] wrote: > * Bruce Evans <[EMAIL PROTECTED]> [020131 09:42] wrote: > > > > I'm not sure that releasing the lock here is safe, but other parts of > > fdalloc() do this. > > I don't think this is safe at a glance, I think it's only safe right > b

Re: *_enable="YES" behavior is bogus

2002-02-01 Thread Siegbert Baude
Hi all, > But I think that the intent in /etc/rc.conf is that enable="NO" > _is_ the same thing as disabling it. You might say "If that were > the intent, they'd have used ___." What word should we use > to indicate the absolute YES or NO that some of us believe > should be the simple correc

Re: Recent -Current & KDE problems

2002-02-01 Thread Alan Eldridge
On Fri, Feb 01, 2002 at 10:36:01AM -0800, David O'Brien wrote: >On Fri, Feb 01, 2002 at 11:07:19AM -0500, Alan Eldridge wrote: >> How are you going to tell, in the objprelink port, what version of >> binutils you're working with? If you patch it to fix the -current problem, >> you'll likely break

Re: Recent -Current & KDE problems

2002-02-01 Thread David O'Brien
On Fri, Feb 01, 2002 at 11:07:19AM -0500, Alan Eldridge wrote: > How are you going to tell, in the objprelink port, what version of > binutils you're working with? If you patch it to fix the -current problem, > you'll likely break -stable. I plan on MFC'ing Binutils 2.12.0 when it is released in

Re: panic in vfs_syscalls

2002-02-01 Thread Alfred Perlstein
* Michael Nottebrock <[EMAIL PROTECTED]> [020131 12:19] wrote: > I'm getting these kind of panics with yesterday's kernel every time I > try to use rpm. > > [[EMAIL PROTECTED]]:~ > rpm -Uhv --root=/compat/linux > /home/lofi/libpng-1.0.9-1.i386.rpm > recursed on non-recursive lock (sleep mutex) f

Re: *_enable="YES" behavior is bogus

2002-02-01 Thread Erik Trulsson
On Fri, Feb 01, 2002 at 02:47:30AM -0330, Paul Fardy wrote: > These examples, _and_yours_, are examples that suggest that > /etc/rc.conf has a fundamental principle that > > foo_enable="YES/NO" > > is supreme. One can set up all the requisite parameters (e.g. you > can create sendmail.cf,

Re: *_enable="YES" behavior is bogus

2002-02-01 Thread Paul Fardy
Paul Fardy <[EMAIL PROTECTED]> types: >> When the rc.conf file includes >> foo_enable="NO" >> it's right to expect that the system will operate like a system that does >> not >> have foo installed. On Thursday, January 31, 2002, at 04:43 AM, Mike Meyer wrote: > So you think that if I instal

Re: Recent -Current & KDE problems

2002-02-01 Thread Pete Fritchman
++ 01/02/02 11:07 -0500 - Alan Eldridge: | On Fri, Feb 01, 2002 at 10:18:20AM -0500, Pete Fritchman wrote: | >++ 01/02/02 09:04 -0600 - David W. Chapman Jr.: | >| I'm seeing this on a -current as of yesterday and as of today. I | >| just finished a make world and kernel a few mins ago as well as

Re: Recent -Current & KDE problems

2002-02-01 Thread John Hay
> On Fri, Feb 01, 2002 at 10:18:20AM -0500, Pete Fritchman wrote: > >++ 01/02/02 09:04 -0600 - David W. Chapman Jr.: > >| I'm seeing this on a -current as of yesterday and as of today. I > >| just finished a make world and kernel a few mins ago as well as > >| rebuilding all my ports, but kde s

Re: Recent -Current & KDE problems

2002-02-01 Thread Alan Eldridge
On Fri, Feb 01, 2002 at 10:18:20AM -0500, Pete Fritchman wrote: >++ 01/02/02 09:04 -0600 - David W. Chapman Jr.: >| I'm seeing this on a -current as of yesterday and as of today. I >| just finished a make world and kernel a few mins ago as well as >| rebuilding all my ports, but kde still dies

Re: Recent -Current & KDE problems

2002-02-01 Thread Pete Fritchman
++ 01/02/02 09:04 -0600 - David W. Chapman Jr.: | I'm seeing this on a -current as of yesterday and as of today. I | just finished a make world and kernel a few mins ago as well as | rebuilding all my ports, but kde still dies when I try to load it, | last night before I tried to rebuild all t

Recent -Current & KDE problems

2002-02-01 Thread David W. Chapman Jr.
I'm seeing this on a -current as of yesterday and as of today. I just finished a make world and kernel a few mins ago as well as rebuilding all my ports, but kde still dies when I try to load it, last night before I tried to rebuild all the ports I was getting signal 11's. Any ideas anyone?

Re: Pam problems today

2002-02-01 Thread David W. Chapman Jr.
On Fri, Feb 01, 2002 at 06:25:21AM -0800, Edwin Culp wrote: > David, > > Thanks for posting this. I have built a new world and kernel but haven't > run mergemaster, yet. I did see the problem just waiting in > /usr/src/etc/rc.d so I think I'll just leave it there for the time being. > > Thank

Re: Pam problems today

2002-02-01 Thread Edwin Culp
David, Thanks for posting this. I have built a new world and kernel but haven't run mergemaster, yet. I did see the problem just waiting in /usr/src/etc/rc.d so I think I'll just leave it there for the time being. Thanks again for the advance notice. ed Quoting "David W. Chapman Jr." <[EMAI

How is maintaining ipsec SADB code?

2002-02-01 Thread Ilmar S. Habibulin
I'm trying to implement the use of SA sensitivity labels. While looking through the code, i've founded some unclear operations, so I want to ask some questions about them. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: AMD AGP Bug

2002-02-01 Thread Terry Lambert
Peter Wemm wrote: > I'm a little confused as to which bugs are which that we're talking > about now. Which is the one that you're trying to sell the info for? I'm not really trying to sell the fix; it's that I'm not willing to give it away when it's no benefit to do so; I'd need a bribe. Kind o

Re: Pam problems today

2002-02-01 Thread Dag-Erling Smorgrav
"David W. Chapman Jr." <[EMAIL PROTECTED]> writes: > are the lines I had to comment out. I checked and I don't have > pam_login_access.so. I know that there have been a bunch of changes > recently, so if this is a known problem I apologize. Right. I forgot to commit the Makefile. Sorry :(

Re: AMD AGP Bug

2002-02-01 Thread Peter Wemm
Terry Lambert wrote: > Glendon Gross wrote: > > That's right, guys! This is FreeBSD after all... so Mr. Lambert is > > entitled to charge 10K for that bugfix code if he wants. In fact he is > > "Free" to do so. But it's a little pricy for me, although perhaps not for > > AMD if it means they ca

Re: AMD AGP Bug

2002-02-01 Thread Terry Lambert
Glendon Gross wrote: > That's right, guys! This is FreeBSD after all... so Mr. Lambert is > entitled to charge 10K for that bugfix code if he wants. In fact he is > "Free" to do so. But it's a little pricy for me, although perhaps not for > AMD if it means they can fix their cache-paging proble