Re: [Re: [Re: coarse vs fine-grained locking in SMP systems]]

1999-06-27 Thread Matthew Dillon
Here's the basic problem: The kernel is currently designed for single-threaded operation plus interrupt handling. A piece of code in the kernel can temporarily disable certain interrupts with the spl*() codes to cover situations where a race on some system resource might

Re: ufs/ffs resize?

1999-06-27 Thread Greg Lehey
On Sunday, 27 June 1999 at 9:33:09 +0200, [EMAIL PROTECTED] wrote: Another datapoint ot consider, it seems that Linux (at least the derivative version maintained by Alan Cox -- the other one :) ) has now grown an LVM system (probably à la HP or AIX). That's what I've been told yesterday

Improving the Unix API

1999-06-27 Thread Francois-Rene Rideau
Improving the Unix Kernels' API A Kernel Discussion with Hacker Robert Ehrlich Summary: after a discussion with R.E., I submit a suggestion about improving the API of free Unices with useful features such as open(path,O_NULL); Dear Free *n*x Kernel Hackers, I've been

Re: All this and documentation too? (was: Microsoft performance (was: All this and documentation too? (was: cvs commit: src/sys/isa sio.c)))

1999-06-27 Thread Karl Pielorz
Greg Lehey wrote: I've come to understanding that lack of documentation is probably one of the factors that keep the system healthy, because it keeps the unskilled people away. I don't know whether it's true but I read in books that reading code is one of the methods to learn

Re: Improving the Unix API

1999-06-27 Thread Doug Rabson
On Sun, 27 Jun 1999, Alexander Viro wrote: On Sun, 27 Jun 1999, Doug Rabson wrote: This looks viable as long as you don't use small integers to represent FL_UFS etc. Having a single header defining constants for all filesystems Erm... sizeof(int)==4. I doubt that you will

Re: Improving the Unix API

1999-06-27 Thread der Mouse
(clri didn't work?) Never heard about clri (was under Linux). May not have existed, then, which *would* explain it. :-) Another problem was the ability to change the mount status of a partition from read-write to read-only or to unmounted, See NetBSD (and presumably other BSD) "mount -o

Re: Improving the Unix API

1999-06-27 Thread Alexander Viro
On Sun, 27 Jun 1999, der Mouse wrote: (clri didn't work?) Never heard about clri (was under Linux). May not have existed, then, which *would* explain it. :-) # debugfs -w /dev/sda1 debugfs: clri file debugfs: close It exists, all right ;-) Even documented - man 8 debugfs and there

Re: Improving the Unix API

1999-06-27 Thread Colin Wood
Alexander Viro wrote: asbestos underware[1] BTW, how does NetBSD deal with HFS cough forks? /asbestos underware easy, it doesn't :-) we don't currently have HFS support, mainly b/c the only freeware implementations of it (that i'm aware of) are GPL'd, and no one has been able to devote

Re: Inetd and wrapping.

1999-06-27 Thread John Baldwin
On 25-Jun-99 Aaron Smith wrote: On Fri, 25 Jun 1999 10:14:48 +0200, Sheldon Hearn writes: I think I prefer the suggestion I saw from someone else, which would allow ftp stream tcp nowait/10/10/wrap root ... This can be done in such a way as to be backward compatible. Looks like

Re: Inetd and wrapping.

1999-06-27 Thread John Baldwin
On 25-Jun-99 Drew Eckhardt wrote: In article [EMAIL PROTECTED] you write: Here's one possibility, it adds a a wrap/nowrap field that goes beside the wait/nowait field, so you would have: ftp stream tcp nowait wrap root /usr/libexec/ftpd ftpd -l Breaking backwards

Re: Inetd and wrapping.

1999-06-27 Thread Ben Rosengart
On Fri, 25 Jun 1999, David Malone wrote: Some people think that doing the hosts.allow lookup is too expensive for some services but not others. (It requires opening /etc/hosts.allow, reading it in line by line and possibly doing DNS lookups). I would hope that anyone concerned about speed

RE: setiathome crashes 3.2?

1999-06-27 Thread Richard Flores
unsubscribe freebsd-hackers end -Original Message- From: Thomas David Rivers [mailto:[EMAIL PROTECTED]] Sent: Sunday, June 27, 1999 7:09 PM To: [EMAIL PROTECTED] Subject: setiathome crashes 3.2? I seem to recall seeing this someone (this may not be the right list.) But -

Re: setiathome crashes 3.2?

1999-06-27 Thread Matthew Jacob
Umm- I've been running it for weeks on 3.2 with no problem. On Sun, 27 Jun 1999, Thomas David Rivers wrote: I seem to recall seeing this someone (this may not be the right list.) But - I downloaded the 3.2 Seti@home and starting running it on a left-over 75mhz laptop I have. It

Re: Inetd and wrapping.

1999-06-27 Thread Aaron Smith
On Sun, 27 Jun 1999 22:26:34 EDT, John Baldwin writes: Let's say I have two services, foo and bar, with food and bard. I want to wrap food, but *NOT* bard and they are both in /etc/inetd.conf. How do you propose to solve this with the internal wrapping (which is a good idea, IMO as it

Re: Volume managers (was: ufs/ffs resize?)

1999-06-27 Thread Bernd Walter
On Sun, Jun 27, 1999 at 09:33:45AM +0930, Greg Lehey wrote: On Sunday, 27 June 1999 at 0:35:54 +0200, Ollivier Robert wrote: I think one of the difficulty of growing a FS is that you have to choose whether you need the FS to be contiguous or not. The latter case makes it much more

Re: ufs/ffs resize?

1999-06-27 Thread sthaug
Another datapoint ot consider, it seems that Linux (at least the derivative version maintained by Alan Cox -- the other one :) ) has now grown an LVM system (probably à la HP or AIX). That's what I've been told yesterday during a small conference about Linux and free software in France

Re: [Re: [Re: coarse vs fine-grained locking in SMP systems]]

1999-06-27 Thread Matthew Dillon
Here's the basic problem: The kernel is currently designed for single-threaded operation plus interrupt handling. A piece of code in the kernel can temporarily disable certain interrupts with the spl*() codes to cover situations where a race on some system resource might

Re: [Re: [Re: coarse vs fine-grained locking in SMP systems]]

1999-06-27 Thread Warner Losh
In message 199906270733.aaa10...@apollo.backplane.com Matthew Dillon writes: : Here's the basic problem: The kernel is currently designed for : single-threaded operation plus interrupt handling. A piece of code : in the kernel can temporarily disable certain interrupts with the :

Re: ufs/ffs resize?

1999-06-27 Thread Greg Lehey
On Sunday, 27 June 1999 at 9:33:09 +0200, sth...@nethelp.no wrote: Another datapoint ot consider, it seems that Linux (at least the derivative version maintained by Alan Cox -- the other one :) ) has now grown an LVM system (probably à la HP or AIX). That's what I've been told yesterday

Improving the Unix API

1999-06-27 Thread Francois-Rene Rideau
Improving the Unix Kernels' API A Kernel Discussion with Hacker Robert Ehrlich Summary: after a discussion with R.E., I submit a suggestion about improving the API of free Unices with useful features such as open(path,O_NULL); Dear Free *n*x Kernel Hackers, I've been

Re: Improving the Unix API

1999-06-27 Thread Bill Sommerfeld
.. but there remained one that garbled meta-data had made into a non-existing block device, that would resist rm -f. He realized that the device had an immutable attribute. However, the problem is that to change the attribute, you have to open the file before you can ioctl() on it; BSD4.4

Re: Improving the Unix API

1999-06-27 Thread Werner Almesberger
Francois-Rene Rideau wrote: Robert told me that in some Unix flavors of old, it was possible to open a file by path with a null access mode (O_NULL ?) E.g. Linux. Very undocumented, but has been around for ages ('92 or such). The main purpose is to keep the floppy drive from spinning up to

Re: All this and documentation too? (was: Microsoft performance (was: All this and documentation too? (was: cvs commit: src/sys/isa sio.c)))

1999-06-27 Thread Karl Pielorz
Greg Lehey wrote: I've come to understanding that lack of documentation is probably one of the factors that keep the system healthy, because it keeps the unskilled people away. I don't know whether it's true but I read in books that reading code is one of the methods to learn programming.

Re: Improving the Unix API

1999-06-27 Thread Alexander Viro
On Sun, 27 Jun 1999, Bill Sommerfeld wrote: .. but there remained one that garbled meta-data had made into a non-existing block device, that would resist rm -f. He realized that the device had an immutable attribute. However, the problem is that to change the attribute, you have to

Re: Improving the Unix API

1999-06-27 Thread Bill Sommerfeld
Usage of ioctl() on Linux was a bad idea and it's going to be fixed. More or less in the same direction, not exactly the same - 4.4 chflags() works fine for UFS and leaves other filesystems to map what they can into the UFS set. Which is bogus - immutable is not a UFS attribute, it's VFS

Re: Improving the Unix API

1999-06-27 Thread der Mouse
He realized that the device had an immutable attribute. He tried to change the attribute with open() and ioctl() As I think someone already mentioned, BSD has chflags(), which takes a pathname. Robert had to hand-remove the immutable flag (I guess, by accessing the relevant block directly).

Re: Improving the Unix API

1999-06-27 Thread Alexander Viro
On Sun, 27 Jun 1999, Bill Sommerfeld wrote: Usage of ioctl() on Linux was a bad idea and it's going to be fixed. More or less in the same direction, not exactly the same - 4.4 chflags() works fine for UFS and leaves other filesystems to map what they can into the UFS set. Which is

Re: Improving the Unix API

1999-06-27 Thread Doug Rabson
On Sun, 27 Jun 1999, Alexander Viro wrote: On Sun, 27 Jun 1999, Bill Sommerfeld wrote: Usage of ioctl() on Linux was a bad idea and it's going to be fixed. More or less in the same direction, not exactly the same - 4.4 chflags() works fine for UFS and leaves other filesystems to

Re: Improving the Unix API

1999-06-27 Thread Bill Sommerfeld
Right. Except that UFS has not only generic attibutes. For example, you have UF_NODUMP and SF_ARCHIVED. The *only* place in the /sys you mention the former is sys/stat.h Well, right, because backup/restore aren't part of the kernel... (BTW, you don't even map it on EXT2_NODUMP_FL).

Re: Improving the Unix API

1999-06-27 Thread Alexander Viro
On Sun, 27 Jun 1999, Doug Rabson wrote: This looks viable as long as you don't use small integers to represent FL_UFS etc. Having a single header defining constants for all filesystems Erm... sizeof(int)==4. I doubt that you will need more. just doesn't scale at all. Sure.

Re: Improving the Unix API

1999-06-27 Thread Jan-Simon Pendry
Alexander Viro wrote: Proposed API on the Linux side being int chflags(name, level, oldp, newp); where level is FL_VFS for generic attirbutes (fs may map them on its own set) and FL_{UFS,EXT2,...} for raw flags - corresponding filesystem is free to interpret the thing as it likes and

[no subject]

1999-06-27 Thread W Gerald Hicks
To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message

Re: Improving the Unix API

1999-06-27 Thread Alexander Viro
On Sun, 27 Jun 1999, der Mouse wrote: Another problem was the ability to change the mount status of a partition from read-write to read-only or to unmounted, See NetBSD (and presumably other BSD) mount -o update,rdonly and/or umount -f. (Last I tried, the latter didn't work as it

Re: Improving the Unix API

1999-06-27 Thread Alexander Viro
On Sun, 27 Jun 1999, Jan-Simon Pendry wrote: Alexander Viro wrote: Proposed API on the Linux side being int chflags(name, level, oldp, newp); where level is FL_VFS for generic attirbutes (fs may map them on its own set) and FL_{UFS,EXT2,...} for raw flags - corresponding

ipfilter volunteer

1999-06-27 Thread Guido van Rooij
I'd like to volunteer to maintain ipfilter. I already told several people at the usenix conference, but as I have seen others taking interest as well, it seems right to at least spread it more publicly. I am still waiting for a machine I won at the conference to start on it though so it might

Re: building thread-safe Xlibs

1999-06-27 Thread Jeroen Ruigrok/Asmodai
* Francis Jordan (fran...@netscape.net) [990626 06:03]: xc/include/Xos_r.h which contains definitions of same (basically, pwd.h wrappers) for various platforms, but not FreeBSD (I guess at the time FreeBSD didn't have threads). Unfortunately, the wrappers for other platforms are no

Re: Improving the Unix API

1999-06-27 Thread Gandhi woulda smacked you
On Sun, 27 Jun 1999, der Mouse wrote: # Robert had to hand-remove the immutable flag # (I guess, by accessing the relevant block directly). # # (clri didn't work?) Obviously the guy thinks along the lines that you need a file descriptor to do things to files. That, or he didn't want to do an

sio2 often fails to initialize

1999-06-27 Thread Bart Trzynadlowski
Hi, I set about to reconfigure my kernel and everything works great except for sio2. My COM3 port is unusual, it has the port address 0x3e8 with an IRQ of 10 so I commented out the relevant sio2 line in my configuration file and replaced it with this: device sio2at isa? port 0x3e8

[Call for review] apmd for FreeBSD

1999-06-27 Thread Mitsuru IWASAKI
Hi, I'm ready to import apmd into freefall CVS repository. Now manpage (first version) and patch for CURRENT kernel were prepared :) Please review them before my commit. Any comments, suggestions, corrections are very appreciated. The latest (and final?) version of apmd package is available

Re: Microsoft performance (was: All this and documentation too?

1999-06-27 Thread Peter Jeremy
Nick Hibma hi...@skylink.it wrote: Programmers need documentation too. And they are going to scream like mad if there isn't any. But in the end they start reading the code anyway, even if there is docu, because they don't trust anything but their own eyes and brain. It's all documented in C

Re: Improving the Unix API

1999-06-27 Thread Francois-Rene Rideau
On Sun, Jun 27, 1999 at 12:58:05PM -0400, der Mouse wrote: As I think someone already mentioned, BSD has chflags(), [...] Yup. Robert had to hand-remove the immutable flag (I guess, by accessing the relevant block directly). (clri didn't work?) Never heard about clri (was under Linux). And I

Re: Improving the Unix API

1999-06-27 Thread Doug Rabson
On Sun, 27 Jun 1999, Alexander Viro wrote: On Sun, 27 Jun 1999, Doug Rabson wrote: This looks viable as long as you don't use small integers to represent FL_UFS etc. Having a single header defining constants for all filesystems Erm... sizeof(int)==4. I doubt that you will need

Re: Improving the Unix API

1999-06-27 Thread der Mouse
(clri didn't work?) Never heard about clri (was under Linux). May not have existed, then, which *would* explain it. :-) Another problem was the ability to change the mount status of a partition from read-write to read-only or to unmounted, See NetBSD (and presumably other BSD) mount -o

pseudo kernel dma/tee

1999-06-27 Thread Alfred Perlstein
Is there any support or plans for support of kernel dma, sort of like the aio stuff, however you just give the kernel two file descriptors and perhaps some parameters (such as seeking to a specific point on either or both files and amount of data to be sent) and the kernel will then do all the

Re: Improving the Unix API

1999-06-27 Thread Francois-Rene Rideau
On Sun, Jun 27, 1999 at 07:33:32PM -0400, der Mouse wrote: If you re-read the original message, the problem is what to do about processes with open file descriptors on the partition [...] Yes, that's the most difficult part. [...] NetBSD manpage: -f The filesystem is forcibly

Re: Improving the Unix API

1999-06-27 Thread Alexander Viro
On Sun, 27 Jun 1999, der Mouse wrote: (clri didn't work?) Never heard about clri (was under Linux). May not have existed, then, which *would* explain it. :-) # debugfs -w /dev/sda1 debugfs: clri file debugfs: close It exists, all right ;-) Even documented - man 8 debugfs and there

Re: Improving the Unix API

1999-06-27 Thread Jason Thorpe
On Sun, 27 Jun 1999 20:43:28 -0400 (EDT) Alexander Viro v...@math.psu.edu wrote: Forced revoke()? But then there is mmap() and IIRC revoke() on *BSD doesn't unmap the stuff. Oh, shit, there is such thing as pending unlink... Does vgone() force it? It doesn't unmap the region, but it

Re: Improving the Unix API

1999-06-27 Thread Alexander Viro
On Mon, 28 Jun 1999, Doug Rabson wrote: I'm talking about the concept of a header file containing something like: #define FL_VFS 0 #define FL_FOOFS1 #define FD_BARFS2 ... not being scalable. Do you have a complete list of filesystem

Re: Improving the Unix API

1999-06-27 Thread Alexander Viro
On Sun, 27 Jun 1999, Jason Thorpe wrote: Regarding unlink()... those aren't operations on vnodes. Those are operations on the filesystem namespace, and are thus (correctly) unaffected. Eh, wait. Those are operations on namespace, but at some moment you need to clean the bit in inode

Re: Improving the Unix API

1999-06-27 Thread Colin Wood
Alexander Viro wrote: asbestos underware[1] BTW, how does NetBSD deal with HFS cough forks? /asbestos underware easy, it doesn't :-) we don't currently have HFS support, mainly b/c the only freeware implementations of it (that i'm aware of) are GPL'd, and no one has been able to devote enough

Re: Improving the Unix API

1999-06-27 Thread allbery
On 27 Jun, Jason Thorpe wrote: +- | Alexander Viro v...@math.psu.edu wrote: |doesn't unmap the stuff. Oh, shit, there is such thing as pending |unlink... Does vgone() force it? | | Regarding unlink()... those aren't operations on vnodes. Those are | operations on the filesystem

Re: Improving the Unix API y,

1999-06-27 Thread Brian F. Feldman
On Sun, 27 Jun 1999, Alexander Viro wrote: As for the opening with no permissions - well, it would make *big* sense if we could narrow down the API and move chown(), chmod(), etc. into libc leaving f-variants in the kernel. Binary compatibility... Extreme variant might include

Re: Improving the Unix API

1999-06-27 Thread allbery
On 27 Jun, To: thor...@nas.nasa.gov wrote: +- | (To which my own answer would be: deallocated on close as usual, no | reason to treat this case specially that I know of.) +---8 Strike that, I was on the wrong page. (Crossed threads re: general revoke() on Linux) -- brandon s. allbery

Re: Improving the Unix API

1999-06-27 Thread Alexander Viro
On Sun, 27 Jun 1999 allb...@ece.cmu.edu wrote: On 27 Jun, Jason Thorpe wrote: +- | Alexander Viro v...@math.psu.edu wrote: |doesn't unmap the stuff. Oh, shit, there is such thing as pending |unlink... Does vgone() force it? | | Regarding unlink()... those aren't

setiathome crashes 3.2?

1999-06-27 Thread Thomas David Rivers
I seem to recall seeing this someone (this may not be the right list.) But - I downloaded the 3.2 s...@home and starting running it on a left-over 75mhz laptop I have. It seems to crash the laptop (silently lock it up, actually) fairly quickly. Did I recall someone else mentioning that?

Re: Improving the Unix API

1999-06-27 Thread der Mouse
-f The filesystem is forcibly unmounted. Active special devices continue to work, but all other files return errors if further accesses are attempted. I think that returning errors is WRONG, unless [...] It means that you can't fix the problem with the

Re: Inetd and wrapping.

1999-06-27 Thread John Baldwin
On 25-Jun-99 Aaron Smith wrote: On Fri, 25 Jun 1999 10:14:48 +0200, Sheldon Hearn writes: I think I prefer the suggestion I saw from someone else, which would allow ftp stream tcp nowait/10/10/wrap root ... This can be done in such a way as to be backward compatible. Looks like

Re: Inetd and wrapping.

1999-06-27 Thread John Baldwin
On 25-Jun-99 Drew Eckhardt wrote: In article 199906242353.taa06...@smtp4.erols.com you write: Here's one possibility, it adds a a wrap/nowrap field that goes beside the wait/nowait field, so you would have: ftp stream tcp nowait wrap root /usr/libexec/ftpd ftpd -l

Re: Inetd and wrapping.

1999-06-27 Thread Ben Rosengart
On Fri, 25 Jun 1999, David Malone wrote: Some people think that doing the hosts.allow lookup is too expensive for some services but not others. (It requires opening /etc/hosts.allow, reading it in line by line and possibly doing DNS lookups). I would hope that anyone concerned about speed

RE: setiathome crashes 3.2?

1999-06-27 Thread Richard Flores
unsubscribe freebsd-hackers end -Original Message- From: Thomas David Rivers [mailto:riv...@dignus.com] Sent: Sunday, June 27, 1999 7:09 PM To: freebsd-hackers@FreeBSD.ORG Subject: setiathome crashes 3.2? I seem to recall seeing this someone (this may not be the right list.)

Re: setiathome crashes 3.2?

1999-06-27 Thread Matthew Jacob
Umm- I've been running it for weeks on 3.2 with no problem. On Sun, 27 Jun 1999, Thomas David Rivers wrote: I seem to recall seeing this someone (this may not be the right list.) But - I downloaded the 3.2 s...@home and starting running it on a left-over 75mhz laptop I have. It

Re: Inetd and wrapping.

1999-06-27 Thread Aaron Smith
On Sun, 27 Jun 1999 22:26:34 EDT, John Baldwin writes: Let's say I have two services, foo and bar, with food and bard. I want to wrap food, but *NOT* bard and they are both in /etc/inetd.conf. How do you propose to solve this with the internal wrapping (which is a good idea, IMO as it eliminates