Ignorance wrote:

> but if adding line to fstab:
>
> /dev/sda1 /dysk ext3 default 0 0
>
> as last line, it don't work. Line is ignoring, but why?
> There is nothing in logs.
>
> Greetz:
> I.
>

Is there a newline after that line in fstab? Are those spaces between
each field or tab's? I not sure if my information is helpful.

Reading the mount man page it says.

(i) The command
mount -a [-t type] [-O optlist]
(usually given in a bootscript) causes all file systems
mentioned in fstab (of the proper type and/or having or
not having the proper options) to be mounted as indicated,
except for those whose line contains the noauto keyword.
Adding the -F option will make mount fork, so that the
filesystems are mounted simultaneously.

(ii) When mounting a file system mentioned in fstab, it
suffices to give only the device, or only the mount point.

(iii) Normally, only the superuser can mount file systems.
However, when fstab contains the user option on a line,
then anybody can mount the corresponding system.


Richard

richard napisał(a):

> Ignorance wrote:
>
>> but if adding line to fstab:
>>
>> /dev/sda1 /dysk ext3 default 0 0
>>
>> as last line, it don't work. Line is ignoring, but why?
>> There is nothing in logs.
>>
>> Greetz:
>> I.
>>
>
> Is there a newline after that line in fstab? Are those spaces between
> each field or tab's? I not sure if my information is helpful.
>
> Reading the mount man page it says.
>
> (i) The command
> mount -a [-t type] [-O optlist]

> Richard

Yes it works. I think that problem is with order as the system starts.
I uncommented module in /etc/rc.d/rc.modules (aic7xxx), and I think that
first system is mounting discs and then load drivers. It is reason
why slack is ignoring not existing partition (at this moment).
Can it be?

I.

Ignorance <ignorance@interia.pl> writes:

> hello,
>
> Have a problem with fstab, if I'm mounting disk manually:
>
> mount /dev/sda1 /dysk
>
> all is ok.:
>
> but if adding line to fstab:
>
> /dev/sda1 /dysk ext3 default 0 0
>
> as last line, it don't work. Line is ignoring, but why?
> There is nothing in logs.

Because the device isn't being mounted.

Adding a line to /etc/fstab does not, of itself mount anything. fstab
simply provides file system information for commands which DO mount file
systems. Such as mount!

Is this device something you want mounted all the time (its a usb device,
isn't it?). In that case you need to put something like your command
line above into one of the scripts in /etc/rc.d Perhaps the best place
to experiment would be rc.local

The revised Good Book contains a useful overview of the system and the
scripts in rc.d

http://lizella.net/chapter4.html#SYSTEMOVERVIEW

All those scripts repay reading, but you may feel that is OTT for the task
in hand :-)


On my machine at home that device gets used when I plug in my card
reader. So in fstab I have

/dev/sda1 /mnt/flash vfat noauto,user 0 0

and in the script I use to offload pictures I mount the thing with

mount /mnt/flash


hth


Glyn
--
RTFM http://www.tldp.org/index.html
GAFC http://slackbook.lizella.net/
STFW http://groups.google.com/groups?hl=e...inux.slackware
JFGI http://jfgi.us/

Ignorance <ignorance@interia.pl> wrote:
> Yes it works. I think that problem is with order as the system starts.
> I uncommented module in /etc/rc.d/rc.modules (aic7xxx), and I think that
> first system is mounting discs and then load drivers. It is reason
> why slack is ignoring not existing partition (at this moment).
> Can it be?

No. The problem is not with /etc/rc.d/rc.modules order. That is executed
in rc.S before the mount -a call is made. So if the proper drivers are in
rc.modules, they will be loaded before the drives are mounted. Now, the
problem may be with the driver itself. Check the logs for information on
that as well.

Ignorance <ignorance@interia.pl> wrote:
> No, so I'm asking, it should it be. (grep sda1 * in /var/log dir.)

Actually, this driver thought with your other above reply, I have to ask.
Does that reply mean there was no mention of sda or sda1 in your
/var/log/dmesg? When my SATA controller loads, I get a line about what
partitions sda has. Rather than just grepping the file, I strongly suggest
you read dmesg so you get a better understanding of the boot process.

If aic7xxx is not the proper driver module, then hotplug is most likely
loading the right (or at least a working) module, which is why you can
mount the drive manually. Hotplug runs in rc.M, so it comes too late for
the mount -a command in the boot process. Try doing an lsmod to determine
the modules hotplug has loaded for the drive and then uncomment that line
in rc.modules.