Hi,
Pascal Hambourg wrote:
> Tested with debian-12.6.0-amd64-netinst.iso on QEMU+OVMF and real hardware:
> (proc) (memdisk) (cd0) (cd0,apple2) (cd0,apple1) (cd0,msdos2)
I wonder from where (cd0,apple2) comes. A Debian amd64 netinst ISO has a
single APM partition which marks the EFI El Torito boot
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
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
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
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/ )
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 have is Xfburn, which it gives
you an option of creating an ISO, i
Hi,
Jonathan Dowland sent me the URL of a test image which demonstrates
the problem with reading ISO 9660 images not produced on Linux.
Indeed the problem appears when reading the Rock Ridge info of the
root directory. So xorriso-1.4.6 in Debian testing cannot avoid it.
The root directory recor
Hi,
Jonathan Dowland wrote:
> But digging into this a little, it seems to be an argument order issue.
Yes, sequence matters. The arguments are commands like in a shell script,
not options like with program "ls".
There is command -x which lets xorriso sort the arguments in a sequence
that is most
On Wed, Nov 23, 2016 at 03:40:22PM +, Jonathan Dowland wrote:
> But digging into this a little, it seems to be an argument order issue.
...and all of my ISOs now read fine without the RR warnings. I haven't
double-checked
the docs, if you state that the argument order of -read_fs / -indev is
On Fri, Nov 18, 2016 at 05:27:25PM +0100, Thomas Schmitt wrote:
> $ gdb xorriso/xorriso
> (gdb) b fs_image.c:3024
> (gdb) b rockridge_read.c:111
> (gdb) r -read_fs norock -indev /path/to/your.iso
Using the above and one of the UDF images that I am about to email you a URL to,
and the above
On Tue, Nov 22, 2016 at 09:46:16PM +0100, Thomas Schmitt wrote:
> If they demonstrate the Rock Ridge read error despite -read_fs "norock",
> then they might help to solve the riddle.
Yes the do. I'm just about to mail you privately with a URL to one.
signature.asc
Description: Digital signature
Hi,
i wrote about video DVDs:
> > That's probably UDF filesystems. Interesting anayways.
Jonathan Dowland wrote:
> Good catch: you are right, they are. Are they interesting enough for me to
> put them online somewhere?
If they demonstrate the Rock Ridge read error despite -read_fs "norock",
then
On Fri, Nov 18, 2016 at 05:27:25PM +0100, Thomas Schmitt wrote:
> If you got the GNU xorriso tarball, then it is not linked dynamically
> with installed libisofs.so but rather statically with its own copy of
> libisofs.
OK, yup that's what I did.
> In the build directory
>
> $ xorriso/xorriso
llegal space at offset
> 3
> iso-info reports a line like the following for each directory
>++ WARN: XA signature not found in ISO9660's system use area; ignoring
> XA attributes for this file entry.
That's obviously Joliet woes. (Not only Rock Ridge can be awkward.)
>
On Fri, Nov 18, 2016 at 03:29:54PM +, Jonathan Dowland wrote:
> I'm wondering if my hand-built modern xorriso is linking against my old
> system libisofs.
> I am doing some investigation.
I can't see any .so files in my xorriso build directory, but ldd does not show
this xorriso
binding agai
same output for all
the
failing ISOs.
isoinfo reports
isoinfo: Warning: Joliet escape sequence uses illegal space at offset 3
iso-info reports a line like the following for each directory
++ WARN: XA signature not found in ISO9660's system use area; ignoring
XA attrib
On Thu, Nov 10, 2016 at 07:39:22PM +0100, Thomas Schmitt wrote:
> > Interestingly 1.4.7 can read one more of these ISOs, leaving 19 bad.
>
> Was that already with -read_fs "norock" ?
No, I didn't try that yet; I'll try that when I next take a look (probably
Monday). Thanks for the suggestion!
>
Hi,
> Interestingly 1.4.7 can read one more of these ISOs, leaving 19 bad.
Was that already with -read_fs "norock" ?
If so: Do you still see the error message
"Damaged RR/SUSP information."
?
> With 1.3.2 and this ISO in particular, it said
>libisofs: SORRY : Mandatory Rock Ridge PX entr
On Thu, Nov 10, 2016 at 11:56:36AM +, Jonathan Dowland wrote:
> On Thu, Nov 10, 2016 at 11:35:02AM +, Jonathan Dowland wrote:
> > I'll try the following command with both my current xorriso version and
> > 1.4.6,
> > against all of my currently imported ISOs, and report back what my result
On Thu 10 Nov 2016 at 15:21:42 +0100, Thomas Schmitt wrote:
> Hi,
>
> two hours ago, i sent the mail below as reply to
> https://lists.debian.org/debian-user/2016/11/msg00355.html
> Subject line was:
> LDO_SUBSCRIBER, was Re: xorriso: listing files+offsets in an IS
On Thu, Nov 10, 2016 at 03:21:42PM +0100, Thomas Schmitt wrote:
> My mails (and those of most other regular posters) have it in their
> X-Spam-Status when they arrive in my mailbox something like:
...
> The word "LDOSUBSCRIBER" seems to be the indication for a sunscribed
> sender.
...
> My best the
Hi,
two hours ago, i sent the mail below as reply to
https://lists.debian.org/debian-user/2016/11/msg00355.html
Subject line was:
LDO_SUBSCRIBER, was Re: xorriso: listing files+offsets in an ISO9660 image
w/o RockRidge
Date: Thu, 10 Nov 2016 12:59:10 +0100
But it did not arrive in my
Hi,
i have now uploaded
http://www.gnu.org/software/xorriso/xorriso-1.4.7.tar.gz
for testing of improved xorriso command -read_fs "norock".
Have a nice day :)
Thomas
Hi,
Jonathan Dowland wrote:
> 4 Application:
> 1 Application:
> ...
> The first one is completely empty labels. The second is roughly 64
> whitespace characters.
Looks like an interesting collection.
It would be nice if libisofs could exercise with it.
I am in the process of te
On Thu, Nov 10, 2016 at 11:35:02AM +, Jonathan Dowland wrote:
> I'll try the following command with both my current xorriso version and 1.4.6,
> against all of my currently imported ISOs, and report back what my results
> are:
With 1.3.2, at least, only 20/45 of my ISOs fail; the Application l
On Wed, Nov 09, 2016 at 02:29:25PM +0100, Thomas Schmitt wrote:
> I would be interested to examine such an ISO, if privacy permits.
Thanks for the offer!
Once I've narrowed down which of my ISOs suffer this problem, I'll see
which are not too private, some are basically just "Downloads" folders
f
Hi Thomas, thanks for replying!
On Wed, Nov 09, 2016 at 02:02:48PM +0100, Thomas Schmitt wrote:
> your mail headers do not contain "LDO_SUBSCRIBER", so i Cc: you.
I've never heard of LDO_SUBSCRIBER, but I am subscribed - no need to CC
me. (I put something like that in my signature to make things
Partially answering my own question, "iso-info" from the libcdio-utils
package prints out the Logical Sector Number for files which is probably
what I need, at least it can be translated into the Logical Block Address,
I just need to figure out mapping the numbers from ddrescue's log files
into tha
Hi,
regrettably the ban on reading Rock Ridge gets not into effect before
the attempt to read the SUSP entries of the root directory record.
So if that chain is damaged, then one would have to hack the source code:
-
--- libi
Hi,
it looks like
-read_fs norock
with xorriso >= 1.4.2 gives hope to circumvent the error message.
It will go for the Joliet tree, if present, as would do "isoinfo -J".
If you want the dull ISO names in any case: -read_fs ecma119
-
Hi,
your mail headers do not contain "LDO_SUBSCRIBER", so i Cc: you.
Jonathan Dowland wrote:
> [xorriso] seems to always complain about missing RR records:
> [...]
> xorriso -indev disk.iso -rockridge off -error_behavior image_loading
best_effort -abort_on NEVER -find . -exec report_lba
> libisof
Hi,
I'm trying to map files within ISO9660 images to block offsets within the
image. This is to try and determine which files are impacted by damaged or
missing blocks in the images.
These are all images of home made CD-rs and DVD-Rs from over the last 17 or so
years. I am importing the
raises the error message of bad superblock (mount -t iso9660
> /dev/sr1 /mountpoint). These iso images can be read on other computers.
(...)
I would first try the most obvious: attach a different optical unit to
your system (either USB or internal. Yup, I know it's annoying but...)
a
)
and it is not possible to mount my old iso images. At the moment BOTH dvd
burners do not work (do not read iso images).A first try to mount the medium
fails
with a busy device error message, further attempts raises the error message
of bad superblock (mount -t iso9660 /dev/sr1 /mountpoint
On Fri, Feb 20, 2004 at 02:42:23AM +0200, Micha Feigin wrote:
> There are several tools to do this on M$, isn't there something for
> doing it on linux?
What there are tools for on Windows is recreating the ISO after you've
modified the data inside it. There are also tools on Linux to do this
job
On Thu, Feb 19, 2004 at 07:59:20AM +0100, Kristian Rink wrote:
>
> Hi Micha,...
>
> On Thu, 19 Feb 2004 04:01:03 +0200
> Micha Feigin <[EMAIL PROTECTED]> wrote:
>
> > How do I change things inside an iso9660 file system (cdrom
>
> You don't. ISO9660
Hi Micha,...
On Thu, 19 Feb 2004 04:01:03 +0200
Micha Feigin <[EMAIL PROTECTED]> wrote:
> How do I change things inside an iso9660 file system (cdrom
You don't. ISO9660 per se is a read-only filesystem with no
abilities to write to it. If you want to modify / add files, you'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 18 February 2004 05:01 pm, Micha Feigin wrote:
> How do I change things inside an iso9660 file system (cdrom image)?
> I tried to mount it rw but it seemed to ignore the rw option, that is
> mount -o loop,rw file.iso /mnt
> l
How do I change things inside an iso9660 file system (cdrom image)?
I tried to mount it rw but it seemed to ignore the rw option, that is
mount -o loop,rw file.iso /mnt
left it still in a read only state.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe"
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
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
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
| >
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
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
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
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 ./SE1-Software_Engineering.3010-361/src/FindRoo
On Tuesday 11 September 2001 21:19, richard wrote:
> A still new installation of potato from CDROM.
>
> Upon mount /dev/cdrom or mount -t iso9660 /dev/cdrom /cdrom I get the
> subject error message.
>
> The line
>/dev/cdrom /cdrom iso9660 defaults,ro,user,no auto
on Tue, Sep 11, 2001 at 09:19:41PM -0400, richard ([EMAIL PROTECTED]) wrote:
> A still new installation of potato from CDROM.
>
> Upon mount /dev/cdrom or mount -t iso9660 /dev/cdrom /cdrom I get the
> subject error message.
>
> The line
>/dev/cdrom /cdrom iso9660
A still new installation of potato from CDROM.
Upon mount /dev/cdrom or mount -t iso9660 /dev/cdrom /cdrom I get the
subject error message.
The line
/dev/cdrom /cdrom iso9660 defaults,ro,user,no auto
is already in /etc/fstab, put there by the installer.
What's wrong? Do I ha
on Sun, May 20, 2001 at 09:23:30PM -0400, Mel Herndon ([EMAIL PROTECTED]) wrote:
> Karsten,
>
> I tried insmod and it could not find the module. Is there a command line
> that I can use when I boot to the cd to force it to install(override)
> the selection option to make su
hen it runs the script to setup a connection, and then dselect to
> allow the packages to be installed. Here is what is happening though.
>
> I tried using the program...it refused to recognize /dev/cdrom...ok I
> back out...and try to mount the cdrom..error message
>
> mount:
2000, "Mathew Watson" wrote:
> Date: Fri, 25 Aug 2000 20:12:54 -0700
> To: "Debian List"
> From: "Mathew Watson" <[EMAIL PROTECTED]>
> Subject: Potato, iso9660 not supported by kernel
>
> Using new potato CDs, I've managed to install the b
Using new potato CDs, I've managed to install the base system. Upon
rebooting, as prompted to after making a boot floppy, the CD rom is
inaccessible. The error message is "fs type iso9660 not supported by
kernel." I repeated the base install and carefully searched for iso9660
suppor
, 3 Apr 1999, Johann Spies wrote:
> I am trying to install hamm and get this message from dselect or when I
> want to mount the cdrom. I did install a cdrom as a device and did not
> see iso9660 as an option amongst the filesystems during the installation
> process.
>
> Can someb
I am trying to install hamm and get this message from dselect or when I
want to mount the cdrom. I did install a cdrom as a device and did not
see iso9660 as an option amongst the filesystems during the installation
process.
Can somebody help me please?
It is not the first time I install Linux
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
"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 wi
Hi,
Anybody know what an unresolved symbol is ? I've just compiled a
kernel making iso9660 support a module. I've done this in bo with no
problems. In hamm, however, when I try to mount a cd, I get an error saying
that the kernel does not support iso9660 filesystems.
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
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
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&
Hellou Friends,
My recent Red Hat installation (don't know how to check the kernel version
yet!), says iso9660 file system not supported by kernel. It can't be like
that, because I installed from the cdrom. Is there any way out?
Also, the system does not allow me to edit a few files,
Eric Drayer wrote:
>
> currently the sugestion is to say yes to _NLS but there might be another
> fs that has somthing to do??? with iso9660.
That's appropriate. Afaik you'll need at least one NLS and one
KEYMAP (sp?) def
more detail
kernel-HOWTO (to both iso9660 and smp)
and if recommended parallel processing HOWTO for smp
>
until next mail ;)
Peter
--
:~~~ [EMAIL PROTECTED] ~~:
: student of technical computer science:
: university of a
-> > I recompiled my kernal to support two chips. When I went through
-> > the make config i did not see any thing that looked like it might belong
-> > to the iso9660 file system. I need this fs to mount my cdrom.
-> > I looked in /proc/filesystem and sure enough iso
Subject: mount -r -t iso9660...->fs not supp by kernal
Date: Wed, Dec 23, 1998 at 10:17:41AM -0700
In reply to:Eric Drayer
Quoting Eric Drayer([EMAIL PROTECTED]):
>
> I recompiled my kernal to support two chips. When I went through
> the make config i did not see an
currently the sugestion is to say yes to _NLS but there might be another
fs that has somthing to do??? with iso9660.
ORIGINAL message
I recompiled my kernal to support two chips. When I went
> _SYSU_FS
> _UFS_FS
> _XIA_FS
> _NLS
> _NFS_FS
> _NCP_FS
> _SMB_FS
> _HPFS_FS
While doing make {menu,x}config you need nls support and something else but my
mind blanked. If you read thru the fs listed in menu or x config you will see
what you missed.
I recompiled my kernal to support two chips. When I went through
the make config i did not see any thing that looked like it might belong
to the iso9660 file system. I need this fs to mount my cdrom.
I looked in /proc/filesystem and sure enough iso9660 was not there. Also
looked at the modules
> something like that?
>
> Any help is greatly appreciated.
Yes, though of course it won't be possible to boot from the CD.
Just do: (assuming the cd is already mounted under /cdrom, and the
file is "main.raw")
mount -t iso9660 -o loop,ro /cdrom/main.raw /mnt
Then, assuming
Hi All,
Today a friend of mine gave me a CD with raw binary image of hamm on it.
MD5 sum is correct. Would it be possible to use this CD as a hamm
distribution without burning new CD. May be using loopback device or
something like that?
Any help is greatly appreciated.
Eugene Sevinian
---
Frank Barknecht hat gesagt: // Frank Barknecht wrote:
>
> 1) By hand:
> As root give the command:
> $ modprobe iso9660
>
> 2) Automatically at boot time:
> put a line in /etc/modules with:
> iso9660
Oops, make
me hat gesagt: // me wrote:
> I installed Debian 2.0 from a bootable cd. Everythinng went fine until
> I rebooted
> and began deselect. I received the message "fs type iso9660 not
> supported by kernal.
> I did not see any option to enable NLS or anything that mention i
ld, it comes with the default setup).
>
>
> I installed Debian 2.0 from a bootable cd. Everythinng went fine until
> I rebooted
> and began deselect. I received the message "fs type iso9660 not
> supported by kernal.
> I did not see any option to enable NL
ed Debian 2.0 from a bootable cd. Everythinng went fine until
I rebooted
and began deselect. I received the message "fs type iso9660 not
supported by kernal.
I did not see any option to enable NLS or anything that mention iso9660
file system.
What do I need to do. If you can help
I installed Debian 2.0 from a bootable cd. Everythinng went fine until
I rebooted
and began deselect. I received the message "fs type iso9660 not
supported by kernal.
I did not see any option to enable NLS or anything that mention iso9660
file system.
What do I need to do. If you can help p
Hi,
kernel-source-2.0.33_2.0.33-9.deb (found in my hamm mirror)
-rw-r--r-- root/root 844 1998-05-01 04:38
usr/src/kernel-source-2.0.33/README.Debian
That points to stuff in /usr/doc/kernel-source-2.0.33/, which
has more docs. I mean, I am running out of places to put point
On 16 Jul 1998, Manoj Srivastava wrote:
: Hi,
: >>"E" == E L Meijer \(Eric\) writes:
:
: E> What about putting a Readme.debian in the /usr/src/linux dir of the
: E> debian kernel-source package, in which you tell people about compiling
: E> kernels the debian way? I think that would be reall
Hi,
>>"E" == E L Meijer \(Eric\) writes:
E> What about putting a Readme.debian in the /usr/src/linux dir of the
E> debian kernel-source package, in which you tell people about compiling
E> kernels the debian way? I think that would be really helpful to new
E> debian users. It seems that the
>
> Hi,
>
> Hmm. I think I shall put a note at the bottom of the man page
> pointing to the /usr/doc/kernel-package area. I have gotten too used
> to looking at /usr/doc, apparently. I have tried to put a fairly
> complete tutorial about kernel compilation in
> /usr/doc/kernel-package/R
Matthew Collins wrote:
[...]
> I have a hard enough time remembering the name of things I've
> installed. :)
I know the feeling. Try typing `dpkg -l' and you will see what you
installed.
Eric
--
E.L. Meijer ([EMAIL PROTECTED]) | tel. office +31 40 2472189
Eindhoven Univ. of Technol
Hi,
Hmm. I think I shall put a note at the bottom of the man page
pointing to the /usr/doc/kernel-package area. I have gotten too used
to looking at /usr/doc, apparently. I have tried to put a fairly
complete tutorial about kernel compilation in
/usr/doc/kernel-package/README.gz
On Wed, 15 Jul 1998 09:04:42 -0500 (CDT), you wrote:
>
>RTFM kernel-package docs. All Debian documentation is in
>/usr/doc/ ... at the very least, there will be a copyright
>file there :)
>
[snip]
>
>kernel-package is the coolest thing ever. It has a ton of options,
>works with Debian kernel
On Wed, 15 Jul 1998, Matthew Collins wrote:
[ snip ]
: All the functionallity you describe sounds really good, I (and many
: others by the sounds of things) might be missing the point here, but
: how do we USE this marvelous package? Is there any documentation,
: because the man pages are really,
On Wed, Jul 15, 1998 at 08:46:35AM +, Matthew Collins wrote:
> On 14 Jul 1998 18:21:21 -0500, you wrote:
>
> Does make-kpkg run config for you? It dosn't say.
It does not run config...you have to run make [menu,x]config yourself
> I run make config
> first, and the run make-kpkg. Off it goe
On 14 Jul 1998 18:21:21 -0500, you wrote:
> Rubbish. Please do not spread FUD. I have, at times, a round
> dozen kernel images on my machine, all compiled with
> kernel-package. I even have 2-3 2.0.34 images *ON AT THE SAME TIME*.
> Look at my lilo.conf, 5 (count it, five) different options.
Hi,
>>"Jay" == Jay Barbee <[EMAIL PROTECTED]> writes:
Jay> ...I believe I am confused... I do not mind a little
Jay> automation, but currently in my lilo.conf I have 3 linux kernels
Jay> that I use.
Jay> This kernel-package util seems as if it takes this functionality
Jay> away from you and
...I believe I am confused...
I do not mind a little automation, but currently in my lilo.conf I have 3 linux
kernels that I use.
Linux [default]
Old [Previous Image]
Experment [Pointing to /usr/src/linux/arch/i386/boot/zImage]
This kernel-package util seems as if it takes this functionality aw
config', enable the NLS support and you will get
> > the option for ISO9660, FAT, VFAT, etc...
> >
>
> I recompiled mine and I still cannot get the ISO, FAT or VFAT to mount. I
> also
> cannot load this module manually? I have not looked into this too hard, but
> I
> Nico,
>
> During your 'make menuconfig', enable the NLS support and you will get
> the option for ISO9660, FAT, VFAT, etc...
>
I recompiled mine and I still cannot get the ISO, FAT or VFAT to mount. I also
cannot load this module manually? I have not looked
Nico,
During your 'make menuconfig', enable the NLS support and you will get
the option for
ISO9660, FAT, VFAT, etc...
Steve Mayer
[EMAIL PROTECTED]
Nico De Ranter wrote:
>
> Hi,
>
> can anybody tell me how to enable iso9660 support in a 2.0.34
> kernel. There doe
*-Nico De Ranter (14 Jul)
| > On Tue, Jul 14, 1998 at 09:21:28AM +0200, Nico De Ranter wrote:
| > >
| > > Hi,
| > >
| > > can anybody tell me how to enable iso9660 support in a 2.0.34
| > > kernel. There doesn't seem to be an option when I do 'make me
On Tue, Jul 14, 1998 at 09:53:11AM +0200, Nico De Ranter wrote:
> Ah, I didn't know iso and fat where languages :-)
Changed in 2.0.35 anyway, just out.
Hamish
--
Hamish Moffatt, [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
Latest Debian packages at ftp://ftp.rising.com.au/pub/hamish.
> On Tue, Jul 14, 1998 at 09:21:28AM +0200, Nico De Ranter wrote:
> >
> > Hi,
> >
> > can anybody tell me how to enable iso9660 support in a 2.0.34
> > kernel. There doesn't seem to be an option when I do 'make menuconfig'.
>
> In men
On Tue, Jul 14, 1998 at 09:21:28AM +0200, Nico De Ranter wrote:
>
> Hi,
>
> can anybody tell me how to enable iso9660 support in a 2.0.34
> kernel. There doesn't seem to be an option when I do 'make menuconfig'.
In menu filesystems set on "Native language su
Hi,
can anybody tell me how to enable iso9660 support in a 2.0.34
kernel. There doesn't seem to be an option when I do 'make menuconfig'.
Nico
--
--
Nico De Ranter
Sony Service Center (PSDC-B/DNSE-B)
Sint Stevens Woluwestraat 55 (Rue de Woluwe-Saint-Etienne)
1130 Brussel (Brux
john, thanks for your patience and your help. purged ppp-2.3.5 and
downgraded to ppp-2.2.0f...so i'm once again happily SLiRPing along. i
had tried just downgrading without purging the newer version but got the
same behavior from 2.2 as 2.3 as long as 2.3 was on the system.
--c
[EMAIL PROTEC
Nathan E Norman writes:
> Out of curiousity, what will happen to a PPP setup in a server
> environment? (the linux box is the RAS)
The files that the ppp postinst messes with are only used by pon to dial
out. However, you may still need to do some reconfiguration as some of the
changes in pppd a
On 7 Jul 1998 [EMAIL PROTECTED] wrote:
: Dennis writes:
: > Upgrades do not affect the configurations, either. I'm not sure if they
: > do, but if chat/pppd packages prompt you during installs/upgrade, you
: > should keep the existing configuration files instead of installing the
: > maintainers
Dennis writes:
> Upgrades do not affect the configurations, either. I'm not sure if they
> do, but if chat/pppd packages prompt you during installs/upgrade, you
> should keep the existing configuration files instead of installing the
> maintainers configs. Keeping existing config files is usually
1 - 100 of 113 matches
Mail list logo
