what's the maximum swap size
See mkswap(8), making sure you have a non-ancient page
(one that mentions Linux 2.1.117).
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
The "none" bit puzzles me the most.
It is a common misconfiguration. Given a line
device dir type options garbage
in /etc/fstab, some umount versions will complain "device busy"
when the umount fails. Thus, it is better to use
proc/proc proc
devpts /dev/pts devpts
The signature on man-pages-1.34.tar.gz is bad:
Hmm, thought I had corrected that already.
Is it correct now?
Andries
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
From: Chris Wedgwood [EMAIL PROTECTED]
On Thu, Jan 11, 2001 at 09:34:08PM -0500, Michael Rothwell wrote:
The man pages for open, read and write say that if a file is opened
using the O_NONBLOCK flag, then read() and write() will always return
immediately and not
the patch locates partitions inside the plan9
i can't find anyone with plan9 to test,
I'll have a look.
A week ago you sent almost the same patch.
Was there a reason to change __u32 into unsigned long?
Andries
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
Matti Aarnio writes:
And the partitions are PHYSICAL partition numbers,
not some logical ones.
That is very interesting. Can you explain to me what
physical partition numbers are?
Andries
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
From: Anton Altaparmakov [EMAIL PROTECTED]
Subject: Getting the number of 512-byte sectors?
My question is how to get the _real_ number of sectors of a partition from
within a file system. I.e. we are starting only with the knowledge of the
struct super_block for the
does partitioning slow things down?
No.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Andreas Dilger writes:
: What would be wrong with changing the kernel to skip the first page
: of swap, and allowing us to put a signature there?
Swap space already has a signature. Read mkswap(8).
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
Andrew Clausen writes:
can anyone remember why we have partition IDs?
Partition IDs are not necessary. Linux works fine
when you have no partition table at all, and have a
parttab file in an initrd disk telling the kernel where
the partitions are supposed to be.
No kernel changes required.
Andreas Dilger wrote:
It would already be possible to auto-enable any devices with the swap
signature by doing the same sort of search mount(8) is doing for LABEL
and UUID.
That would be a very poor idea.
Since different filesystems have signatures in different places,
a partition may well
Mark Lord writes:
Even better would be to add a stage in front of the fall-back,
which queries the BIOS (from kernel startup code) for translation
info on ALL drives.
It doesn't work.
I wrote the code and asked people to test it.
So many BIOS quirks.
(Numbering of drives depends on setup
In my case, I have two identical Maxtor drives, but they reported
different geometry. How could that be?
A FAQ.
Read "14.2 Nonproblem: Identical disks have different geometry?"
http://www.win.tue.nl/~aeb/linux/Large-Disk-14.html#ss14.2
-
To unsubscribe from this list: send the line
Andreas Huppert wrote:
I have been trying to mount the dos-partition /dev/hdb1 on /dos/d for
three years and it fails:
Yes. It has 805998 data sectors, which require 50374 clusters,
but the fat16 has room only to describe 39168 clusters.
The kernel mount code considers this an error.
You
Now that on-board ethernet on the lp486e (also known as
lpe486 and as elp486 and as PWS and as `Reuters') works
out of the box under 2.2.19, people started asking about 2.4.
A patch is found at
ftp.XX.kernel.org/.../kernel/people/aeb/lp486e.c-for-2.4.4
It works (has gotten all of two minutes
From: Martin Dalecki [EMAIL PROTECTED]
The attached patch is fixing georgeous backward compatibility
in the mount system command. It is removing two useless defines in
the kernel headers and finally doubles the number of possible
flags for the mount command.
Please
20:12 is more common
Which is major, which is minor?
20bit major
That is not more common. Around us we see major:minor splits
8:24, 12:20, 14:18. If we want to use NFSv3 and communicate
with all these systems we would do wise to use 32:32.
[Reminds me of a discussion that ended unfinished.
The fs and stat structs are set up to allow 32bits.
64bits is a major exercise
No. Inside the kernel the dev_t type does not really occur.
The exercise is essentially the patch that I sent last month or so.
Andries
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the
The exercise is essentially the patch that I sent last month or so.
mknod takes a 32bit input
the stat64 padding only has room for 32bits
Hmm. You make me search for this old patch.
Since Linus' reaction was not exactly positive I left
the topic again, but there must be a copy somewhere..
Im very interested in 32bit dev_t or at least implementing
the 'lots of majors' half of it because we are probably
going to need it in the 2.5 years before we have a 2.6
Yes, a larger dev_t has been desirable for a long time,
and more and more kludges are invented to work around its lack.
If I am not mistaken, Richard Hirst has also done work on this thing.
He did 53c710+. The 700 and 700/66 are much less capable devices.
Yes. But long ago he wrote:
---
You need quite a different driver from the 53c710 drivers that
exist, because 53c700 doesn't have DSA register. I've
New SCSI driver for 53c700 chip
Good!
If I am not mistaken, Richard Hirst has also done work on this thing.
The Panther/lp486e/PWS/... has on-board ethernet (82596)
and this now works under both 2.2 and 2.4.
It also has on-board SCSI (NCR 53c700-66), maybe memory mapped,
I forget. Maybe
The LANANA discussion has forked into a forest of vaguely related
discussions. If I am not mistaken the only real question is
how user space and kernel space communicate device identities.
Here user space is very different from users.
Devices have a device path and device contents.
For the
I disagree that the kernel should apply sequence numbers
You did not read my text. I do not propose the kernel should.
(Quite the contrary, in fact.)
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Someone complained a moment ago about the error return in unlink.
And indeed, it used to be correct but since 2.1.132 we return a
buggy (or at least non-POSIX) error for unlink(directory).
Just changed the man page to say
unlink(2)
...
EPERM The system does not allow unlinking of
IMO that's the case of POSIX being misapplied. Rationale:
* historically, ...
Yes, I know all about that.
Nevertheless the facts are here:
EPERM The system does not allow unlinking of directories,
or unlinking of directories requires privileges
that
What are the units of the return value of the BLKGETSIZE ioctl on Linux?
Sectors of size 512.
or is it in units of sector size bytes as returned by BLKSSZGET
No.
Andries
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
root@bug:/zip# mount /zip
root@bug:/zip# ls -al
total 8
drwxr-xr-x2 root root 4096 Dec 1 08:29 .
drwxr-xr-x 31 65534root 4096 Apr 24 20:56 ..
root@bug:/zip# cd /zip
root@bug:/zip# ls -al
total 22182
...
Is that okay?
Yes. Your working directory does not
Getting a list of all ioctls in the tree, along with types of their arguments
would be a great start. Anyone willing to help with that?
% man 2 ioctl_list
gives a very outdated list. Collecting the present list is trivial
but time-consuming. If anyone does I would be happy if he also
sent me
From: Ben LaHaise [EMAIL PROTECTED]
3. Userspace partition code proposal
Given the above two bits, here's a brief explaination of a
proposal to move management of the partitioning scheme into
userspace, along with portions of raid startup, lvm, uuid and
Andrew Morton writes:
(2) what about bootstrapping? how do you find the root device?
Do you do root=/dev/hda/offset=63,limit=1235823? Bit nasty.
Ben's patch makes initrd mandatory.
Can this be fixed? I've *never* had to futz with initrd.
Probably most systems
Andries, I wouldn't call it trivial.
I am a mathematician. Definition of trivial in this case:
No intelligence required, just patience and careful work.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
After man-pages-1.36 and kbd-1.06 today util-linux-2.11c.
-
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/
Alexander Viro writes:
Folks, before you get all excited about cramming side effects
into open(2), consider ...
I agree completely.
A lot of stuff relies on the fact that close(open(foo, O_RDONLY))
is a no-op. Breaking that assumption is a Bad Thing(tm).
Also here I would like to agree.
Linus writes:
0 is EOF _for_reads_. For writes it is not very well defined
Hmm.
So -EFBIG is certainly the preferable return value,
Yes. The Austin 6th draft writes
EFBIG:
An attempt was made to write a file that exceeds the implementation-defined
maximum file size or the
Alexander Viro writes:
patch below adds the missing half of kdev_t -
for block devices we already have a unique pointer
and that adds a similar animal for character devices.
Very good.
(Of course I did precisely the same, but am a bit slower in
submitting things during a stable series or
They are entirely different. Too different sets of operations.
Maybe you didnt understand what I meant.
both bdev and cdev take care of the correspondence
device number --- struct with operations.
The operations are different, but all bdev/cdev code is identical.
So the choice is between two
Martin Dalecki writes:
I fully agree with you.
Good.
Unfortunately I do not fully agree with you.
Most of the places where there kernel is passing kdev_t
would be entierly satisfied with only the knowlendge of
the minor number.
My kdev_t is a pointer to a structure with device data
and
From [EMAIL PROTECTED] Wed May 23 00:39:23 2001
On Tue, 22 May 2001 [EMAIL PROTECTED] wrote:
The operations are different, but all bdev/cdev code is identical.
So the choice is between two uglies:
(i) have some not entirely trivial amount of code twice in the
why not implement partitions as simply doing block remaps
Everybody agrees.
Andries
-
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
IMHO it would be nice to create wrappers for accessing the block arrays
Last year Linus didnt like that at all. Maybe this year.
Andries
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
dev_t rdev;
Reasonable.
Good. We all agree.
(But now you see what I meant in comments about mknod.)
kdev_t dev;
Useless. If you hope that block_device will help to solve rmmod races
Yes. Why am I mistaken?
Andries
-
To unsubscribe from this list: send the line unsubscribe
On Wed, 23 May 2001 [EMAIL PROTECTED] wrote:
why not implement partitions as simply doing block remaps
Everybody agrees.
No they don't.
We had this discussion already. We all agree.
Maybe you read in remap something other than a simple addition
but I don't. This
But I don't want an initrd.
Don't be afraid of words. You wouldnt notice - it would do its
job and disappear just like piggyback today.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Andries, initrd code is _sick_.
Oh, but the fact that there exists a bad implementation
does not mean the idea is wrong. It is really easy to
make an elegant implementation.
Andries
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
Besides, just on general principles, we'd better have clean interface
for changing partitioning
It is not quite clear to me what you are arguing for or against.
But never mind - I'll leave few hours from now.
When the time is there I'll show you an implementation,
and if you don't like it,
From [EMAIL PROTECTED] Sat May 19 20:07:23 2001
initrd is an unnecessary pain in the ass for most people.
It had better not become mandatory.
You would not notice the difference, only your kernel would be
a bit smaller and the RRPART ioctl disappears.
Would I
What is the communication between user space and kernel
that transports device identities?
It doesn't change, the same symbolic names still work.
But today, unless you think of devfs or so, device identities
are not transported by symbolic names. They are given by
device numbers.
[Yes,
Opening device files often has interesting side effects.
Too bad. They can be triggered by similar races between attacker
changing the type of object (file-symlink) and backup.
Yes. This is a well-known security problem.
Doing
stat(file, s);
if (action desired) {
Alan writes:
The current partitioning code consists of re-reading from disk. That is
code that has to be present anyway even without an initrd since it is
needed for mounting other filesystems
I am not quite sure what you are saying here.
(For example, the even was unexpected.)
It
initrd is an unnecessary pain in the ass for most people.
It had better not become mandatory.
You would not notice the difference, only your kernel would be
a bit smaller and the RRPART ioctl disappears.
[Besides: we have lived with DOS-type partition tables for ten years,
but they will not
How about:
# mkpart /dev/sda /dev/mypartition -o size=1024k,type=swap
# ls /dev/mypartition
basesizedevicetype
Generally, we shouldn't care which order the kernel enumerates
devices in or which device number gets assigned internally. If we
did
From [EMAIL PROTECTED] Wed May 23 14:16:46 2001
It is entirely possible to remove all partition table handling code
from the kernel. User space can figure out where the partitions
are supposed to be and tell the kernel.
For the initial boot this user space can be in an
On Tue, 29 May 2001, John Chris Wren wrote:
In BSD, select() states that when a time out occurs,
the bits passed to select will not be altered.
In Linux, which claims BSD compliancy for this
in the man page (but does not state either way
what
So how does this say the value of the fdsets are undefined
after a timeout?
You are right, it doesn't say so. I should have said
That is, a wise programmer does not assume any particular value
for the bits after an error.
Andries
-
To unsubscribe from this list: send the line unsubscribe
Compiling 2.4.5 with CONFIG_USB=y and CONFIG_PCI not set
fails with drivers/usb/usbdrv.o: undefined reference to `pci_pool_*'.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
My RTL8139 (Identified 8139 chip type 'RTL-8139A')
was fine in 2.4.3 and doesnt work in 2.4.5.
Copying the 2.4.3 version of 8139too.c makes things work again.
Since lots of people complained about this, I have not tried to
debug - maybe a fixed version already exists?
One remark:
2.4.5 says
This evening I needed to work on a filesystem of a non-Linux OS,
full of absolute symlinks. After mounting the fs on /mnt, each
symlink pointing to /foo/bar in that filesystem should be
regarded as pointing to /mnt/foo/bar.
Since doing ls -ld on every component of every pathname was
far too
From [EMAIL PROTECTED] Sun Jun 3 02:49:08 2001
On Sun, 3 Jun 2001 [EMAIL PROTECTED] wrote:
This evening I needed to work on a filesystem of a non-Linux OS,
full of absolute symlinks. After mounting the fs on /mnt, each
symlink pointing to /foo/bar in that filesystem
/* No capabilities? What if users do thousands of these? */
look at mount_is_safe()
Yes, good. My remark means that more tests are required
than those sketched in mount_is_safe(), and that means
that for the time being we can throw out the routine
mount_is_safe(), and remove the test on
We can kludge around anything. The question being, what for?
It still leaves ncp with its ioctls ugliness.
I show how to simplify the kernel source without changing the
interface. That is good, and there are some free benefits.
You want to design a new interface. Maybe that is good as well,
From [EMAIL PROTECTED] Sun Jun 3 13:25:31 2001
[One could start a subdiscussion about that part.
The mount(2) system call needs to transport vfs information
and per-fs information. So far, the vfs information used
flag bits only, but sooner or later we'll want to have
Current interface had grown an impressive collection of warts.
Worse yet, you _can't_ put parsing into generic code.
There are filesystems that have a binary object as 'data'.
Yes, that was a very unfortunate decision, back in the good old times
when nfs was implemented. And smb, ncp, coda
On Tue, Sep 05, 2000 at 09:55:48AM -0400, James Lewis Nance wrote:
I have a box with 2 ethernet cards. One is a ne2k-pci and one is a
tulip. Under 2.2.X the ne card is eth0 and the tulip is eth1. Unfortunatly
if I boot a 2.4.X kernel, the tulip card is assigned eth0 and the ne card
On Thu, Sep 07, 2000 at 12:42:42AM +0200, Luca Montecchiani wrote:
few ours ago I discover that my kernel 2.4.0-test8pre5 was unable to
correctly identify the geometry of my second ide HD (*),
Always remember: a disk does not have a geometry.
this is very bad
Why precisely?
and fdisk
On Thu, Sep 07, 2000 at 07:45:48AM +0200, Luca Montecchiani wrote:
I think I prefer the current version over your patched version.
But will probably change my mind when many people complain.
Why have *fdisk or lilo trouble ?
I don't know whether lilo has trouble. But if it has
that is
On Fri, Sep 08, 2000 at 10:19:17AM +0200, Andreas Eibach wrote
about his problems with a large disk:
Motherboard GA-586 SG w/AWARD BIOS 4.51PG
(no updates available anymore from the manufacturer! 586sg
BIOS rev. is 1.15)
Maxtor 60 GB hard drive:
- Capacity Limitation Jumper J46 APPLIED
Linus, Andre, all:
Below a tiny patch to ide.c in the handling of the
HDIO_DRIVE_TASK ioctl. It makes sure that the
command goes to the right device.
(The current version obliges user space to keep track
of master/slave, which is inconvenient. Given this
patch I can release some disk utilities
On Fri, Sep 08, 2000 at 03:41:27AM +0100, Anton Altaparmakov wrote:
[kernel-2.4.0-test3 to kernel-2.4.0-test8-pre6, bug present in those two,
didn't try others]
I have been trying to get the linear md driver to work with NTFS volumes
for several months and it never worked. - I was
Dear Linus, Al, all:
Below a patch to prevent mounting the same filesystem
repeatedly on the same mount point. This 4-line patch is
+ /* Refuse the same filesystem on the same mount point */
+ retval = -EBUSY;
+ if (nd.mnt nd.mnt-mnt_sb == sb
+
On Mon, Sep 11, 2000 at 02:52:45AM +0200, Magnus Naeslund wrote:
*The hdb info:
Sep 10 11:52:43 genbaby kernel: hdb: QUANTUM FIREBALL SE8.4A, ATA DISK drive
Sep 10 11:52:43 genbaby kernel: hdb: QUANTUM FIREBALL SE8.4A, 8063MB w/80kB
Cache, CHS=1027/255/63, UDMA(33)
Sep 10 11:52:43 genbaby
On Tue, Sep 12, 2000 at 03:34:22PM +, Steven Walter wrote:
If you're logging in as root, this is probably a result of the VT not
being named in /etc/securetty. Devfsd mucks up the names, so you can
either include "1," which would allow root logins from pseudo-terminals
and other
On Wed, Sep 13, 2000 at 01:56:39AM -0400, [EMAIL PROTECTED] wrote:
8. Fix Exists But Isnt Merged
...
9. To Do
* Mount of new fs over existing mointpoint should return an error
unless forced (Andrew McNabb, Alan Cox)
Probably this belongs under 8. I posted a patch a few days
On Wed, Sep 13, 2000 at 10:50:09AM -0400, Douglas Gilbert wrote:
Since upgrading from 2.4.0-test7 to test8 (4 days ago)
I have had nothing but trouble on my AMD k6-2 500MHz
UP machine:
3 spontaneous reboots during boot
1 boot just started spraying lines full of numbers
2 badly
On Sat, Sep 16, 2000 at 11:35:24AM +0100, Nick Holloway wrote:
I have a zip disk which I attempted to mount using the following fstab
entry:
/dev/sda4 /zip vfat noauto,nodev,nosuid,user
This caused a spew of "bread failed" errors, and the mount process ended
up blocked in
On Sun, Sep 17, 2000 at 11:13:22AM -0500, Adam wrote:
FWIW, I downloaded install 'floppyC28.fs' from openbsd web site.
OK. So did I.
% md5sum floppyC28.fs
2ae3c61008df5accdfb132f20e744bfb floppyC28.fs
% file floppyC28.fs
floppyC28.fs: x86 boot sector, system OpenBSD, BSD disklabel
In order
On Sun, Sep 17, 2000 at 02:53:03PM -0400, [EMAIL PROTECTED] wrote:
still problems...
[root@pepsi /]# ls /mnt
[root@pepsi /]# dmesg | tail -3
UFS-fs error (device 02:00): ufs_readdir: bad entry in directory #2, size
512: reclen is too small for namlen - offset=0, inode=2, reclen=12,
On Mon, Sep 18, 2000 at 04:50:55AM -0700, Andre Hedrick wrote:
[ext2 errors and fdisk complaints on 2.4.0test8, patched?]
Andre,
(i) Geometry does not play any role in the functioning of Linux -
it is only a matter to LILO and fdisk. So, if you meet
a strange geometry, then that is surprising,
On Mon, Sep 18, 2000 at 03:41:11PM -0700, John Byrne wrote:
1.) Any decision on what the bigger dev_t will be? 16-bit major and
16-bit minor, for example?
My old code does something like this:
major = (dev 32);
minor = (dev 0x);
if (!major) {
On Thu, Sep 21, 2000 at 11:43:07AM +0200, Abramo Bagnara wrote:
In ALSA we use the return value from ioctl as a simple way to return a
positive number to user space (if the return value is less than 0 we got
error, of course)
We got the doubt that this break some unknown standards or some
Not only Sun does, Linux does too (e.g. in various networking ioctls).
I would just fix the man page.
Ach - more ugliness in Linux.
New man page fragment:
...
RETURN VALUE
Usually, on success zero is returned. A few ioctls use
the return value as an output parameter and
On Fri, Sep 22, 2000 at 02:34:16PM +0200, Igmar Palsenberg wrote:
It could be that it is choking on the fact that one drives is LBA, one
drive isn't. Drives are identical, but dmesg gives different CHS for each
of them..
A FAQ. See
On Fri, Sep 22, 2000 at 04:59:11PM +0200, Pavel Machek wrote:
test8 exhibits rather strange behaviour:
root@bug:~# ls -al /tmp/swap
-rw-r--r-- 1 root root 27164672 Sep 22 16:58 /tmp/swap
root@bug:~# mkswap /tmp/swap
Setting up swapspace, size = 27160576 bytes
root@bug:~# swapon
On Fri, Sep 22, 2000 at 12:03:30PM -0700, Andre Hedrick wrote:
On Fri, 22 Sep 2000, Andries Brouwer wrote:
Here 1.4 MB is wasted on hdb because the BIOS has invented
this 1229/255/63 translation. The disk access methods on
hdb and hdc is the same.
Yes, and soon CHS will go away
On Mon, Sep 25, 2000 at 11:29:48AM -0700, H. Peter Anvin wrote:
I guess mount -t bind is officially gone. What is the new official
replacement? New system call?
mount --bind
(use mount from util-linux 2.10o)
Andries
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
On Thu, Sep 28, 2000 at 04:18:00PM +0100, Tigran Aivazian wrote:
Hi Andries,
I just noticed that this boot message looks very strange:
SCSI device sda: 1039329 512-byte hdwr sectors (532 MB)
sda: sda1 sda1
Yes, no doubt because of the fragment of a patch for fs/partitions/check.c:
@@
On Wed, Sep 27, 2000 at 02:32:17PM +0100, Bernhard Bender wrote:
looking at my process list after a week or so of uptime I discoverd that PIDs
seem to wrap around at 32767 (aka. 2^15 - 1).
Yes.
I find this "feature" annoying, since I like to view my process list sorted
by PID, which gives
On Fri, Sep 29, 2000 at 09:17:11AM +1200, Chris Wedgwood wrote:
[The patch is available. There are a few security advantages.
Also, it makes a fork a just measurable fraction of a percent
faster.]
How does it make it faster? The only thing I can see is it might
remove the
On Thu, Sep 28, 2000 at 03:41:41PM -0700, Jack Howarth wrote:
I find that the compile of gnome-utils fails as follows...
In file included from /usr/include/linux/string.h:21,
from /usr/include/linux/fs.h:23,
from badblocks.c:43:
Yes, a well-known
At 00:40 29/09/2000, [EMAIL PROTECTED] wrote:
I'm writing some code to grok the Intel EFI GUID Partition Table structures.
To to so, my partition reading code (in fs/partitions) needs to be able to
read one physical sector at a time, particularly the first and last sectors
on the disk. The
On Fri, Sep 29, 2000 at 11:44:54AM +0200, [EMAIL PROTECTED] wrote:
After modifying sys_open() by prepending a namei(filename),
all devices mounted while the modified sys_open is in place,
report an EBUSY when trying to umount them.
You forget dput(dentry).
-
To unsubscribe from this list:
On Fri, Sep 29, 2000 at 03:57:10PM -0400, Albert D. Cahalan wrote:
The code is old.
There is very little reason for it, and we could change today.
My machines regularly see 6- or 7-digit PIDs.
Oh, the horror!
Consider, do you like to type "kill 1234567890" more than
a simple "kill
On Fri, Sep 29, 2000 at 05:36:48PM -0500, [EMAIL PROTECTED] wrote:
But the question was about reading from disk, not about reading
from partition.
Actually, that's next. In EFI, all partitions have a starting LBA and
ending LBA on the disk. So, it would be easy to have an "odd sized"
On Fri, Sep 29, 2000 at 06:51:22PM -0400, Chris Wing wrote:
(ii) There is also a rather obscure place in SYSV IPC where a 16-bit pid_t
is used for the fields msg_lspid and msg_lrpid of the (obsolete)
struct msqid_ds and the fields shm_cpid and shm_lpid of the (obsolete)
struct shmid_ds.
On Fri, Sep 29, 2000 at 04:10:51PM -0700, H. Peter Anvin wrote:
I find that the compile of gnome-utils fails as follows...
In file included from /usr/include/linux/string.h:21,
from /usr/include/linux/fs.h:23,
from badblocks.c:43:
Yes, a
On Sat, Sep 30, 2000 at 08:35:28AM -0500, Jeff Epler wrote:
31- or 32-bit PIDs might be a convenience, but they don't furnish
security against wraparound attacks, they just make them take
a little longer to exploit.
Precisely. It takes a factor 6 longer.
Maybe you think security is a
On Sat, Sep 30, 2000 at 03:09:10PM +0100, Nix wrote:
Yesterday, I noticed that netstat had stopped working on my 2.2.17 box
The reason is fairly self-evident:
: loki:/# cat /proc/net/dev
...
: lo:%lu %lu %lu %lu %lu %lu %lu %lu %lu %lu %lu %lu %lu %lu %lu %lu
: eth0:%lu %lu %lu %lu
On Tue, 29 Feb 2000 11:10:20, Mikulas Patocka wrote:
: This code in breada
:
:if (blocks (read_ahead[MAJOR(dev)] index))
:blocks = read_ahead[MAJOR(dev)] index;
:
: will increase number of block that are read ahead. However the code
: doesn't check for end of device
On Sun, Oct 01, 2000 at 12:36:16PM -0400, tenthumbs wrote:
I have some fat16 partitions which I mount as msdos, intentionally not
vfat. With 2.2.18pre14, the listings are now in uppercase which is a big
change from previous kernels. A bug or a feature?
Well, looking at the patch you see
On Mon, Oct 02, 2000 at 02:33:20AM +0200, Daniel Phillips wrote:
On Mon, 02 Oct 2000, Andries Brouwer wrote:
[you sounded as if you noticed a discrepancy somewhere - so I expected:
foo.c uses this in line 123 but bar.c uses that in line 666.]
No, I'm just trying to understand the meaning
1 - 100 of 737 matches
Mail list logo
