From: Ewerton Romulo <ewertonromulo@gmail.com>
To: Jan Hudec <bulb@ucw.cz>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: Run linux in ramdisk(tmpfs) and use a mounted HD for files cause memory and CPU overflow!
Date: Wed, 29 Jun 2005 01:41:13 -0300 [thread overview]
Message-ID: <1f52e8ed05062821415f505fee@mail.gmail.com> (raw)
In-Reply-To: <20050628202457.GC30378@vagabond>
OK!
/proc/modules
via-rhine 10328 1
8139too 11996 1
mii 1868 0 [via-rhine 8139too]
sch_ingress 1116 0 (unused)
sch_sfq 2816 321
sch_htb 16896 2
cls_u32 3960 108
cls_fw 2004 1
ip_nat_quake3 1544 0 (unused)
ip_nat_mms 2352 0 (unused)
ip_nat_h323 2020 0 (unused)
ip_nat_amanda 708 0 (unused)
ip_nat_irc 1648 0 (unused)
ip_nat_ftp 2096 0 (unused)
ip_conntrack_quake3 1592 1
ip_conntrack_mms 2480 1
ip_conntrack_h323 1832 1
ip_conntrack_egg 2024 0 (unused)
ip_conntrack_amanda 968 1
ip_conntrack_irc 2344 1
ip_conntrack_ftp 3120 1
softdog 1316 1
My /proc/mount is:
rootfs / rootfs rw 0 0
/dev/root / tmpfs rw 0 0
/proc /proc proc rw 0 0
devpts /dev/pts devpts rw 0 0
/dev/hda1 /test vfat rw 0 0
The tmpfs is my root that is descompression from a .tgz file in the
beginning of boot.
I use kernel 2.4.30 oficial, no especific linux distribution!
next prev parent reply other threads:[~2005-06-29 4:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-27 9:18 Run linux in ramdisk(tmpfs) and use a mounted HD for files cause memory and CPU overflow! Ewerton Romulo
2005-06-27 14:20 ` Jan Hudec
2005-06-28 18:06 ` Ewerton Romulo
2005-06-28 20:24 ` Jan Hudec
2005-06-29 4:41 ` Ewerton Romulo [this message]
2005-06-29 8:41 ` Jan Hudec
2005-06-29 16:28 ` Bryan Henderson
2005-06-29 18:36 ` Ewerton Romulo
2005-06-29 21:00 ` Bryan Henderson
2005-06-30 16:02 ` Jan Hudec
2005-06-29 18:46 ` Ewerton Romulo
2005-06-28 21:42 ` Bryan Henderson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1f52e8ed05062821415f505fee@mail.gmail.com \
--to=ewertonromulo@gmail.com \
--cc=bulb@ucw.cz \
--cc=linux-fsdevel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.