-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Simon Geard wrote:
> Stick a label on the filesystem, and mount it via /dev/disk/by-label/*?
> Or did I miss an earlier part of the conversation that rules that out?
>
> Simon.
>
That would work but is not really the problem. The problem is trying t
On Thu, 2009-03-19 at 09:19 +, Jack Stone wrote:
> Mike McCarty wrote:
> > Jack Stone wrote:
> >> Sorry I should have made that clear. Yes the device does have an entry
> >> in fstab. So far it is always given the same name (sde), but I don't
> >> know if I can rely on that.
> >
> > You
Mike McCarty wrote:
> Jack Stone wrote:
>> Sorry I should have made that clear. Yes the device does have an entry
>> in fstab. So far it is always given the same name (sde), but I don't
>> know if I can rely on that.
>
> You cannot. It depends on the order in which the USB gets
> enumerated,
Jack Stone wrote:
> Randy McMurchy wrote:
>> The 'mount -a' command will only mount those filesystems
>> identified in /etc/fstab. And typically you would not put
>> a USB device in /etc/fstab. Have you identified the USB
>> drive in that file? If so, how do you ensure that the drive
>> always has
Jack Stone wrote:
> Dan Nicholson wrote:
>
>> Out of curiosity, do you have usb-storage, libata or scsi built into
>> the kernel or as modules? It may help to get more things built into
>> the kernel.
>>
> I tried recompiling and compiled a few more modules into the kernel but
> that didn'
Dan Nicholson wrote:
> I'm think this is a timing issue with using USB disks since it
> requires the usb-storage and the whole libata stack to be loaded and
> then have all the disks and partitions enumerated before the devices
> are created. I think this is just slow on USB and why the event isn't
On Tue, Jan 6, 2009 at 4:08 AM, Jack Stone wrote:
> Hi all,
>
> I have a LFS 6.3 system which I am trying to attach a Maxtor Onetouch IV
> USB hard disk too. The system recognises the disk under the udev_retry
> script but only after the next init script finished running, i.e after
> udevsettle r
Randy McMurchy wrote:
> Just out of curiosity (as I'm not sure I can help you with
> this issue), could you show the entry in /etc/fstab that
> you currently have
/dev/sde1 /backup xfs
defaults,nobarrier,noatime 10
The nobarrier is an XFS option to disable write-barr
Jack Stone wrote:
> Sorry I should have made that clear. Yes the device does have an entry
> in fstab. So far it is always given the same name (sde), but I don't
> know if I can rely on that.
Just out of curiosity (as I'm not sure I can help you with
this issue), could you show the entry in /
On Tue, Jan 06, 2009 at 06:59:01AM -0600, Randy McMurchy wrote:
> Jack Stone wrote:
>
> > As the udev_retry script is after the mountfs script I tried adding an
> > extra_mount script after udev_retry which does a "mount -a".
>
> The 'mount -a' command will only mount those filesystems
> identif
Randy McMurchy wrote:
> The 'mount -a' command will only mount those filesystems
> identified in /etc/fstab. And typically you would not put
> a USB device in /etc/fstab. Have you identified the USB
> drive in that file? If so, how do you ensure that the drive
> always has the same device filename
Jack Stone wrote:
> As the udev_retry script is after the mountfs script I tried adding an
> extra_mount script after udev_retry which does a "mount -a".
The 'mount -a' command will only mount those filesystems
identified in /etc/fstab. And typically you would not put
a USB device in /etc/fstab.
Hi all,
I have a LFS 6.3 system which I am trying to attach a Maxtor Onetouch IV
USB hard disk too. The system recognises the disk under the udev_retry
script but only after the next init script finished running, i.e after
udevsettle returns. This seems to be regardless of what the next
init
13 matches
Mail list logo
