On Wed, 09 May 2001, Marco Calistri wrote:
> On 09-May-2001 Richard Adams wrote:
> > On Tue, 08 May 2001, Marco Calistri wrote:
> >> Hello,I'am using new kernel 2.4.x and beside several other new features
> >> I'am still looking to understand the proper usage/configuration of
> >> /dev/shm.
> >>
> [...cut]
> >> none /dev/shm shm defaults 0 0
> >> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> > If you read /usr/src/linux-{2.4}/Documemtation/devices.txt you will see a
> > differance between your fstab entry and the example given.
> >
> > tmpfs /dev/shm tmpfs defaults 0 0
I possably should have said read
/usr/src/linux/-{2.4}/documentation/Configure.help
I can assure you my example above works, it is mounted and "df" shows it usage,
which is still "0" here as the machine in question is mostly idle, or i have
not set up the sysctl system properly to handle it all.
>
> Hi Richard,I red just /Documentation/Changes where the line is as above:
> --
> System V shared memory is now implemented via a virtual filesystem.
> You do not have to mount it to use it. SYSV shared memory limits are
> set via /proc/sys/kernel/shm{max,all,mni}. You should mount the
> filesystem under /dev/shm to be able to use POSIX shared
> memory. Adding the following line to /etc/fstab should take care of
> things:
>
> none /dev/shm shm defaults 0 0
>
> Remember to create the directory that you intend to mount shm on if
> necessary (The entry is automagically created if you use devfs). You
> can set limits for the number of blocks and inodes used by the
> filesystem with the mount options nr_blocks and nr_inodes.
> --
> I've checked but on my /linux/Documentation/device.txt I haven't
> no traces at all about /etc/fstab/ sintax examples.
> It is the archive extracted from 2.4.0.tar.gz kernel:
>
> LINUX ALLOCATED DEVICES
>
> Maintained by H. Peter Anvin <[EMAIL PROTECTED]>
>
> Last revised: December 29, 2000
>
> /dev/shm shmfs POSIX shared memory maintenance access
>
> --
> > That should automount it at bootime, to avoid a reboot do;
> > mount /dev/shm
> >
> > You use 'df' to see its usage not 'free'
>
> Ok!
> > Its the "driver" getting unloaded not the device getting mounted/unmounted.
> > You possably have a cronjob running which could be doing this.
> > Or you have both kmod and kerneld working on your system, read
> > /usr/src/linux-{2.4}/Documemtation/kmod.txt
>
> Yes I've cronjobs for autoload/unload modules:
Well thats your answer then on that one. If the device is not in use the
cronjob will unload the module via kmod, its normally as easy as that.
> None kerneld or kmod running (using "ps aux|grep k...")
Well you wont see "kmod" running as it's in the kernel.
> But with new 2.4.x we have another .conf to check(may be):
> # Sample /etc/devfsd.conf configuration file.
'man devfsd'
Should explain.
> Yes Richard:under 2.2.18 never seen such dmesg IRQ allocation problem.
> BTW:all is working as well also with 2.4.2,both CDROM and sound,
> I was just warned by the log message.
If it works why worry or break it.!
>
> So you are a "newbie" ? ;)
Yes, with about 10+ years of linux experiance at home and at my work. + many
grey hairs to prove it.
>
> Thank you Richard!
Your welcome.
>
> --Marco
--
Regards Richard
[EMAIL PROTECTED]
http://people.zeelandnet.nl/pa3gcu/
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
