Ohmster wrote:
> Cousin Stanley <cousinstanley********.com> wrote in news:1184051730_69381
> @sp6iad.superfeed.net:
>
>> Cousin Ohm ....
>>
>> Try giving mount a filesystem type ....
>>
>> sudo mount -t ramfs /dev/ram1 /mnt/ram
>>
>
> That did work Cousin Stanley,l or anyone, but how do you know the capacity
> of the new ramdrive? There seems to be no way of determining that. Not even
> df shows how much you can put in the new /mnt/ram/ mount.
>

zgrep CONFIG_BLK_DEV_RAM_SIZE /proc/config.gz

--

//Aho

"J.O. Aho" <user@example.net> wrote in
news:5fj2qbF3ctqc6U2@mid.individual.net:

>> That did work Cousin Stanley,l or anyone, but how do you know the
>> capacity of the new ramdrive? There seems to be no way of determining
>> that. Not even df shows how much you can put in the new /mnt/ram/
>> mount.
>>
>
> zgrep CONFIG_BLK_DEV_RAM_SIZE /proc/config.gz

What do you do with this Aho?

[ohmster@ohmster mnt]$ sudo mount -t ramfs /dev/ram1 /mnt/ram
[ohmster@ohmster mnt]$ mount
/dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/hda1 on /boot type ext3 (rw)
tmpfs on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
/dev/ram1 on /mnt/ram type ramfs (rw)
[ohmster@ohmster mnt]$ zgrep CONFIG_BLK_DEV_RAM_SIZE /proc/config.gz
gzip: /proc/config.gz: No such file or directory
[ohmster@ohmster mnt]$ sudo zgrep CONFIG_BLK_DEV_RAM_SIZE /proc/config.gz
gzip: /proc/config.gz: No such file or directory
[ohmster@ohmster mnt]$

--
~Ohmster
ohmster at ohmster dot com
Put "messageforohmster" in message body
(That is Message Body, not Subject!)
to pass my spam filter.

On Jul 9, 9:33 pm, "J.O. Aho" <u...@example.net> wrote:
> heavytull wrote:
> > On Jul 8, 4:42 pm, Linonut <lino...@bellsouth.net> wrote:
> >> After takin' a swig o' grog, Chris F.A. Johnson belched out this bit o' wisdom:
>
> >>>> I would like to know whether it is possible for wget when writing its output to
> >>>> files to decrease its hard disk accesses while downloading.
> >>> Let your operating system do its job. You are unlikely to come up
> >>> with anything more efficient.
> >> Especially with Linux.
>
> >> --
> >> Tux rox!
>
> > I'm wondering whether the linux stiff (the kernel and filesystems
> > ext2, 3 and reiserfs) is tuned to save hardware lifespan.
>
> > hints:
> > 1- just listen the noise difference that makes the hard drive while
> > writing or reading a lot of data under linux and then under windows
> > with the ntfs.
>
> Yeah, I agree, the windows box is noisy.
>
what do you mean??
> > 2- i've read that during years there was a cdrecording driver (the
> > default one for most distros) (for packet writing i think) that was
> > doing a bloody write test at the same address everytime a cdrw was
> > mounted under linux.
>
> Never seen anything like that and I really doubt that, as there is no reason
> to make a write test to a block device at mount time.
>
i'll try to find again the developper website.
> > 3- i doubt whether usb-storage driver doesn't make a write test if
> > mounted a usk key that is not write protected or that doesn't have
> > that feature.
>
> Why would it make a write test? A read test is more sensible.
>
shut up with your questions; i'm talking about the facts, just ask the
developpers if you want an answer!
> --
>
> //Aho

Ohmster wrote:
> "J.O. Aho" <user@example.net> wrote in
> news:5fj2qbF3ctqc6U2@mid.individual.net:
>
>>> That did work Cousin Stanley,l or anyone, but how do you know the
>>> capacity of the new ramdrive? There seems to be no way of determining
>>> that. Not even df shows how much you can put in the new /mnt/ram/
>>> mount.
>>>
>> zgrep CONFIG_BLK_DEV_RAM_SIZE /proc/config.gz
>
> What do you do with this Aho?

You get the info about this special kernel option (the size of /dev/ramX), of
course that requires that the distro has done the smart thing and allow users
to fetch the kernel configuration from the kernel.


> [ohmster@ohmster mnt]$ sudo zgrep CONFIG_BLK_DEV_RAM_SIZE /proc/config.gz
> gzip: /proc/config.gz: No such file or directory

Time to switch to a better distro? :)

CONFIG_BLK_DEV_RAM_SIZE=4096

with other words 4k

--

//Aho

"J.O. Aho" <user@example.net> wrote in
news:5fkl95F3cm1ppU1@mid.individual.net:

> Ohmster wrote:
>> "J.O. Aho" <user@example.net> wrote in
>> news:5fj2qbF3ctqc6U2@mid.individual.net:
>>
>>>> That did work Cousin Stanley,l or anyone, but how do you know the
>>>> capacity of the new ramdrive? There seems to be no way of
>>>> determining that. Not even df shows how much you can put in the new
>>>> /mnt/ram/ mount.
>>>>
>>> zgrep CONFIG_BLK_DEV_RAM_SIZE /proc/config.gz
>>
>> What do you do with this Aho?
>
> You get the info about this special kernel option (the size of
> /dev/ramX), of course that requires that the distro has done the smart
> thing and allow users to fetch the kernel configuration from the
> kernel.

Ahhh, information is good. My Fedora Core 6 distro did not give me the
/proc/config.gz gzip that you had mentioned. I would rather not switch
distros, I have mine setup to act as servers for 3 FQDNs and there is a
lot of customization that went into this. There may be some option to
install or specify in order to get this kernel option of "the size of
/dev/ramX" that you mention. Linux is pretty much Linux and Fedora really
is no slacker. What might I need to enable this disk size information
feature, Aho or anyone else?

I may upgrade to Fedora 7 when it matures enough. I really like the Beryl
desktop in gnome and spent a bit of time customizing it the way I want.
It is actually useful such as being able to zoom in anywhere on anything,
rather than just eye candy. Good stuff, wonder if Aero Glass will even
come close to this?

>> [ohmster@ohmster mnt]$ sudo zgrep CONFIG_BLK_DEV_RAM_SIZE
>> /proc/config.gz gzip: /proc/config.gz: No such file or directory
>
> Time to switch to a better distro? :)
>
> CONFIG_BLK_DEV_RAM_SIZE=4096
>
> with other words 4k
>

Thanks for your help Aho, you are a good man Charlie Brown. ;>)

--
~Ohmster
ohmster /a/t/ ohmster dot com
Put "messageforohmster" in message body
(That is Message Body, not Subject!)
to pass my spam filter.

Ohmster wrote:
> "J.O. Aho" <user@example.net> wrote in
> news:5fkl95F3cm1ppU1@mid.individual.net:
>
>> Ohmster wrote:
>>> "J.O. Aho" <user@example.net> wrote in
>>> news:5fj2qbF3ctqc6U2@mid.individual.net:
>>>
>>>>> That did work Cousin Stanley,l or anyone, but how do you know the
>>>>> capacity of the new ramdrive? There seems to be no way of
>>>>> determining that. Not even df shows how much you can put in the new
>>>>> /mnt/ram/ mount.
>>>>>
>>>> zgrep CONFIG_BLK_DEV_RAM_SIZE /proc/config.gz
>>> What do you do with this Aho?
>> You get the info about this special kernel option (the size of
>> /dev/ramX), of course that requires that the distro has done the smart
>> thing and allow users to fetch the kernel configuration from the
>> kernel.
>
> Ahhh, information is good. My Fedora Core 6 distro did not give me the
> /proc/config.gz gzip that you had mentioned. I would rather not switch
> distros,

Red Hat has the config file in the kernel-<version>.src.rpm and they think
that is enough. Select the right one, as they provide for quite many different
CPUs.


> What might I need to enable this disk size information
> feature, Aho or anyone else?

Not sure what you mean, but if you are talking about making larger /dev/ramX,
then you need to recompile the kernel with a larger size set in there.

--

//Aho

"J.O. Aho" <user@example.net> wrote in
news:5fs3leF3egqh7U1@mid.individual.net:

[...]
>> Ahhh, information is good. My Fedora Core 6 distro did not give me
>> the /proc/config.gz gzip that you had mentioned. I would rather not
>> switch distros,
>
> Red Hat has the config file in the kernel-<version>.src.rpm and they
> think that is enough. Select the right one, as they provide for quite
> many different CPUs.

Ohhh, I do not think I have the kernel source rpm installed, let's check on
that.

[ohmster@ohmster ~]$ rpm -qa |grep kernel
kernel-2.6.20-1.2933.fc6
kernel-devel-2.6.20-1.2933.fc6
kernel-2.6.20-1.2944.fc6
kernel-devel-2.6.20-1.2944.fc6
kernel-headers-2.6.20-1.2944.fc6
[ohmster@ohmster ~]$ uname -srv
Linux 2.6.20-1.2944.fc6 #1 SMP Tue Apr 10 18:46:45 EDT 2007
[ohmster@ohmster ~]$

Well, I got the headers but not the source.

>> What might I need to enable this disk size information
>> feature, Aho or anyone else?
>
> Not sure what you mean, but if you are talking about making larger
> /dev/ramX, then you need to recompile the kernel with a larger size
> set in there.

I just want to see how big this ram drive is, how much data can I put in it
before it gets full.

--
~Ohmster
ohmster /a/t/ ohmster dot com
Put "messageforohmster" in message body
(That is Message Body, not Subject!)
to pass my spam filter.

> ....
> I just want to see how big this ram drive is,
> how much data can I put in it before it gets full.

Cousin Ohm ....

I wrote a small Python program to write 4096 byte chunks
to the ram disk and quit looking after success at 64 MB ....

The program should indicate failure if you run out of space
but I didn't .... :-)

Following results on my 350 MHz dinosaur Compaq box
with only 224 MB of memory under Debian Etch ....

# ----------------------------------------------------------------

$ sudo python ram_zeros.py 16384 /mnt/ram

# 4096 byte records written .... 16384

Process time ................... 3.2347 seconds

/mnt/ram ....

total 64M
-rw-r--r-- 1 root root 64M 2007-07-15 08:43 zeros.txt
# ----------------------------------------------------------------

Usage ............ sudo python ram_zeros.py n_rec path

n_rec .......... number of 4096 byte records to write

path ........... path to your ram disk

# ----------------------------------------------------------------

Download ....

http://fastq.com/~sckitching/Python/ram_zeros.py
[ 879 bytes ]


--
Stanley C. Kitching
Human Being
Phoenix, Arizona


----== Posted via Newsfeeds.Com - Unlimited-Unrestricted-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----

J.O. Aho wrote:
> Ohmster wrote:
>> "J.O. Aho" <user@example.net> wrote in
>> news:5fj2qbF3ctqc6U2@mid.individual.net:
>>
>>>> That did work Cousin Stanley,l or anyone, but how do you know the
>>>> capacity of the new ramdrive? There seems to be no way of determining
>>>> that. Not even df shows how much you can put in the new /mnt/ram/
>>>> mount.
>>>>
>>> zgrep CONFIG_BLK_DEV_RAM_SIZE /proc/config.gz
>> What do you do with this Aho?
>
> You get the info about this special kernel option (the size of /dev/ramX), of
> course that requires that the distro has done the smart thing and allow users
> to fetch the kernel configuration from the kernel.
>
>
>> [ohmster@ohmster mnt]$ sudo zgrep CONFIG_BLK_DEV_RAM_SIZE /proc/config.gz
>> gzip: /proc/config.gz: No such file or directory
>
> Time to switch to a better distro? :)
>
> CONFIG_BLK_DEV_RAM_SIZE=4096
>
> with other words 4k
>
isn't it 4 MEG?

anyway i think you can also store it on an arbitrarely large tmpfs fs
and tweak vm.swappiness so VM prefers to use ram
vm.swappiness=0