In article [EMAIL PROTECTED] you write:
Brian Fundakowski Feldman wrote:
It sounds to me that what you really want are the semantics of a
symbolic link and not the semantics of a hard link. Is it just me,
or does it seem as if the pathname of the executable being stored as
a virtual symlink
Err... I don't see the problem. The permissions of the hardlink will
be different, so the user might be able to see the "code", but won't
be able to run the suid (because the hardlink won't have the suid
bit set).
Suid bit is stored in the inode, not the directory entry, so it will
be set.
You can make hard links to
No, you cannot.
Yes you can - you just need to make sure the target directory is on
the same filesystem as the *original* file.
11:30:gonzo 9% cp /bin/sleep /tmp
11:30:gonzo 10% ls -l /tmp/sleep*
-r-xr-xr-x 1 dwmalone wheel 45224 Nov 7 11:30 /tmp/sleep
On Sun, Nov 07, 1999 at 05:44:51PM +0900, Daniel C. Sobral wrote:
Actually, use fstat to check against ftpd, and lockf between the
scripts. :-)
Good idea :) I think that I'll do just that.
Cheers,
--
Jos Backus _/ _/_/_/"Modularity is not a hack."
Kevin Day [EMAIL PROTECTED] writes:
The problem is that 'fsck -py' ignores the 'p' and will fsck every time,
even if it's unneeded. This takes ages for me. I believe I submitted a PR
with a 'fix' to fsck.
'fsck -p || fsck -y' should do the trick.
DES
--
Dag-Erling Smorgrav - [EMAIL
To whoever that may interest, I've now got a nearly working freebsd
loader for the NetWinder. It currently only uses the serial console and
miss internal hard driver support but work is underway for both these
issues.
I'm making some progress too in getting world to compile but work in
this area
On Sun, 7 Nov 1999, Stephane E. Potvin wrote:
To whoever that may interest, I've now got a nearly working freebsd
loader for the NetWinder. It currently only uses the serial console and
miss internal hard driver support but work is underway for both these
issues.
I'm making some progress
On Sun, 7 Nov 1999, Sean Eric Fagan wrote:
I don't, but what I like doesn't matter, it seems -- Warner knows everything.
So I'm sure he knows better than I do the overhead this will impose, and the
impracticality in a general system.
Unix really isn't set up to carry around 'official
On Sat, 6 Nov 1999, Warner Losh wrote:
There are ways that the user can see the code to execute it, but not
read it normally. procfs breaches this inability to read the file.
Also, there are many related problems which make a proper fix for this
that is more complicated than removing
To whoever that may interest, I've now got a nearly working freebsd
loader for the NetWinder. It currently only uses the serial console and
miss internal hard driver support but work is underway for both these
issues.
Cool! Does the NetWinder use OpenFirmware, or some other firmware
Mike Smith wrote:
To whoever that may interest, I've now got a nearly working freebsd
loader for the NetWinder. It currently only uses the serial console and
miss internal hard driver support but work is underway for both these
issues.
Cool! Does the NetWinder use OpenFirmware, or
On Sun, Nov 07, 1999 at 04:57:54PM +0100, Dag-Erling Smorgrav wrote:
Kevin Day [EMAIL PROTECTED] writes:
The problem is that 'fsck -py' ignores the 'p' and will fsck every time,
even if it's unneeded. This takes ages for me. I believe I submitted a PR
with a 'fix' to fsck.
'fsck -p ||
At work we have 18 or so web servers runing FreeBSD 3.0 on daul PIIs.
When they see very high loads (~300+) the SMP starts do get confused
and things randomly fail.
Were there signifigant SMP changes from 3.0-RELEASE to 3.3-RELEASE
that may make SMP more stable at high loads? Are their any
Why trying to debug some locking code of my own I enabled
SIMPLELOCK_DEBUG, only to find out that I was getting lots of
`simple_unlock: lock not held' in lockmgr - acquire - apause.
Looking closer at `apause' it seems rather clear that it can cause
this. I proposed simple change is below.
:well, I am working on writing a capture program to do 640x480x12bpp@30fps
:to a raw disk, but writing to the raw device is SOOO slow... the reason
:I say it's slow is the fact that it takes 8 times the system time writing
:than reading...
:
:a bit about the system... k6/2-250, 100mhz system
* Matthew Dillon
| FreeBSD boxes can handle up to 4 Gigabytes of main memory.
Is this true for the Alpha kernels too?
--
Andreas Dobloug : email: [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
16 matches
Mail list logo
