Richard Hector wrote, on 06/02/10 09:07:
On Sat, 2010-02-06 at 07:39 +1030, Arthur Marsh wrote:
Last question is, what guarantee is there that the device file will have
been generated (assuming that the USB drive is present) before the
@reboot cron event is run?
The standard mount script is
On Sat, 2010-02-06 at 07:39 +1030, Arthur Marsh wrote:
> Last question is, what guarantee is there that the device file will have
> been generated (assuming that the USB drive is present) before the
> @reboot cron event is run?
The standard mount script is run in runlevel S, which is entered be
Dave Thayer wrote, on 05/02/10 16:01:
On Wed, Feb 03, 2010 at 11:01:00PM +1030, Arthur Marsh wrote:
In my case I have:
UUID=4823-93A9 /mnt/usb8gigvfat
defaults,users,uid=65534,gid=65534,umask=000,shortname=win95
0 2
(all on one line)
If I change that trailing "2" to a zero, no fs
On Wed, Feb 03, 2010 at 11:01:00PM +1030, Arthur Marsh wrote:
>
> In my case I have:
>
> UUID=4823-93A9 /mnt/usb8gigvfat
> defaults,users,uid=65534,gid=65534,umask=000,shortname=win95
> 0 2
>
> (all on one line)
>
> If I change that trailing "2" to a zero, no fsck should be perform
On Thu, 4 Feb 2010 17:42:45 -0600
"Boyd Stephen Smith Jr." wrote:
...
> If the file system may or may not be there, the information about the file
> system is not *static* (unchanging). Because the answer is sometimes
> "/dev/some/thing/or/other" and sometimes the answer is NULL and errno is
On Thursday 04 February 2010 17:00:49 Celejar wrote:
> On Thu, 4 Feb 2010 10:31:10 -0600
> "Boyd Stephen Smith Jr." wrote:
> > In any case, /etc/fstab is for *static* file systems. It is *not* for
> > file systems that may or may not be there when the system is booting (or
> > otherwise in operat
On Thu, 4 Feb 2010 10:31:10 -0600
"Boyd Stephen Smith Jr." wrote:
...
> In any case, /etc/fstab is for *static* file systems. It is *not* for file
> systems that may or may not be there when the system is booting (or otherwise
> in operation).
Please substantiate this assertion with some doc
Boyd Stephen Smith Jr.:
> On Thursday 04 February 2010 10:53:06 Jochen Schulz wrote:
>> Boyd Stephen Smith Jr.:
>>> In any case, /etc/fstab is for *static* file systems. It is *not* for
>>> file systems that may or may not be there when the system is booting (or
>>> otherwise in operation).
>>
>>
On Thursday 04 February 2010 11:44:36 Pier Paolo wrote:
> Yeah! An udev rule seems a good approach to me: i want to rsync my
> backup on an external drive. I'm using rsnapshot/cron stuff, but i'll
> get soon annoyed about to control the log, see if backup is already made
> and all, as there is no w
Il giorno gio, 04/02/2010 alle 23.57 +1030, Arthur Marsh ha scritto:
> Pier Paolo wrote, on 04/02/10 04:07:
> > Il giorno mer, 03/02/2010 alle 16.35 +, Camaleón ha scritto:
> >> On Wed, 03 Feb 2010 23:04:26 +1030, Arthur Marsh wrote:
> >>
> >>> Camaleón wrote, on 03/02/10 21:52:
> You shou
On Thursday 04 February 2010 10:53:06 Jochen Schulz wrote:
> Boyd Stephen Smith Jr.:
> > In any case, /etc/fstab is for *static* file systems. It is *not* for
> > file systems that may or may not be there when the system is booting (or
> > otherwise in operation).
>
> NACK. Or don't you have an e
On Thu, 04 Feb 2010 10:31:10 -0600, Boyd Stephen Smith Jr. wrote:
> On Thursday 04 February 2010 09:04:08 Camaleón wrote:
>> Yes, but the mount point of the OP is not critical for his system, that
>> was what I wanted to say. And the kernel must be aware of that device
>> is trivial and can be sk
Boyd Stephen Smith Jr.:
>
> In any case, /etc/fstab is for *static* file systems. It is *not* for file
> systems that may or may not be there when the system is booting (or otherwise
> in operation).
NACK. Or don't you have an entry for your CD/DVD drive?
J.
--
If I had to live on a desert i
On Thursday 04 February 2010 09:04:08 Camaleón wrote:
> On Thu, 04 Feb 2010 08:50:58 -0600, Boyd Stephen Smith Jr. wrote:
> > In , Camaleón wrote:
> >>But I still find the point valid: if a mount point defined in "fstab" is
> >>not present at boot time, it should warn the user and log the error but
On Thu, 04 Feb 2010 08:50:58 -0600, Boyd Stephen Smith Jr. wrote:
> In , Camaleón wrote:
>>But I still find the point valid: if a mount point defined in "fstab" is
>>not present at boot time, it should warn the user and log the error but
>>the boot process should not be stopped at all because the
In , Camaleón wrote:
>On Fri, 05 Feb 2010 00:01:17 +1030, Arthur Marsh wrote:
>> The response I received to
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568200 suggest that the
>> responder thinks that running fsck on a non-existent device is the
>> proper behaviour /-:.
>
>I've also found s
On Fri, 05 Feb 2010 00:01:17 +1030, Arthur Marsh wrote:
> Camaleón wrote, on 04/02/10 03:05:
>>> I would also like the machine to boot fully if it is started without
>>> the USB flash drive present.
>>
>> That should not happen at all (if the disk is not present it should log
>> a warn, but the
In <5quq37-nql@ppp121-45-136-118.lns11.adl6.internode.on.net>, Arthur
Marsh wrote:
>Camaleón wrote, on 04/02/10 03:05:
>> On Wed, 03 Feb 2010 23:04:26 +1030, Arthur Marsh wrote:
>>> Camaleón wrote, on 03/02/10 21:52:
You should not list your devices in fstab if you want to make use of
>>>
Camaleón wrote, on 04/02/10 03:05:
On Wed, 03 Feb 2010 23:04:26 +1030, Arthur Marsh wrote:
Camaleón wrote, on 03/02/10 21:52:
You should not list your devices in fstab if you want to make use of
your DE hotplug capabilities.
As I just posted in another message in this thread, I'd like the
Pier Paolo wrote, on 04/02/10 04:07:
Il giorno mer, 03/02/2010 alle 16.35 +, Camaleón ha scritto:
On Wed, 03 Feb 2010 23:04:26 +1030, Arthur Marsh wrote:
Camaleón wrote, on 03/02/10 21:52:
You should not list your devices in fstab if you want to make use of
your DE hotplug capabilities.
Il giorno mer, 03/02/2010 alle 16.35 +, Camaleón ha scritto:
> On Wed, 03 Feb 2010 23:04:26 +1030, Arthur Marsh wrote:
>
> > Camaleón wrote, on 03/02/10 21:52:
>
> >> You should not list your devices in fstab if you want to make use of
> >> your DE hotplug capabilities.
> >>
> > As I just po
On Wed, 03 Feb 2010 23:04:26 +1030, Arthur Marsh wrote:
> Camaleón wrote, on 03/02/10 21:52:
>> You should not list your devices in fstab if you want to make use of
>> your DE hotplug capabilities.
>>
> As I just posted in another message in this thread, I'd like the USB
> flash drive to be auto
Camaleón wrote, on 03/02/10 21:52:
On Wed, 03 Feb 2010 00:30:47 -0500, Frank McCormick wrote:
Camaleón wrote:
Mmm... I think "LABEL" would take precedence over another mount option
<<(UUID, ID or PATH) so if you "tag" your media device with a LABEL, it
should be mounted when plugged under
Frank McCormick wrote, on 03/02/10 16:00:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The bottom line: There is no problem even if
flashdrives/cameras etc are in fstab but not present- you
simply get the error logged
Well, there is a definite problem in my case (Debian unstable on
i386).
On Wed, 03 Feb 2010 00:30:47 -0500, Frank McCormick wrote:
>> Camaleón wrote:
>
>
>>>Mmm... I think "LABEL" would take precedence over another mount option
> <<(UUID, ID or PATH) so if you "tag" your media device with a LABEL, it
>>>should be mounted when plugged under "/media/mylabel".
>
> W
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> > >
> > > The bottom line: There is no problem even if
> > > flashdrives/cameras etc are in fstab but not present- you
> > > simply get the error logged
> >
> > Well, there is a definite problem in my case (Debian unstable on
> > i386).
> >
> >
On Wed, 03 Feb 2010 09:42:40 +1030
Arthur Marsh wrote:
> Frank McCormick wrote, on 03/02/10 06:16:
> >
> > To the OP:
> >
> > The bottom line: There is no problem even if flashdrives/cameras etc
> > are in fstab but not present- you simply get the error logged
> >
> >
> > Cheers
> > - --
Frank McCormick wrote, on 03/02/10 10:01:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 03 Feb 2010 09:42:40 +1030
Arthur Marsh wrote:
The bottom line: There is no problem even if flashdrives/cameras
etc are in fstab but not present- you simply get the error logged
Well, there is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 03 Feb 2010 09:42:40 +1030
Arthur Marsh wrote:
> >
> > The bottom line: There is no problem even if flashdrives/cameras
> > etc are in fstab but not present- you simply get the error logged
>
> Well, there is a definite problem in my cas
Frank McCormick wrote, on 03/02/10 06:16:
To the OP:
The bottom line: There is no problem even if flashdrives/cameras etc
are in fstab but not present- you simply get the error logged
Cheers
- --
Frank
Well, there is a definite problem in my case (Debian unstable on i386).
Error code
Frank McCormick wrote, on 03/02/10 02:11:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 02 Feb 2010 15:00:41 + (UTC)
Camaleón wrote:
On Tue, 02 Feb 2010 22:25:12 +1030, Arthur Marsh wrote:
Hi, I found that initscripts seems to attempt to run fsck on
non-existent devices that app
On Tue, 02 Feb 2010 15:08:57 -0500, Frank McCormick wrote:
> On Tue, 02 Feb 2010 19:59:13 + (UTC) Camaleón wrote:
>> Question is, do you really need "those" devices (flash drives and MC/SD
>> memory cards) to be present in "fstab"? That is, do you need static
>> mount points for that kind of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 02 Feb 2010 19:59:13 + (UTC)
Camaleón wrote:
> On Tue, 02 Feb 2010 14:46:09 -0500, Frank McCormick wrote:
>
> > To the OP:
> >
> > The bottom line: There is no problem even if flashdrives/cameras
> > etc are in fstab but not present-
On Tue, 02 Feb 2010 14:46:09 -0500, Frank McCormick wrote:
> To the OP:
>
> The bottom line: There is no problem even if flashdrives/cameras etc are
> in fstab but not present- you simply get the error logged
Question is, do you really need "those" devices (flash drives and MC/SD
memory card
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 02 Feb 2010 18:45:25 + (UTC)
Camaleón wrote:
> On Tue, 02 Feb 2010 13:34:40 -0500, Frank McCormick wrote:
>
> > On Tue, 02 Feb 2010 18:10:29 + (UTC) Camaleón wrote:
>
> >> Uh? Didn't you say...? :-?
> >>
> >> ***
> >> I found that
On Tue, 02 Feb 2010 13:34:40 -0500, Frank McCormick wrote:
> On Tue, 02 Feb 2010 18:10:29 + (UTC) Camaleón wrote:
>> Uh? Didn't you say...? :-?
>>
>> ***
>> I found that initscripts seems to attempt to run fsck on non-existent
>> devices that appear in /etc/fstab, and different fsck programs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 02 Feb 2010 18:10:29 + (UTC)
Camaleón wrote:
> On Tue, 02 Feb 2010 12:31:56 -0500, Frank McCormick wrote:
>
> > On Tue, 02 Feb 2010 16:12:56 + (UTC) Camaleón wrote:
> >
> >> I.e., if your USB drive is listed there and you have somet
On Tue, 02 Feb 2010 12:31:56 -0500, Frank McCormick wrote:
> On Tue, 02 Feb 2010 16:12:56 + (UTC) Camaleón wrote:
>
>> I.e., if your USB drive is listed there and you have something like:
>>
>> # #
>> /dev/sdb1/data/backupext3
>> acl,user_xattr 1 2 ^
>>
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 02 Feb 2010 16:12:56 + (UTC)
Camaleón wrote:
> On Tue, 02 Feb 2010 10:41:46 -0500, Frank McCormick wrote:
>
> > On Tue, 02 Feb 2010 15:00:41 + (UTC) Camaleón wrote:
> >
> >> > What is the easiest way to set up Debian to automaticall
On Tue, 02 Feb 2010 10:41:46 -0500, Frank McCormick wrote:
> On Tue, 02 Feb 2010 15:00:41 + (UTC) Camaleón wrote:
>
>> > What is the easiest way to set up Debian to automatically mount
>> > specific devices if they are present, but not cause a boot failure
>> > when they are absent?
>>
>> "m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 02 Feb 2010 15:00:41 + (UTC)
Camaleón wrote:
> On Tue, 02 Feb 2010 22:25:12 +1030, Arthur Marsh wrote:
>
> > Hi, I found that initscripts seems to attempt to run fsck on
> > non-existent devices that appear in /etc/fstab, and different f
On Tue, 02 Feb 2010 22:25:12 +1030, Arthur Marsh wrote:
> Hi, I found that initscripts seems to attempt to run fsck on
> non-existent devices that appear in /etc/fstab, and different fsck
> programs for different filesystem types give different error codes.
>
> What is the easiest way to set up D
Hi, I found that initscripts seems to attempt to run fsck on
non-existent devices that appear in /etc/fstab, and different fsck
programs for different filesystem types give different error codes.
What is the easiest way to set up Debian to automatically mount specific
devices if they are prese
Here is one I can not explain: A user wanted to mount a vfat partition
(/dev/hda4) to /mnt/hda4. His fstab had this line in it:
/dev/hda4 /mnt/hda4 auto defualts,rw,users,owner,auto,uid=1000 0 0
(uid=username ID).
And yet, root:root owned all the files/dirs, that was to be expected, I
thi
Hi
When you get "Input/Output" error, there may be a hardware error :-(
Check your /var/log/messages.
You can check the partition layout using gpart.
http://www.stud.uni-hannover.de/user/76201/gpart/, or the deb.
Look at man e2fsck, especially -b, -B and -n.
HTH
Jan-Marek
--
To UNSUBSCRIBE,
James Hosken wrote:
Quoting Paul Morgan <[EMAIL PROTECTED]>:
On Sat, 29 Nov 2003 11:46:13 +, James Hosken wrote:
Quoting Carl Fink <[EMAIL PROTECTED]>:
On Wed, Nov 26, 2003 at 07:03:57PM +, James Hosken wrote:
mount -t ext2 /dev/hdb5 /mnt/old-disk/
and I get th
On Sat, 29 Nov 2003 11:46:13 +, James Hosken wrote:
> Quoting Carl Fink <[EMAIL PROTECTED]>:
>
>> On Wed, Nov 26, 2003 at 07:03:57PM +, James Hosken wrote:
>>
>> > mount -t ext2 /dev/hdb5 /mnt/old-disk/
>> >
>> > and I get the error
>> >
>> > mount: wrong fs type, bad option, bad super
Quoting Carl Fink <[EMAIL PROTECTED]>:
> On Wed, Nov 26, 2003 at 07:03:57PM +, James Hosken wrote:
>
> > mount -t ext2 /dev/hdb5 /mnt/old-disk/
> >
> > and I get the error
> >
> > mount: wrong fs type, bad option, bad superblock on /dev/hdb5,
> >or too many mounted file systems
> >
On Wed, Nov 26, 2003 at 07:03:57PM +, James Hosken wrote:
> mount -t ext2 /dev/hdb5 /mnt/old-disk/
>
> and I get the error
>
> mount: wrong fs type, bad option, bad superblock on /dev/hdb5,
>or too many mounted file systems
> I'm pritty sure that it is the right file systems, I was u
I'm trying to mount a old disk with my /home and some other files.
I run the command
mount -t ext2 /dev/hdb5 /mnt/old-disk/
and I get the error
mount: wrong fs type, bad option, bad superblock on /dev/hdb5,
or too many mounted file systems
I'm pritty sure that it is the right file systems
50 matches
Mail list logo
