Re: Sticky/sgid/suid bits safe on regular files?

2004-06-17 Thread Cyrille Lefevre
"Clifton Royston" <[EMAIL PROTECTED]> wrote: [snip] > Can anybody confirm for me that the suid, sgid, and sticky bit are in > fact no-ops for FreeBSD on regular non-executable files, as it appears > they should be? how about the use of hard link which is not os depedent ? if ln source .source;

Re: why timeradd() and co are hidden from the kernel space ?

2004-06-17 Thread Cyrille Lefevre
"Bruce Evans" <[EMAIL PROTECTED]> wrote: > On Thu, 17 Jun 2004, Cyrille Lefevre wrote: > > > is there any reasons to hide timeradd() and co in > > from the kernel space (! _KERNEL) ? > > Yes. This prevents them being used in the kernel. They are compatibility > cruft for NetBSD. In the kernel

Sticky/sgid/suid bits safe on regular files?

2004-06-17 Thread Clifton Royston
I need to add a feature to an application where it can keep tabs on whether one specific action has ever been taken on any given file, one of possibly hundreds of thousands of a dynamically changing file set. The files might reside either on an NFS server or on local storage, and may ultimately

Re: Regarding procfs in freeBSd

2004-06-17 Thread Brian Fundakowski Feldman
On Thu, Jun 17, 2004 at 03:28:47PM +0530, ravi wrote: > Hi, > How to get a pointer to pfs_info structure which points to the /proc > directory ? > > I mean , I want to create a proc entry under /proc . > But for this I need to pass an argument struct pfs_info *pi, which > contains a member p

Re: [current tinderbox] failure on amd64/amd64

2004-06-17 Thread Max Laier
On Thursday 17 June 2004 15:21, Maxime Henrion wrote: > It's actually not correct. The scounters[i] here is of type u_int64_t, > so long is not the correct format here (longs are 32bit on many 32bit > architectures such as FreeBSD/i386). The correct format to use here is > %llu (long long's are a

why timeradd() and co are hidden from the kernel space ?

2004-06-17 Thread Cyrille Lefevre
Hi, is there any reasons to hide timeradd() and co in from the kernel space (! _KERNEL) ? how about to remove #ifndef _KERNEL/#endif ? CC -hackers Cyrille Lefevre. -- home: mailto:[EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.fre

Re: [current tinderbox] failure on amd64/amd64

2004-06-17 Thread Maxime Henrion
Liam J. Foy wrote: > On Thu, 17 Jun 2004 05:47:25 -0400 (EDT) > FreeBSD Tinderbox <[EMAIL PROTECTED]> wrote: > > > TB --- 2004-06-17 08:56:11 - tinderbox 2.3 running on freebsd-current.sentex.ca > > TB --- 2004-06-17 08:56:11 - starting CURRENT tinderbox run for amd64/amd64 > > TB --- 2004-06-17 0

Re: [current tinderbox] failure on amd64/amd64

2004-06-17 Thread Liam J. Foy
On Thu, 17 Jun 2004 05:47:25 -0400 (EDT) FreeBSD Tinderbox <[EMAIL PROTECTED]> wrote: > TB --- 2004-06-17 08:56:11 - tinderbox 2.3 running on freebsd-current.sentex.ca > TB --- 2004-06-17 08:56:11 - starting CURRENT tinderbox run for amd64/amd64 > TB --- 2004-06-17 08:56:11 - checking out the sour

Regarding procfs in freeBSd

2004-06-17 Thread ravi
Hi, How to get a pointer to pfs_info structure which points to the /proc directory ? I mean , I want to create a proc entry under /proc . But for this I need to pass an argument struct pfs_info *pi, which contains a member pi_root which inturn points to the /proc's pfs_node How to get th