Jim Lesurf writes:
Richard Kettlewell wrote:
So do that. What's stopping you?

Because its still not clear to me what specific values I should put on the
fstab line. I found examples which looked different in ways that weren't
clear to me. Hence asking here for help on the issue.

Having used

sudo mkdir -p /mnt/ramdisc

what should I add to fstab to get the same as from my giving the command

sudo -t tmpfs -o size=128m tmpfs /mnt/ramdisc

after every bootup? And essentially gived a way to save/read/etc my
temporary files (usually) in ram for the duration of a session/

Did you try reading the man page I referred to?

--
http://www.greenend.org.uk/rjk/

In article
wwvy4kdnbu9.fsf@l1AntVDjLrnP7Td3DQJ8ynzIq3lJMueXf 87AxnpFoA.invalid,
Richard Kettlewell wrote:
Jim Lesurf writes:
Richard Kettlewell wrote:
So do that. What's stopping you?

Because its still not clear to me what specific values I should put on
the fstab line. I found examples which looked different in ways that
weren't clear to me. Hence asking here for help on the issue.

Having used

sudo mkdir -p /mnt/ramdisc

what should I add to fstab to get the same as from my giving the
command

sudo -t tmpfs -o size=128m tmpfs /mnt/ramdisc

after every bootup? And essentially gived a way to save/read/etc my
temporary files (usually) in ram for the duration of a session/

Did you try reading the man page I referred to?

Yes, along with various books and webpages on the topic. But none have
clarified this for me. And as I pointed out, examples I found showed
different and apparently conflicting texts for such an fstab line. Leaving
me little wiser as to the specific line I should use.

Alas, for those who *don't* already know all the answers 'man pages' may
be little more than a list of options or settings which don't tell the
reader *how* to use them appropriately for the situation you want. Fine
as reminders to those who already understand. But less use if you
don't.

That isn't a Linux problem. It crops up for all OS's and all kinds of
software where the author of the software wrote the 'documentation'. And
when doing so took for granted things the reader may not know.

Of all the 'example' versions I found the one that looked most likely to be
what I'd want from the above commands would be

tmpfs /mnt/ramdisc tmpfs nodev,nosuid,size=128m 0 0

as an added line to fstab having first used mkdir -p /mnt/ramdisc

But I've seen so many other examples said to be ways to do this for what
I'm after that the 'man page' doesn't resolve for me.

Hence why I keep explaining what I want to do, and asking for help.

Jim

--
Please use the address on the audiomisc page if you wish to email me.
Electronics http://www.st-and.ac.uk/~www_pa/Scot...o/electron.htm
Armstrong Audio http://www.audiomisc.co.uk/Armstrong/armstrong.html
Audio Misc http://www.audiomisc.co.uk/index.html

Jim Lesurf writes:
Richard Kettlewell wrote:
Jim Lesurf writes:
Richard Kettlewell wrote:
So do that. What's stopping you?

Because its still not clear to me what specific values I should put on
the fstab line. I found examples which looked different in ways that
weren't clear to me. Hence asking here for help on the issue.

Having used

sudo mkdir -p /mnt/ramdisc

what should I add to fstab to get the same as from my giving the
command

sudo -t tmpfs -o size=128m tmpfs /mnt/ramdisc

after every bootup? And essentially gived a way to save/read/etc my
temporary files (usually) in ram for the duration of a session/

Did you try reading the man page I referred to?

Yes, along with various books and webpages on the topic. But none have
clarified this for me. And as I pointed out, examples I found showed
different and apparently conflicting texts for such an fstab line. Leaving
me little wiser as to the specific line I should use.

Alas, for those who *don't* already know all the answers 'man pages' may
be little more than a list of options or settings which don't tell the
reader *how* to use them appropriately for the situation you want. Fine
as reminders to those who already understand. But less use if you
don't.

That isn't a Linux problem. It crops up for all OS's and all kinds of
software where the author of the software wrote the 'documentation'. And
when doing so took for granted things the reader may not know.

Of all the 'example' versions I found the one that looked most likely to be
what I'd want from the above commands would be

tmpfs /mnt/ramdisc tmpfs nodev,nosuid,size=128m 0 0

as an added line to fstab having first used mkdir -p /mnt/ramdisc

But I've seen so many other examples said to be ways to do this for what
I'm after that the 'man page' doesn't resolve for me.

OK. Some of the possible lines you quoted have a mode= parameter, but
your command doesn’t, and you say don’t know if those lines are suitable
for you. *I don’t know either* because I don’t know what behavior you
actually want. I can’t tell the difference between (1) you do want it,
but don’t know to add it to the mount command and (2) you don’t want it,
but don’t know to remove it from the fstab line.

That’s why I pointed you at the mount man page, because that’s where
that parameter is described. My guess would be that you don’t want it,
but I can’t read your mind.

--
http://www.greenend.org.uk/rjk/

In article
wwv8ucdm0fu.fsf@l1AntVDjLrnP7Td3DQJ8ynzIq3lJMueXf 87AxnpFoA.invalid,
Richard Kettlewell wrote:
Jim Lesurf writes:
[snip waste of effort]

OK. Some of the possible lines you quoted have a mode= parameter, but
your command doesn't, and you say don't know if those lines are suitable
for you. *I don't know either* because I don't know what behavior you
actually want. I can't tell the difference between (1) you do want it,
but don't know to add it to the mount command and (2) you don't want it,
but don't know to remove it from the fstab line.

I've repeatedly explained the behaviour I want, and my program examples the
kind of use intended. Sorry if that hasn't been clear enough. I'll ask
elsewhere.

Jim

--
Please use the address on the audiomisc page if you wish to email me.
Electronics http://www.st-and.ac.uk/~www_pa/Scot...o/electron.htm
Armstrong Audio http://www.audiomisc.co.uk/Armstrong/armstrong.html
Audio Misc http://www.audiomisc.co.uk/index.html

I have now put up a Linux version of CD_HealthCheck. This can be found
alongside Flac_HealthCheck via a link on

http://www.audiomisc.co.uk/software/index.html

As usual, source code is provided. Anyone interested can use/modify/etc
that as they like.

To save myself time and effort, this version piggybacks on cdparanoia. But
it works OK here. If anyone wants to do a better version, please do!

Similarly, I'd welcome someone porting these programs to Windows / Macs so
that others can carry out similar analysis on their CDs / flac files.

Jim

--
Please use the address on the audiomisc page if you wish to email me.
Electronics http://www.st-and.ac.uk/~www_pa/Scot...o/electron.htm
Armstrong Audio http://www.audiomisc.co.uk/Armstrong/armstrong.html
Audio Misc http://www.audiomisc.co.uk/index.html