Kevin R. Bulgrien [EMAIL PROTECTED] writes:
Did anything final every come out of this thread.
Not from the coreutils side, no. My assumption is that it's
some sort of low-level system bug. But we haven't heard from
the low-level guys (whom you probably should be talking to).
The simple
ls
Did anything final every come out of this thread. I've written a
plug-in script for amaroK that a Suse user is complaining about.
I never heard of a system unmounting a disk automagically behind
the user's back when a mount was explicitly requested.
df is reporting USB media to be have 0 bytes
Paul Eggert wrote:
Juergen Weigert [EMAIL PROTECTED] writes:
Unless I'm missing something I'd rather not change the default behavor
of df, as that would be a compatibility hassle. That is, df shouldn't
attempt to mount file systems by default; it should do so only if the
user asks, with a
This sounds like an autofs problem. I'm running ubuntu and hal auto
mounts removable media when it is inserted. When it is not mounted, df
will not show a line for it at all, since df only shows mounted points.
I think what you are seeing is an autofs mount point being mounted
there which
Phillip Susi wrote:
This sounds like an autofs problem. I'm running ubuntu and hal auto
mounts removable media when it is inserted. When it is not mounted, df
will not show a line for it at all, since df only shows mounted points.
I think what you are seeing is an autofs mount point being
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Juergen Weigert on 9/20/2005 2:54 PM:
Wouldn't open() suffice? That would be simpler.
I chose opendir(), because I am not sure if all systems allow open() on a
directory node. Otherwise I'd also favour open(), it has no issue with
Sure.
Is it sufficient to abondon copyright,
Nope - FSF requires assignment of copyright, not abandonment.
This is not true. But one must do so in writting (i.e. signing a
copyright disclaimer, which more or less puts the changes/program into
the Public Domain).
Juergen Weigert [EMAIL PROTECTED] writes:
Unless I'm missing something I'd rather not change the default behavor
of df, as that would be a compatibility hassle. That is, df shouldn't
attempt to mount file systems by default; it should do so only if the
user asks, with a new option.
These
Juergen Weigert [EMAIL PROTECTED] writes:
On a recent SUSE Linux df became unreliable for e.g. USB-drives.
This is because hald automatically mounts and unmounts such drives
as they are accessed.
Usually I get something like:
$ df /media/USB_DISK
Filesystem 1K-blocks Used
On Sep 20, 05 13:12:46 -0700, Paul Eggert wrote:
Juergen Weigert [EMAIL PROTECTED] writes:
On a recent SUSE Linux df became unreliable for e.g. USB-drives.
This is because hald automatically mounts and unmounts such drives
as they are accessed.
Usually I get something like:
$ df
Hi coreutils people!
On a recent SUSE Linux df became unreliable for e.g. USB-drives.
This is because hald automatically mounts and unmounts such drives
as they are accessed.
Usually I get something like:
$ df /media/USB_DISK
Filesystem 1K-blocks Used Available Use% Mounted on
11 matches
Mail list logo
