Manpage 'man 2 fork' says:
'File locks ... are not inherited.'
This is true for POSIX locks, but not for flock-type locks.
This phrase comes directly from posix fork manpage,
which is not aware of flock-style locks.
Maybe fork manpage should rather say:
... POSIX file
Sorry for the screwed subject line. Should have been:
Subject: manual page 'man 2 fork' wrt file locks
Yakov
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
P
Manual page 'man 2 fork' says:
'File locks ... are not inherited.'
This is true for POSIX locks (fcntl-style locks).
But flock-style locks (aka bsd-style locks) are not inherited across
fork, correct ?
Would not it be more helpful if fork manpage said:
POSIX file locks
>From the userlevel, can I get an estimate of "amount of entropy"
in /dev/random, that is, the estimate of number of bytes
readable until it blocks ? Of course multiple processes
can read bytes and this would not be exact ... but still .. as an upper
boundary estimate ?
Thanks
Yakov
-
To unsubscr
On 8/15/07, Marc Perkel <[EMAIL PROTECTED]> wrote:
> I want to throw out some concepts about a new way of
> thinking about file systems. But the first thing you
> have to do is to forget what you know about file
> systems now. This is a discussion about a new view of
> looking a file storage that i
kernels ?
Yakov Lerner
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On 2/14/07, sfaibish <[EMAIL PROTECTED]> wrote:
On Sat, 10 Feb 2007 22:06:37 -0500, Sorin Faibish <[EMAIL PROTECTED]> wrote:
> Introducing DualFS
>
> File System developers played with the idea of separation of
> meta-data from data in file systems for a while. The idea was
> lately revived by a
Does /proc have any entries to flip the "software read-only flag"
for a partition or disk (which are physically read-write) ?
Yakov
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org
On a small Celeron-based appliance, Usb2 disk is not recognized *if*
it is connected during kernel boot.
But if not connected during boot, and I connect it later, it is
recognized and works ok.
I tried various 2.6.16, 17 and 18 kernels, both modular, and
all-static, with the same result.
What can
How can I get serial_no from usb-attached HD drive ?
The HDIO_GET_IDENTITY ioctl fails (like 'hdparm -i').
Any advice on how to extract the drive serialNo from the usb disk ?
Can I write kernel module to extract the SerialNo ?
(I don't need whole 'struct hd_driveid', only the SerialNo).
Thanks
Y
Is it easily possible to build two architectures in
the same source tree (so that intermediate fles
and resut files do not interfere ) ?
Thanks
Yakov
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at htt
te modified data between in between my read-write pair.
Yakov
Yakov Lerner wrote:
> I'd like to make read-write test of the raw disk, and disk has
> mounted partitions. Is it possible to lock range of sectors
> of the raw device so that any kernel code that wants to write
> to
12 matches
Mail list logo
