Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<002201c22892$b3848d20$7978a8c0@nonnon>
From:	"liangalei" <liangalei AT mail DOT cs DOT sjtu DOT edu DOT cn>
To:	<cygwin AT cygwin DOT com>
Subject:	Fw: ramdisk--------How to build a ramdisk file in Cygwin?
Date:	Thu, 11 Jul 2002 12:23:26 +0800
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4910.0300
X-MIME-Autoconverted:	from base64 to 8bit by delorie.com id g6B4J9G30739

----- Original Message ----- 
From: "liangalei" <liangalei AT mail DOT cs DOT sjtu DOT edu DOT cn>
To: "Jason Morgan" <jason DOT morgan AT citel DOT com>
Sent: Thursday, July 11, 2002 12:22 PM
Subject: ramdisk--------How to build a ramdisk file in Cygwin?


> Hi,
> 
> thanks you for help from last email (which is about kernel cross-compile for arm core), and now I meet a new problem when I want to build a "ramdisk".
> 
> Following gives two messages of "mkramdisk script" and "error report", like the command "mount" given by Cygwin is very different from "mount" in Linux, like "mount -t ext2" is an invalid command.
> 
> How to build a ramdisk file in Cygwin?
> 
> the script "mkramdisk" I got is as following
> =====================================================
> echo "YOU MUST BE ROOT TO DO THIS"
> 
> rm -f ramdisk.be.*
> 
> # Make a file of 
> dd if=/dev/zero of=ramdisk.be bs=1k count=16384
> 
> # Make a file system on it. 
> /sbin/mke2fs -vm0 -F ramdisk.be 16384
> 
> # Mount it as a file systm
> mount -o loop -t ext2 ramdisk.be /mnt
> 
> # copy the big endian tree to this file system
> cd bigtree
> cp -R -p -d -f . /mnt
> cd ..
> 
> # umount the file system
> umount /mnt
> 
> # gzip it
> gzip -v9 ramdisk.be
> 
> # copy it to tftpboot
> cp ramdisk.be.gz      /tftpboot/ramdisk_img.gz
> 
> if [ ! -d ../../bin ]; then mkdir -p ../../bin; fi
> cp ramdisk.be.gz      ../../bin/ramdisk_img.gz
> 
> rm -f ramdisk.be.*
> =========================================================================
> 
> 
> And Error messages reported by Cygwin shell as follows
> ========================================================================
> tar: bigtree/dev/ttyx2: Cannot mknod: Function not implemented
> tar: bigtree/dev/ptyx3: Cannot mknod: Function not implemented
> tar: bigtree/dev/ttyx3: Cannot mknod: Function not implemented
> ................
> 
> tar: Error exit delayed from previous errors
> 
> done copying files
> tar cvfz bigtree.tar.gz bigtree >/dev/null
> YOU MUST BE ROOT TO DO THIS
> 16384+0 records in
> 16384+0 records out
> /sbin/mke2fs: not found
> usage mount [-bfstux] <win32path> <posixpath>
> -b  text files are equivalent to binary files (newline = \n)
> -f  force mount, don't warn about missing mount point directories
> -s  add mount point to system-wide registry location
> -t  text files get \r\n line endings (default)
> -u  add mount point to user registry location (default)
> -x  treat all files under mount point as executables
> 
> [-bs] --change-cygdrive-prefix <posixpath>
>     change the cygdrive path prefix to <posixpath>
> --show-cygdrive-prefixes
>     show user and/or system cygdrive path prefixes
> --import-old-mounts
>     copy old registry mount table mounts into the current mount areas
> umount: /mnt: No such file or directory
> ramdisk.be:              99.9% -- replaced with ramdisk.be.gz
> bash-2.04$
> 

- Raw text -