Re: booting from Promise tx2000: FIXED
Len Conrad [EMAIL PROTECTED] writes: while waiting for Soeren Schmidt to get the Promise SX4000 driver done! I was under the impression that the SX4000 and SX6000 were already supported? I know that phk has an SX6000 which he says works fine. OTOH, it's possible that this hasn't percolated down to -STABLE yet. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
HOWTO track resource leaks in kernel modules ?
Hi - I was thinking about making some changes to if_de.c to support a tulip card which isn't being recognized properly. To begin this process, I need to make if_de.c export a detach function so it could be unloaded from the kernel to make debugging of the module a little easier. I've implemented a detach function, which at first glance seems ok. I've run an extremely crude test by kldload / kldunload in an infinte loop for about an hour... and the system hasn't panic-ed. And memory utilization doesn't appear to have grown. However, I'd like something a bit more accurate. Where would I look for resource leaks? Is there a library or toolkit to track such things for kernel modules? Sorry for my ignorance, but most of my Unix development experience has been centered around apache modules. Thanks, --daxbert To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: booting from Promise tx2000: FIXED
Len Conrad [EMAIL PROTECTED] writes: while waiting for Soeren Schmidt to get the Promise SX4000 driver done! I was under the impression that the SX4000 and SX6000 were already supported? I know that phk has an SX6000 which he says works fine. OTOH, it's possible that this hasn't percolated down to -STABLE yet. Last autumn, SS and I tried to get SX4000 docs from Promise and I was told by Promise .tw that the Promise doesn't support FreeBSD, and SS has lost his earlier contact person at Promise. So it's a happy surprise that I learn this week that SS now has coop from Promise. He didn't say the driver was ready. Len To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Jdk13/14 still hangs in 4.8 Prerelease. Outstanding Fix needs to be committed.
On Tue, Feb 25, 2003 at 01:10:25PM +0100, Martin Blapp wrote: To tell the short story. Linux-mozilla works like a charm as root, but it doesn't as a user if you have a java-applet. This has been a problem for years and it affects other Linux appications such as LabView. There is some commented out code in linux_sched_getscheduler() function that provides the proper functionality. It's unclear to me why the code was commented out in the first place, but it would be really nice to get that resolved once and for all. - Murray pgp0.pgp Description: PGP signature
Re: Jdk13/14 still hangs in 4.8 Prerelease. Outstanding Fix needs to be committed.
At 14:56 25/2/03, Murray Stokely wrote: This has been a problem for years and it affects other Linux appications such as LabView. There is some commented out code in linux_sched_getscheduler() function that provides the proper functionality. It's unclear to me why the code was commented out in the first place, but it would be really nice to get that resolved once and for all. According to kern/40611, the problem is in posix4/p1003_1b.c not in the linux wrapper. The updated patch in the PR audit trail seems to work. -- Bob Bishop +44 (0)118 977 4017 [EMAIL PROTECTED] fax +44 (0)118 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Jdk13/14 still hangs in 4.8 Prerelease. Outstanding Fix need
On 25-Feb-2003 Bob Bishop wrote: At 14:56 25/2/03, Murray Stokely wrote: This has been a problem for years and it affects other Linux appications such as LabView. There is some commented out code in linux_sched_getscheduler() function that provides the proper functionality. It's unclear to me why the code was commented out in the first place, but it would be really nice to get that resolved once and for all. According to kern/40611, the problem is in posix4/p1003_1b.c not in the linux wrapper. The updated patch in the PR audit trail seems to work. There is a much simpler patch one can do: Index: p1003_1b.c === RCS file: /usr/cvs/src/sys/posix4/p1003_1b.c,v retrieving revision 1.5.2.1 diff -u -r1.5.2.1 p1003_1b.c --- p1003_1b.c 3 Aug 2000 01:09:59 - 1.5.2.1 +++ p1003_1b.c 25 Feb 2003 16:17:55 - @@ -62,7 +62,7 @@ * only root can do this. */ -#if 0 +#if 1 /* * This is stolen from CANSIGNAL in kern_sig: * Basically, it changes p31b_proc() to not always return an error for non-root. If rwaston@ signs off on the security implications (should be minimal, basically means that you can change your own scheduling params and can change the params of other processes you own) then I would prefer this patch. I don't know why the check was turned off. The entire #if 0 / #else / #endif seems to have been around since revision 1.1. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Jdk13/14 still hangs in 4.8 Prerelease. Outstanding Fix need
On Tue, Feb 25, 2003 at 11:20:34AM -0500, John Baldwin wrote: Basically, it changes p31b_proc() to not always return an error for non-root. If rwaston@ signs off on the security implications (should be minimal, basically means that you can change your own scheduling params and can change the params of other processes you own) then I would prefer this patch. Yes this is the one I was thinking about when I said the commented out code. I've run a kernel with this patch for months, and I didn't see any problems with it in my (unqualified) review. ;) - Murray pgp0.pgp Description: PGP signature
FreeBSD 5.0 roadmap
Fellow committers, let's have a look at the 5.0 planned roadmap: 1) KSE KSE is a joke at best. Is one of those over-engineered ideas that will never be finished. Too bad, it looked good some months ago. 2) GEOM GEOM is another ego trip for Poul-Henning Kamp. He won't let anyone touch it or improve it. Another piece of code that will rot, like phkmalloc and devd. 3) devfs and devd Like Bruce Evans, I don't see what the advantage of having this is. Another ego trip Poul? 4) UFS2 Unlike other parts of FreeBSD, UFS2 is now a reality, kudos to you Mr. McKusick. 5) gcc + toolchain Until Troll Glass brings us TenDRA, we'll have to do with Gah! Nu's proprietary software. Thankfully, we have Mr. O'Brien on board to take care of it. Also Mr. Kabaev as well. 6) Ports The ports people have done an excellent job, kudos to them. 7) PowerPC port Little progress in this area, come on Benno, you can do better. 8) IA-64 Mr. LNUX Torvalds thinks it's not good, so it must be a heck of a cpu. As we all know, Linux is pure hore sh*t. 9) RAIDframe Pathetic Those RAIDframes are *crap*. Scott, not only you fscked up with the release, but your patches are crap! Sincerely, Elcott Song, RE - Tired of spam? Get advanced junk mail protection with MailFreeway.com Join today its FREE! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Isn't today Troll Tuesday?
( Brett Glass!!! ) o ^__^ o (oo)\___ (__)\ )\/\ ||w | || || - Tired of spam? Get advanced junk mail protection with MailFreeway.com Join today its FREE! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Isn't today Troll Tuesday?
( Brett Glass!!! ) o ^__^ o (oo)\___ (__)\ )\/\ ||w | || || - Tired of spam? Get advanced junk mail protection with MailFreeway.com Join today its FREE! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
i386 tinderbox failure
( Brett Glass!!! ) o ^__^ o (oo)\___ (__)\ )\/\ ||w | || || - Tired of spam? Get advanced junk mail protection with MailFreeway.com Join today its FREE! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
IA-64 tinderbox failure
( Brett Glass!!! ) o ^__^ o (oo)\___ (__)\ )\/\ ||w | || || - Tired of spam? Get advanced junk mail protection with MailFreeway.com Join today its FREE! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Newest Arrivals
Title: HBT Newsletter FEB 03 Did someone forward you this? Opt in to hear it first. Please click. If You no no longger wish to receive our mail, please click here. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Jdk13/14 still hangs in 4.8 Prerelease. Outstanding Fix need (fwd)
Per Martin's request, I'm forwarding this response to the broader group involved in this thread. Basically, I think broadening the scope of processes permitted to make the scheduler call is fine, but you don't want to use the CANSIGNAL() code that's currently present for several reasons. The simplist solution might be to only allow the scheduler change if the requesting process is targetting itself. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Network Associates Laboratories -- Forwarded message -- Date: Tue, 25 Feb 2003 12:53:53 -0500 (EST) From: Robert Watson [EMAIL PROTECTED] To: Martin Blapp [EMAIL PROTECTED] Subject: Re: Jdk13/14 still hangs in 4.8 Prerelease. Outstanding Fix need (fwd) On Tue, 25 Feb 2003, Martin Blapp wrote: Basically, it changes p31b_proc() to not always return an error for non-root. If rwaston@ signs off on the security implications (should be minimal, basically means that you can change your own scheduling params and can change the params of other processes you own) then I would prefer this patch. Hmm. I think the check there is a bit on the unsafe side, that could be why it was disabled. Basically, it permits the scheduler change in the following four circumstances: (0) Superuser always wins (1) Subject real uid is object real uid E.g., any process I should randomly start or own (2) Subject effective uid is object real uid If a tool is temporarily switched to my uid to exercise my privileges, sounds OK. (3) Subject real uid is object effective uid (uh oh) (4) Subject effective uid is object effective uid (uh oh) The reason (3) and (4) are problems is that they affect daemons temporarily switching to a user's privileges to carry out a task -- such as mail delivery, or a userland NFS server or the like. It could be that these are poor handling of the loopback process case, wherein a process can always modify its own scheduling. Take a look at p_cansched() in 5.x for a bit more what I think the check should be. In summary, the rules are: (0) You can always reschedule the current process. (1) If you're in a different jail, deny. (2) Optionally call out to MAC. (3) If the seeotheruids support says you can't see the other process, you can't reschedule it either, regardless of uids. (4) If the real uids are the same, it's OK -- i.e., any arbitrary shell process (setuid or otherwise). (5) If the subject effective uid is the same as the object real uid -- if temporarily adopting a user's privileges, we can reschedule the processes they own. (6) Superuser always wins (subject to 0, 1, 2, 3). (7) Deny I don't know why the check was turned off. The entire #if 0 / #else / #endif seems to have been around since revision 1.1. It's probably because whoever wrote it realized that it was moderately suspect. I would oppose simply enabling the current CANSIGNAL check -- it has serious problems. On the other hand, putting in a refined check sounds reasonable and I'd be happy to review such a patch. Although the code from 5.x won't instantly work with 4.x without substantial modification, it might make a good starting point. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Network Associates Laboratories To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
new freebsd distribution...
Hello, I am wanting to start a new distribution of FreeBSD, which will in short = run on the FreeBSD kore, but will consist of a completely redesigned = installation and driver setup layer. =20 The blue lagoon distribution, will not only consist of a graphical = setup interface, but it will also allow easier: driver , port, x windows = setup, etc... =20 Another improvement would be better interface for disabled users: larger = fonts, colors, etc The project is still in the green, but I am seeking help on getting this = project started. =20 I have worked on a graphical illustration, I can provide it upon = request. Cheers, Diego Montalvo To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Jail seperation patch
Hello, I've been working on extending the jail feature of FreeBSD to make it more friendly to VPS providers. I added the following features: * Rudimentary CPU/RAM/number of processes per-jail limits * Multiple IP support (from Pawel Jakub Dawidek's mijail patch for 4.7) * Proper INADDR_ANY support added (so INADDR_ANY will bind to all IP addresses within a jail) * struct prison added to SysV IPC code (to allow for secure use) * Disk mount hiding * Hot add/remove IP addresses from jail using sysctl * Process hiding (non-root users outside jails cannot see jailed processes) The patch is for 5.0-CURRENT/5.0-RELEASE. I would be interested in any comments or suggestions. If anyone's interested, it can be retrieved at http://msalem.translator.cx/dist/jail_seperation.v5.patch. Example of new sysctl entries: %sysctl -a | grep jail jail.jails.test_lifeafterking_org.max_ram: 0 jail.jails.test_lifeafterking_org.max_cpu: 0 jail.jails.test_lifeafterking_org.max_procs: 0 jail.jails.test_lifeafterking_org.procs_used: 10 jail.jails.test_lifeafterking_org.ram_used: 5971968 jail.jails.test_lifeafterking_org.cpu_used: 0 jail.jails.test_lifeafterking_org.ipv4addr: 10.0.0.3,10.0.0.4 security.jail.set_hostname_allowed: 1 security.jail.socket_unixiproute_only: 1 security.jail.sysvipc_allowed: 0 security.jail.quotas_allowed: 0 security.jail.hide_processes: 0 % Thanks, -- Mooneer Salem GPLTrans: http://www.translator.cx/ lifeafterking.org: http://www.lifeafterking.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: booting from Promise tx2000: FIXED
It seems Dag-Erling Smorgrav wrote: Len Conrad [EMAIL PROTECTED] writes: while waiting for Soeren Schmidt to get the Promise SX4000 driver done! I was under the impression that the SX4000 and SX6000 were already supported? I know that phk has an SX6000 which he says works fine. OTOH, it's possible that this hasn't percolated down to -STABLE yet. The SX6000 is supported, the SX4000 is quite a different animal and is not supported yet. However I'm working with Promise to write support for it... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
