Re: ISO9660 creator in Debian Jessie

2016-12-05 Thread Michael Lange
Hi, On Mon, 05 Dec 2016 09:16:23 +0100 "Thomas Schmitt" wrote: > Hi, > > terryc wrote: > > Unfortuantely, all that both machines have is Xfburn, which it gives > > you an option of creating an ISO, it only does so if the burner is in > > that machine. Major bummer. > (...) > Did you already tr

Re: ISO9660 creator in Debian Jessie

2016-12-05 Thread Jonathan Dowland
On Mon, Dec 05, 2016 at 09:46:55AM +, Brian wrote: > genisoimage -o out.iso file1 file2 . I'd echo this, use genisoimage, but read the man page first, you will almost certainly want to also use the -J and -r arguments too. -- Jonathan Dowland Please do not CC me, I am subscribed to the l

Re: ISO9660 creator in Debian Jessie

2016-12-05 Thread Brian
On Mon 05 Dec 2016 at 17:03:27 +1100, terryc wrote: > I need a prog to create an ISO image of files to transfer to a second > machine for burning, but I've suddenly found that my rich collection of > tools is noew depreciated and D'd in Debian Jessie. > > Unfortuantely, all that both machines hav

Re: ISO9660 creator in Debian Jessie

2016-12-05 Thread Thomas Schmitt
Hi, terryc wrote: > Unfortuantely, all that both machines have is Xfburn, which it gives > you an option of creating an ISO, it only does so if the burner is in > that machine. Major bummer. Sounds like an unfortunate design. I have on my todo list to test CDEmu ( http://cdemu.sourceforge.net/ )

Re: ISO9660 file naming (limits)

2004-01-06 Thread Carlos Sousa
On Tue, 6 Jan 2004 11:17:43 -0500 Derrick 'dman' Hudson wrote: > On Tue, Jan 06, 2004 at 12:41:23PM +, Carlos Sousa wrote: > ... The only anomaly it produces is a visible (and -apparently- empty) > 'rr_moved' directory. > | > |mkisofs -r -D -L -l -graft-points -J -joliet-long -jcharset d

Re: ISO9660 file naming (limits)

2004-01-06 Thread s. keeling
Incoming from Derrick 'dman' Hudson: > On Mon, Jan 05, 2004 at 09:32:21PM -0700, Paul E Condon wrote: > | > | Why don't you avoid problem by using tar on reasonably sized chunks of > | the file tree, and name the tar files concisely? > > I'd rather not have a cd full of tar files since I'm not cr

Re: ISO9660 file naming (limits)

2004-01-06 Thread Derrick 'dman' Hudson
On Tue, Jan 06, 2004 at 12:41:23PM +, Carlos Sousa wrote: | On Mon, 5 Jan 2004 23:12:16 -0500 Derrick 'dman' Hudson wrote: | > I want to make a cd archive of my (past) school work and remove it | > from my hard drive. The problem lies in name/path length limits for | > ISO9660 filesystems. 'm

Re: ISO9660 file naming (limits)

2004-01-06 Thread Derrick 'dman' Hudson
On Mon, Jan 05, 2004 at 09:32:21PM -0700, Paul E Condon wrote: | On Mon, Jan 05, 2004 at 11:12:16PM -0500, Derrick 'dman' Hudson wrote: | > I want to make a cd archive of my (past) school work and remove it | > from my hard drive. The problem lies in name/path length limits for | > ISO9660 filesys

Re: ISO9660 file naming (limits)

2004-01-06 Thread Carlos Sousa
On Mon, 5 Jan 2004 23:12:16 -0500 Derrick 'dman' Hudson wrote: > I want to make a cd archive of my (past) school work and remove it > from my hard drive. The problem lies in name/path length limits for > ISO9660 filesystems. 'mkisofs -R -J' yields output such as > Using FINDR000.HH;1 for > .

Re: ISO9660 file naming (limits)

2004-01-05 Thread Paul E Condon
On Mon, Jan 05, 2004 at 11:12:16PM -0500, Derrick 'dman' Hudson wrote: > I want to make a cd archive of my (past) school work and remove it > from my hard drive. The problem lies in name/path length limits for > ISO9660 filesystems. 'mkisofs -R -J' yields output such as > Using FINDR000.HH;1

Re: iso9660 module in kernel 2.0.34

1999-03-18 Thread G. Crimp
On Tue, Mar 16, 1999 at 07:12:34PM -0600, Paul Miller wrote: > "G. Crimp" wrote: > > > > Hi, > > > > Anybody know what an unresolved symbol is ? I've just compiled a > > This is a function call or variable that the modules wishes to use but > cannot find. > > > kernel making iso9660 su

Re: iso9660 module in kernel 2.0.34

1999-03-17 Thread Paul Miller
"G. Crimp" wrote: > > Hi, > > Anybody know what an unresolved symbol is ? I've just compiled a This is a function call or variable that the modules wishes to use but cannot find. > kernel making iso9660 support a module. I've done this in bo with no > problems. In hamm, however, when

Re: iso9660

1999-02-14 Thread wtopa
Subject: iso9660 Date: Sun, Feb 14, 1999 at 03:05:42PM +0800 In reply to:Bal K. Paudyal Quoting Bal K. Paudyal([EMAIL PROTECTED]): > > Hellou Friends, > > My recent Red Hat installation (don't know how to check the kernel version > yet!), says iso9660 file system not supported

Re: iso9660

1999-02-14 Thread ivan
Debian's a great distro - even comes with iso9660 support built into the installation kernel. You might want to try it :) Recompiling the kernel should work. Check out news://linux.redhat.misc if you need further assistance. At 03:05 PM 2/14/99 +0800, Bal K. Paudyal wrote: >Hellou Friends, > >

Re: iso9660

1999-02-14 Thread Tom Pfeifer
iso9660 support can be either compiled directly into the kernel, or it can be compiled as a module. When compiled directly into the kernel it is always available, while in the case of a module, the module must be loaded (inserted into the kernel) before it can be used. The command 'lsmod' will list

Re: iso9660 image?

1997-05-22 Thread Bruce Perens
I will upload 1.3 images created using the debian-cd package on June 2. I'll probably use Novare as their distribution site - 1.2 GB is a bit large to propogate to all of the mirrors. The response to early prototypes at Pixar has been "I love my Debian system". Bruce -- Bruce Perens K6BP