LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: "Robert M. Stockmann" <stock@stokkie.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ramdisk driver in 2.6.6 has a severe bug
Date: Mon, 17 May 2004 19:18:37 -0400	[thread overview]
Message-ID: <200405172318.i4HNIb0V004180@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Tue, 18 May 2004 01:02:04 +0200." <Pine.LNX.4.44.0405180049040.20775-100000@hubble.stokkie.net>

[-- Attachment #1: Type: text/plain, Size: 806 bytes --]

On Tue, 18 May 2004 01:02:04 +0200, "Robert M. Stockmann" <stock@stokkie.net>  said:
> Hi,
> 
> I have severe problems creating a new root-disk using the ramdisk driver
> of kernel 2.6.6 :

> [tapebox:root]:(/mnt/floppy)# cp -ap bin boot cdrom dev etc floppy lib mnt proc root sbin tag tmp usr var /mnt/root

Were you expecting those to copy all the contents, or just the directories themselves?

Perhaps   tar cf - | (cd /mnt/root && tar xvf -)
or adding a -r flag to that cp?  

> So basicly i copied all my files from rootmdk92 to the new rootmdk100 ramdisk

No, I think you just copied the directories..

> But after copying them and umounting the old ramdisk (rootmdk92) en deleting
>  /dev/loop0 , /dev/loop1 (which is /tmp/rootmdk100) loses all its contents.

It never had the contents to lose.....

[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

  reply	other threads:[~2004-05-17 23:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-17 23:02 Robert M. Stockmann
2004-05-17 23:18 ` Valdis.Kletnieks [this message]
2004-05-17 23:19 ` Andrew Morton
2004-05-17 23:50   ` Robert M. Stockmann
2004-05-18  0:04     ` Andrew Morton
2004-05-18  0:13       ` Robert M. Stockmann
2004-05-18  0:50       ` viro
2004-05-18  1:03         ` Andrew Morton
2004-05-17 23:29 Valdis.Kletnieks

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=200405172318.i4HNIb0V004180@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stock@stokkie.net \
    --subject='Re: ramdisk driver in 2.6.6 has a severe bug' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).