Is there a particular reason why there's no capability for setting flags
on symlinks? the chflags syscall uses namei with FOLLOW, and changing this
to NOFOLLOW allows chflags(2) to Do What I Want (i.e. SF_IMMUTABLE on a
VLNK)
is there a filesystem train crash awaiting me for doing this, or am I
I tought that some might be interested by this:
Copyright (c) 1992-2001 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
sysinit->subsystem 0x0081
FreeBSD 5.0-CURRENT #271: S
I *am* interested by any progress on an ARM machine : I don't yet have
resources to work on such a beast, but I thought on installing NetBSD on
one of our ARM eval boards.
If this is FreeBSD, all the better ...
TfH
PS : a fuller dmesg will be appreciated (along with more detail on your
On Sat, 21 Jul 2001, Arun Sharma wrote:
> Greetings. I'm trying to port an application to FreeBSD. I have
> a signal handler registered using signal(2). It modifies the
> data pointed to by the third argument - of type sigcontext (specifically
> sc_eip) - so that the execution would resume at a di
Hello,
using my ugly hack to do file i/o from a module, I discovered some
problem calling mmap() from a function with a lot of local buffers
defined. I have:
char * pizda_malloc(struct proc *p, int size)
{
struct mmap_args mem; int res; register_t save; char *buf;
save = p->p_retval[0];
mem.
From: "Stephane E. Potvin" <[EMAIL PROTECTED]>
Subject: FreeBSD for ARM processor
Date: Sun, 22 Jul 2001 12:43:27 +
> I tought that some might be interested by this:
>
> Copyright (c) 1992-2001 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
>
:David Malone wrote (2001/06/11):
:> On Sun, Jun 10, 2001 at 05:20:50PM -0700, Peter Wemm wrote:
:> > I agree totally. This should have been done ages ago, I've been burned on
:> > it a few times, but never badly enough to go fix it.
:>
:> I've committed this - I'll let Matt do the MFC when he
:could anyone think about MFC FFS dirpref code?
:is it still not enough stable in CURRENT?
:I heard OpenBSD 2.9 has it already.
Kirk aksed me to do in a month or two ago. It's been on my TODO list
but I haven't had time to do it yet. It's still on my TODO list.
But if someone els
:
:
::could anyone think about MFC FFS dirpref code?
::is it still not enough stable in CURRENT?
::I heard OpenBSD 2.9 has it already.
:
:Kirk aksed me to do in a month or two ago. It's been on my TODO list
:but I haven't had time to do it yet. It's still on my TODO list.
ARRRG
On Sun, Jul 22, 2001 at 12:01:46PM -0700, Matt Dillon wrote:
>
> :
> :
> ::could anyone think about MFC FFS dirpref code?
> ::is it still not enough stable in CURRENT?
> ::I heard OpenBSD 2.9 has it already.
> :
> :Kirk aksed me to do in a month or two ago. It's been on my TODO list
> :b
At 12:43 PM + 7/22/01, Stephane E. Potvin wrote:
>I thought that some might be interested by this:
>
>Copyright (c) 1992-2001 The FreeBSD Project.
>Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
> The Regents of the University of California. All rights reserve
* Stephane E. Potvin <[EMAIL PROTECTED]> [010722 07:57] wrote:
> I tought that some might be interested by this:
>
> Copyright (c) 1992-2001 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
> The Regents of the University of California. All r
Bakul Shah wrote:
> > Flags are associated with inodes, and symlinks do not have
> > inodes in the common case, as they exist solely in the
> > directory entry, unless they are too long.
>
> $ mkdir foo; cd foo; date > x; ln -s x y; ls -lai
> total 3
> 261248 drwxr-xr-x 2 bakul bakul 512 Jul 2
Terry Lambert <[EMAIL PROTECTED]> writes:
> Flags are associated with inodes, and symlinks do not have
> inodes in the common case, as they exist solely in the
> directory entry, unless they are too long.
Hu? The contents of the link will be stored in the inode itself
rather than in data blocks
On Sun, Jul 22, 2001 at 12:47:07PM -0700, Terry Lambert wrote:
> Bruce Evans wrote:
> > > Is there a particular reason why there's no capability for setting flags
> > > on symlinks? the chflags syscall uses namei with FOLLOW, and changing this
> > > to NOFOLLOW allows chflags(2) to Do What I Want
On Sun, 22 Jul 2001, Terry Lambert wrote:
> In fact, "man chflags", and look at the "-L" argument... I
> could make a good argument that it should operate on the
> link itself, if given a "-l" (currently unused) argument.
That was my expected result until I read the manpage completely and
follo
On Sun, 22 Jul 2001, Matt Dillon wrote:
> :Kirk aksed me to do in a month or two ago. It's been on my TODO list
> :but I haven't had time to do it yet. It's still on my TODO list.
>
>ARRRG
>
>Kirk ASKED me to do IT a month or two ago. Sorry, that's worse then
>my typic
* Mike Silbersack <[EMAIL PROTECTED]> [010722 16:57] wrote:
>
> On Sun, 22 Jul 2001, Matt Dillon wrote:
>
> > :Kirk aksed me to do in a month or two ago. It's been on my TODO list
> > :but I haven't had time to do it yet. It's still on my TODO list.
> >
> >ARRRG
> >
> >Kirk
On Sun, 22 Jul 2001, Alfred Perlstein wrote:
> * Mike Silbersack <[EMAIL PROTECTED]> [010722 16:57] wrote:
> > >Kirk ASKED me to do IT a month or two ago. Sorry, that's worse then
> > >my typical typing, I was thinking about something else at the time and
> > >left my fingers on aut
Hi,
I've attached a patch that adds a functions for zone destruction to
the kernel zone allocator, which is needed to properly support the
unload case for modules that create zones (such as nfs.ko).
As a first application of this, it also patches the relevant nfs code
to destroy the internal nfs
At one stage at whistle we had the kernel fully cross-referenced
using the 'global' program (now in ports) which produced
a website that could be browsed to find
'all the callers of xxx()' etc.
does anyone have such a site online at the moment?
--
++ __
21 matches
Mail list logo
