Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: tlug: Preparing the isofs for burning CDs
- To: tlug@example.com
- Subject: Re: tlug: Preparing the isofs for burning CDs
- From: "Stephen J. Turnbull" <turnbull@example.com>
- Date: Fri, 19 Feb 1999 18:49:46 +0900 (JST)
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=us-ascii
- In-Reply-To: <199902190735.IAA12710@example.com>
- References: <199902190609.PAA07005@example.com><199902190735.IAA12710@example.com>
- Reply-To: tlug@example.com
- Sender: owner-tlug@example.com
Thanks, Mike and Dmytro. I don't get the impression you've tried this, though; I guess I'll just have to try it and see what happens. Watch this space for the experimental results ;-) >>>>> "Stephen" == Stephen J Turnbull <turnbull@example.com> writes: Stephen> It would be most convenient if I could just cd into the Stephen> various directories and cp stuff across to the ISO9660 Stephen> image. Is this possible? >>>>> "Dmytro" == Dmytro Kovalev <kovald@example.com> writes: Dmytro> You can create an empty isofs image file with a size big Dmytro> enough to hold all your data, then mount it as loop device Dmytro> and copy files as into usual isofs. I don't remember Dmytro> though how do you create such file (dd will work?) This doesn't quite sound right. Creating the file is no problem, (use dd; in fact I already have a raw partition available too) but there is no such thing as "usual isofs." mkisofs doesn't just make the file system, it also populates it. Even if the mounted file system is writable, I am concerned that mkisofs might do things like "close" the file system by declaring that it has 0 bytes (or whatever I might stuff in there in the first place using mkisofs), and therefore the CD-ROM that reads it wouldn't believe the additional data was there! >>>>> "mike" == mike fabian <mike.fabian@example.com> writes: >> From the CD-Writing-HOWTO: >> (I7(B Create an extended-2 filesystem on this file >> >> bash> /sbin/mke2fs empty_file >> empty_file is not a block special device. >> Proceed anyway? (y,n) y Ah, I forgot I had this resource. But it doesn't speak to my question; I want to add to an ISO 9660 file system, which it is not designed for. mkisofs doesn't act like other mk*fs's. Among other things, my mother's Windose box wouldn't be able to read a CD containing an ext2 file system full of pictures of her granddaughter, rather distressing don't you think? -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 __________________________________________________________________________ __________________________________________________________________________ What are those two straight lines for? "Free software rules." ------------------------------------------------------------------- Next Nomikai: March 19 (Fri), 19:30 Tengu TokyoEkiMae 03-3275-3691 Next Technical Meeting: April 10 (Sat), 12:30 place: Temple Univ. ------------------------------------------------------------------- more info: http://tlug.linux.or.jp Sponsor: PHT
- Follow-Ups:
- Re: tlug: Preparing the isofs for burning CDs
- From: Frank Bennett <bennett@example.com>
- References:
- Re: tlug: Preparing the isofs for burning CDs
- From: Dmytro Kovalev <kovald@example.com>
- Re: tlug: Preparing the isofs for burning CDs
- From: <mike.fabian@example.com>
Home | Main Index | Thread Index
- Prev by Date: tlug: KDE & Japanese
- Next by Date: tlug: Why there won't be no SATS [was: KDE & Japanese]
- Prev by thread: Re: tlug: Preparing the isofs for burning CDs
- Next by thread: Re: tlug: Preparing the isofs for burning CDs
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links