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 hav
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.
>
> >
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
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 a
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,.
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 th
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 fil
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 bitm
On Sun, 27 Jun 1999 allb...@ece.cmu.edu wrote:
> On 27 Jun, Jason Thorpe wrote:
> +-
> | Alexander Viro wrote:
> | > doesn't unmap the stuff. Oh, shit, there is such thing as pending
> | > unlink... Does vgone() force it?
> |
> | Regarding unlink
On Mon, 28 Jun 1999, Alan Cox wrote:
> > As far as sysctl goes, FreeBSD deprecates the use of numbers for OIDs and
> > has a string-based mechanism for exploring the sysctl tree.
>
> So we are actually both going the same way. Linus with /proc/sys and his
> official dislike of sysctl (Oh well I
On Mon, 28 Jun 1999, Doug Rabson wrote:
> As far as I know, only FreeBSD has a string-based sysctl implementation.
> Something which always confused me about Linux' procfs - what have all
> these kernel variables got to do with process state? We used to have a
Nothing. procfs is a union of 4 f
On Mon, 28 Jun 1999, David S. Miller wrote:
>Date: Mon, 28 Jun 1999 06:12:44 -0400 (EDT)
>From: Alexander Viro
>
>3) openpromfs - sparc only (?), AFAICS not actively maintained.
>
> Oh, it's maintained and used every day, believe me.
Cool ;-) There is
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 t
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 fi
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 bit
On Mon, 28 Jun 1999, Doug Rabson wrote:
> As far as I know, only FreeBSD has a string-based sysctl implementation.
> Something which always confused me about Linux' procfs - what have all
> these kernel variables got to do with process state? We used to have a
Nothing. procfs is a union of 4
On Mon, 28 Jun 1999, David S. Miller wrote:
>Date: Mon, 28 Jun 1999 06:12:44 -0400 (EDT)
>From: Alexander Viro <[EMAIL PROTECTED]>
>
>3) openpromfs - sparc only (?), AFAICS not actively maintained.
>
> Oh, it's maintained and used every day, bel
17 matches
Mail list logo
