Hi everyone,
I have noticed quite some time ago a strange way in which some basic
FreeBSD utilities work, related to symlinks. Example session:
bgd@cvs$ mkdir temp
bgd@cvs$ ln -s temp b
bgd@cvs$ ls -ald temp b
lrwxr-xr-x 1 bgd wheel4 Apr 9 11:27 b -> temp
drwxr-xr-x 2 bgd whe
"Crist J. Clark" wrote:
> > file is created in /etc; it does the right thing, if the
> > symlink is read-only, though...).
>
> Exactly, you can't use symlinks with the passwd(1) and pwd_mkdb(8)
> commands as they stand. The commands will bail when they try to create
> a temporary file in /etc, /e
[EMAIL PROTECTED] wrote:
> }> You could say that X11 shouldn't use SHMs the way it does now yeah. =)
> }The real problem is that over the UNIX domain socket, it doesn't
> }get client disconnect notificiations necessary for resource tracking,
> }AND browser use of these resources is practically the
On Tue, Apr 09, 2002 at 04:42:52PM -0700, Terry Lambert wrote:
> Julian Elischer wrote:
> > As terry knows of course, the Interjet
> > had the following /etc/symlinks: (excuse linewrap)
> > lrwxrwxrwx 1 root wheel 20 Mr 28 2001 crontab@ ->
> > /writable/system/crontab
> > lrwxrwxrwx 1
Hey Hackers,
I'm new to the BSD world, and wanted to install 4.5-Stable.
I downloaded the ISO, made the floppies and ran into a snag:
Hard drive is an IDE and the CDROM is SCSI on an Adaptec 2940
(ahc).
It appears (i would love to be wrong) that the Boot floppies
only have support for the aha
FWIW,
This has been fixed in current, kern/kern_exit.c revision 1.147.
Someone should MFC it.
Callum Gibson [EMAIL PROTECTED]
Global Markets IT, Deutsche Bank, Australia 61 2 9258 1620
### The opinions in this message are mine and not Deutsche's ###
To Unsubsc
I have a theory (and a patch) if you're willing to hear it.
[EMAIL PROTECTED] writes:
}> I'd like to take a step further and say it's in SYSVSHM design. All a
}> program has to do is forget to do a shm_detach() and you're f#$%ed.
}Heh. I could make the same argument about "open"...
Except that
Julian Elischer wrote:
> As terry knows of course, the Interjet
> had the following /etc/symlinks: (excuse linewrap)
> lrwxrwxrwx 1 root wheel 20 Mr 28 2001 crontab@ ->
> /writable/system/crontab
> lrwxrwxrwx 1 root wheel 18 Mr 28 2001 group@ ->
> /writable/system/group
[
"Rogier R. Mulhuijzen" wrote:
> >This is a bug in the MIT shared memory extension for X design,
> >and can't be fixed for long running programs with lots of
> >bitmaps.
>
> I'd like to take a step further and say it's in SYSVSHM design. All a
> program has to do is forget to do a shm_detach() and
On Tue, 9 Apr 2002, Terry Lambert wrote:
> "Crist J. Clark" wrote:
> > On Mon, Apr 08, 2002 at 09:13:12PM -0700, Terry Lambert wrote:
> > [snip]
>
> It depends. If this is a truly multiuser environment, then
> you are probably getting your authentication from NIX or RADIUS.
>
> It's really a
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
At 22:06 8-4-2002 -0700, Terry Lambert wrote:
>All you are doing is marking the segment as removed. The segment
>remains attached by the processes which have it open, and those
>references don't go awaya until the processes in question detach
>the segments, and the reference count goes to zero.
At 8:45 PM +1000 4/9/02, [EMAIL PROTECTED] wrote:
>Please don't make me use the kernel debugger... waa
I believe Terry suggested:
...set the DISPLAY environment variable so that it uses a
real network connection, instead of a UNIX domain socket
(and thus allows the use of the MIT SH
subscribe freebsd-hackers [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
[EMAIL PROTECTED] writes:
}I believe this will give incorrect information, as it's pretty
}obvious that any bug here has to be in the Linux ABI treatment
}of the _exit() resource tracking cleanup of the segments when a
}proce (or "Linux thread") exits. The information "-p" gives is
}the last acce
Bob Bishop wrote:
> If you have any permissions on the file, you can prolong its life without a
> link simply by having a process open it. This is 'better' as a DOS because
> it's harder to spot.
Plus you can start a bunch of processes, dup the thing, an then
pass it around amoung the processes s
"Crist J. Clark" wrote:
> On Mon, Apr 08, 2002 at 09:13:12PM -0700, Terry Lambert wrote:
> [snip]
>
> > It's arguable that "/" and "/usr" themselves should be
> > mounted read-only,
>
> It's not very practical to have / read-only on a truely multi-user
> (the only time this linking stuff is much
Hi,
At 11:41 08/04/02 -0700, Michael Smith wrote:
> > On Mon, 8 Apr 2002, [ISO-8859-2] Pawe³ Jakub Dawidek wrote:
> >
> > > Simple example why I think that only owner should have permission to
> create
> > > hardlinks to his files.
>...
> > I see you forgot to 'ls -l' the resultant link ... you'
Andrew wrote:
> On Tue, 9 Apr 2002 [EMAIL PROTECTED] wrote:
> > I replied privately to Terry, but I perhaps should have mentioned also
> > that some of these segments were days old and they were definitely not
> > in use by any process. I logout at the end of every day.
>
> Have you tried ipcs -p
[EMAIL PROTECTED] wrote:
> I replied privately to Terry, but I perhaps should have mentioned also
> that some of these segments were days old and they were definitely not
> in use by any process. I logout at the end of every day.
Logging out does not necessarily stop all processes, or remove
the
At the risk of clogging up -hackers with this, I'm not going crazy...
[EMAIL PROTECTED] writes:
}> I replied privately to Terry, but I perhaps should have mentioned also
}> that some of these segments were days old and they were definitely not
}> in use by any process. I logout at the end of ever
On Mon, Apr 08, 2002 at 09:13:12PM -0700, Terry Lambert wrote:
[snip]
> It's arguable that "/" and "/usr" themselves should be
> mounted read-only,
It's not very practical to have / read-only on a truely multi-user
(the only time this linking stuff is much of an issue) 4-STABLE
system. The two m
22 matches
Mail list logo
