All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amit D Chaudhary <amit@muppetlabs.com>
To: Werner Almesberger <Werner.Almesberger@epfl.ch>
Cc: lermen@fgan.de, linux-kernel@vger.kernel.org
Subject: Re: /linuxrc query
Date: Fri, 23 Mar 2001 09:46:05 -0800	[thread overview]
Message-ID: <3ABB8BDD.60409@muppetlabs.com> (raw)
In-Reply-To: <3ABAEED2.6020708@muppetlabs.com> <20010323075107.Q3932@almesberger.net> <3ABAF49B.9080109@muppetlabs.com> <20010323121824.R3932@almesberger.net>

Werner Almesberger wrote:

> Amit D Chaudhary wrote:
>> But other information in the 
>> initrd.txt mentions otherwise, hence the query here.
> 
> 
> Hmm, sounds like a bug. Where did you find this ?
I quote from the version in linux-2.4.2-ac22
"
Now, the initrd can be unmounted and the memory allocated by the RAM
disk can be freed:

# umount /initrd
# blockdev --flushbufs /dev/ram0    # /dev/rd/0 if using devfs
"

I guess I assumed the above has to be put in /linuxrc as it follows other 
commands which do go in the /linuxrc. The assumption is not quite correct as I 
have since found out.

Regards
Amit



  reply	other threads:[~2001-03-23 17:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-23  6:36 /linuxrc query Amit D Chaudhary
2001-03-23  6:51 ` Werner Almesberger
2001-03-23  7:00   ` Amit D Chaudhary
2001-03-23 11:18     ` Werner Almesberger
2001-03-23 17:46       ` Amit D Chaudhary [this message]
2001-03-23  7:07   ` Amit D Chaudhary
2001-03-23 11:24     ` Werner Almesberger
2001-03-23 14:07   ` David Woodhouse
2001-03-23 18:00     ` RAMFS, CRAMFS and JFFS2(was Re: /linuxrc query) Amit D Chaudhary
2001-03-23 19:37       ` David Woodhouse
2001-03-23 20:25         ` CRAMFS Bjorn Wesen
2001-03-23 22:01           ` CRAMFS Amit D Chaudhary
     [not found] <985356959.24859@whiskey.enposte.net>
2001-03-24  7:33 ` /linuxrc query Stuart Lynne

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=3ABB8BDD.60409@muppetlabs.com \
    --to=amit@muppetlabs.com \
    --cc=Werner.Almesberger@epfl.ch \
    --cc=lermen@fgan.de \
    --cc=linux-kernel@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.