Re: [Cooker] Supermount killed my DVD/CDRW combo drive (suggestion for MDK)
I remember that when supermount was first incorporated into Mandrake, there was an easy to find option during the installation that allowed the user to turn it off before it was installed. Anyway of getting that re-incorporated into 8.2? On Thursday 07 February 2002 09:58 am, Jason Straight wrote: I agree, my opinion is that supermount sucks, until the kernel handles hot swapping better or something. As soon as I try to access something under the mnt dir or whatever when the wrong device is in all hell breaks loose. I wish for us laptop users with modular accessories mdk would put in a choice to use supermount or regular old manual mount - it's not that hard to mount and unmount devices manually. I think it's one of those instances where the product is dumified for customers who can't understand and made annoying for those who can. On Wednesday 06 February 2002 10:28, J. Patrick Smith wrote: Hello. The subject line is misleading. I did for several days assume that my drive had been somehow damaged, but in the preparation of this message, I tried to burn a CD again, and it actually worked. I recently downloaded 8.2beta1 for testing. Following installation, my system froze during the boot process when supermount began accessing my drives. I am using a Toshiba Satellite 3005/S303 which has a modular bay in which I can have either the DVD/CDRW combo drive installed or the Floppy drive. Naturally, I booted with the DVD/CDRW installed. There needs to either be a workaround to prevent supermount from locking up if the floppy drive is not actually present or an errata to indicate that supermount needs to boot with the floppy drive installed. Has anyone else met the same situation? or similar?
Re: [Cooker] Supermount killed my DVD/CDRW combo drive
Borsenkow Andrej [EMAIL PROTECTED] writes: Does it hang after Turning on user and group quotas for local filesystems: messages? In this case (if you can reliably reproduce this problem) could you try the included patch for /etc/rc.d/rc.sysinit and tell if it fixes the problem? The patch look fine for me btw:. -- http://www.chmouel.org/
Re: [Cooker] Supermount killed my DVD/CDRW combo drive
j == J Patrick Smith [EMAIL PROTECTED] writes: j Hello. j The subject line is misleading. I did for several days assume that my drive j had been somehow damaged, but in the preparation of this message, I tried to j burn a CD again, and it actually worked. j I recently downloaded 8.2beta1 for testing. j Following installation, my system froze during the boot process when j supermount began accessing my drives. j I am using a Toshiba Satellite 3005/S303 which has a modular bay in which I j can have either the DVD/CDRW combo drive installed or the Floppy drive. j Naturally, I booted with the DVD/CDRW installed. j There needs to either be a workaround to prevent supermount from locking up j if the floppy drive is not actually present or an errata to indicate that j supermount needs to boot with the floppy drive installed. j Has anyone else met the same situation? or similar? Wait for kernel-2.4.17-16mdk (to appear later today or tommorow), has a new supermount patch. Later, Juan. -- In theory, practice and theory are the same, but in practice they are different -- Larry McVoy
Re: [Cooker] Supermount killed my DVD/CDRW combo drive (suggestion for MDK)
I agree, my opinion is that supermount sucks, until the kernel handles hot swapping better or something. As soon as I try to access something under the mnt dir or whatever when the wrong device is in all hell breaks loose. I wish for us laptop users with modular accessories mdk would put in a choice to use supermount or regular old manual mount - it's not that hard to mount and unmount devices manually. I think it's one of those instances where the product is dumified for customers who can't understand and made annoying for those who can. On Wednesday 06 February 2002 10:28, J. Patrick Smith wrote: Hello. The subject line is misleading. I did for several days assume that my drive had been somehow damaged, but in the preparation of this message, I tried to burn a CD again, and it actually worked. I recently downloaded 8.2beta1 for testing. Following installation, my system froze during the boot process when supermount began accessing my drives. I am using a Toshiba Satellite 3005/S303 which has a modular bay in which I can have either the DVD/CDRW combo drive installed or the Floppy drive. Naturally, I booted with the DVD/CDRW installed. There needs to either be a workaround to prevent supermount from locking up if the floppy drive is not actually present or an errata to indicate that supermount needs to boot with the floppy drive installed. Has anyone else met the same situation? or similar? -- ^^^ Jason Straight -- President BlazeConnect Internet Services -- Cheboygan Michigan ISP: www.blazeconnect.net Products: www.blazeconnect.com Phone: 231-597-0376 -- Fax: 231-597-0393
Re: [Cooker] Supermount killed my DVD/CDRW combo drive
i have a smiliar problems too. I have both a 3.5 and a 5.1/4 floppy drive and i know both works but for some reason if i have floppy2 (5.1/4) specified in /etc/fstab it hangs during the kde startup. /MattB On Wed, 2002-02-06 at 09:28, J. Patrick Smith wrote: Hello. The subject line is misleading. I did for several days assume that my drive had been somehow damaged, but in the preparation of this message, I tried to burn a CD again, and it actually worked. I recently downloaded 8.2beta1 for testing. Following installation, my system froze during the boot process when supermount began accessing my drives. I am using a Toshiba Satellite 3005/S303 which has a modular bay in which I can have either the DVD/CDRW combo drive installed or the Floppy drive. Naturally, I booted with the DVD/CDRW installed. There needs to either be a workaround to prevent supermount from locking up if the floppy drive is not actually present or an errata to indicate that supermount needs to boot with the floppy drive installed. Has anyone else met the same situation? or similar?
RE: [Cooker] Supermount killed my DVD/CDRW combo drive
The subject line is misleading.
The more misleading subject is the more likely messages gets ignored.
I did for several days assume that my drive
had been somehow damaged, but in the preparation of this message, I
tried to
burn a CD again, and it actually worked.
I recently downloaded 8.2beta1 for testing.
Following installation, my system froze during the boot process when
supermount began accessing my drives.
Does it hang after Turning on user and group quotas for local
filesystems: messages? In this case (if you can reliably reproduce this
problem) could you try the included patch for /etc/rc.d/rc.sysinit and
tell if it fixes the problem?
Please, if you report bug, report it with details. Else it is likely
that it simply will be ignored.
I am using a Toshiba Satellite 3005/S303 which has a modular bay in
which I
can have either the DVD/CDRW combo drive installed or the Floppy
drive.
Naturally, I booted with the DVD/CDRW installed.
There needs to either be a workaround to prevent supermount from
locking up
if the floppy drive is not actually present or an errata to indicate
that
supermount needs to boot with the floppy drive installed.
As you may guess if it happened on everyone's system it had been fixed
long ago. It happens only on some systems. It means that you should take
some steps to debug it. Or at least make a proper report stating when
exactly your system hangs and why do you think it is related to
supermount at all :-)
-andrej
--- /etc/rc.d/rc.sysinit.orig Wed Jan 30 21:51:30 2002
+++ /etc/rc.d/rc.sysinitWed Feb 6 19:14:55 2002
@@ -807,6 +807,9 @@
# Mount loopback
action Mounting loopback filesystems: mount -a -O loop
+# Reset pam_console permissions
+rm -rf /var/lock/console.lock /var/lock/console/*
+
# Restart devfsd actions now that the filesystems are ready
if [ -c /dev/.devfsd ]; then
if [ -x /sbin/devfsd ]; then
@@ -936,9 +939,8 @@
done
rm -f /var/lib/rpm/__db*
-# Reset pam_console permissions
-rm -rf /var/lock/console.lock /var/lock/console/*
-[ -x /sbin/pam_console_apply ] /sbin/pam_console_apply -r
+[ -x /sbin/pam_console_apply -a ! -c /dev/.devfsd ] \
+/sbin/pam_console_apply -r
{
# Clean up utmp/wtmp
Re: [Cooker] Supermount killed my DVD/CDRW combo drive
yup, It does not seem to have a problem with a 2nd cdrom/cdrw/dvd because the system automatically recognizes the addition of another hd*, hoever the floppy is assumed and not checked so when it is removedlock up. --- J. Patrick Smith [EMAIL PROTECTED] wrote: Hello. The subject line is misleading. I did for several days assume that my drive had been somehow damaged, but in the preparation of this message, I tried to burn a CD again, and it actually worked. I recently downloaded 8.2beta1 for testing. Following installation, my system froze during the boot process when supermount began accessing my drives. I am using a Toshiba Satellite 3005/S303 which has a modular bay in which I can have either the DVD/CDRW combo drive installed or the Floppy drive. Naturally, I booted with the DVD/CDRW installed. There needs to either be a workaround to prevent supermount from locking up if the floppy drive is not actually present or an errata to indicate that supermount needs to boot with the floppy drive installed. Has anyone else met the same situation? or similar? __ Do You Yahoo!? Send FREE Valentine eCards with Yahoo! Greetings! http://greetings.yahoo.com
