Il dom, 2005-01-23 alle 12:26, Anne Wilson ha scritto :
> There seems to be very little known about the causes of this problem. It
> could be udev or it could be hotplug - at least, I suspect that some
> developers are working hard on it, but there are no hard-and-fast answers
> available on t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 23 Jan 2005 11:13, SnapafunFrank wrote:
> I have had other problems to deal with that I believe stemmed from this
> so now that I am back and have read all the great feedback to this
> thread can I ask what is probably a silly question?
>
No
Lukas Ruzicka wrote:
Supermount could be the problem because the vanilla kernel doesn't use
this feature. Nevertheless I could not mount even devices, where the
supermaount had been turned off.
L.
At least you're not alone. Some time ago there was a thread about
"the ghost in the machine". It
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 20 Jan 2005 14:20, Kaj Haulrich wrote:
> On Thursday 20 January 2005 14:53, Anne Wilson wrote:
> > I do get bitten by the floating device names for removable
> > devices, though. It never happened under 9.1, and I don't think
> > it happen
Il gio, 2005-01-20 alle 14:53, Anne Wilson ha scritto:
> On box2, 10.1
[CUT]
> none /mnt/cdrom supermount
> dev=/dev/hdc,fs=auto,ro,--,umask=0022,user,iocharset=iso8859-15,codepage=850,suid,users
>
> 0 0
> none /mnt/cdrom2 supermount
> dev=/dev/hdd,fs=auto,--,umask=0,user,iocharset=iso8859-1
On Thursday 20 January 2005 15:00, Dennis Myers wrote:
> On Thursday 20 January 2005 07:25 am, Kaj Haulrich wrote:
> > On Thursday 20 January 2005 12:07, Anne Wilson wrote:
> > > On Thursday 20 Jan 2005 11:01, Kaj Haulrich wrote:
> > > > At least you're not alone. Some time ago there was a
> > > >
On Thursday 20 January 2005 14:53, Anne Wilson wrote:
> On Thursday 20 Jan 2005 13:25, Kaj Haulrich wrote:>
>
> > Anne, I envy you. Could you please tell me how ?
>
> No - haven't a clue ;-)
>
> > -- Eventually post
> > your fstab ?
>
> On this box, 10.0
>
> /dev/hde12 / ext3 defaults 1 1
> /dev/h
On Thursday 20 January 2005 07:25 am, Kaj Haulrich wrote:
> On Thursday 20 January 2005 12:07, Anne Wilson wrote:
> > On Thursday 20 Jan 2005 11:01, Kaj Haulrich wrote:
> > > At least you're not alone. Some time ago there was a thread
> > > about "the ghost in the machine". It turned out the culp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 20 Jan 2005 13:25, Kaj Haulrich wrote:>
> Anne, I envy you. Could you please tell me how ?
No - haven't a clue ;-)
> -- Eventually post
> your fstab ?
>
On this box, 10.0
/dev/hde12 / ext3 defaults 1 1
/dev/hde8 /boot ext2 defaults 1 2
On Thursday 20 January 2005 12:07, Anne Wilson wrote:
> On Thursday 20 Jan 2005 11:01, Kaj Haulrich wrote:
> > At least you're not alone. Some time ago there was a thread
> > about "the ghost in the machine". It turned out the culprit
> > was supermount. This devil have plagued us for years now.
I've seen lots of other problems mentioned with the 2.6.10 kernel. I think
that maybe it's not yet production-level?
Anne
On the other hand it helped to solve my usb problem I had with distro
kernel, so a hand made fstab is OK. No other problems encountered yet.
Lukas
- --
Registered Linu
Supermount could be the problem because the vanilla kernel doesn't use
this feature. Nevertheless I could not mount even devices, where the
supermaount had been turned off.
L.
At least you're not alone. Some time ago there was a thread about
"the ghost in the machine". It turned out the culpr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 20 Jan 2005 11:28, Lukas Ruzicka wrote:
> >I've never come across that. Are we talking about major differences, like
> >booting to a 2.4 kernel and a 2.6 kernel? I think I've only ever had
> > minor differences in kernels at any one time.
I've never come across that. Are we talking about major differences, like
booting to a 2.4 kernel and a 2.6 kernel? I think I've only ever had minor
differences in kernels at any one time.
Anne
I mean that 2.6.8.12mdk mounted everything allright, but new 2.6.10
didn't and everytime I trie
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 20 Jan 2005 11:01, Kaj Haulrich wrote:
>
> At least you're not alone. Some time ago there was a thread about
> "the ghost in the machine". It turned out the culprit was
> supermount. This devil have plagued us for years now. In 10.1 is
On Thursday 20 January 2005 11:43, Lukas Ruzicka wrote:
> Anne Wilson napsal(a):
> >-BEGIN PGP SIGNED MESSAGE-
> >Hash: SHA1
> >
> >On Thursday 20 Jan 2005 06:51, SnapafunFrank wrote:
> >>I'm trying to get udev working functionally so am revisiting my
> >> previous attempts from scratch to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 20 Jan 2005 10:43, Lukas Ruzicka wrote:
> But sometimes, especially if you boot up various kernels, the fstab
> created by MCC behaves strangely. I had to edit it per hand and then it
> worked.
>
I've never come across that. Are we talking
Anne Wilson napsal(a):
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 20 Jan 2005 06:51, SnapafunFrank wrote:
I'm trying to get udev working functionally so am revisiting my previous
attempts from scratch to put "my house in order".
First port of call is the fstab file and within that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 20 Jan 2005 06:51, SnapafunFrank wrote:
> I'm trying to get udev working functionally so am revisiting my previous
> attempts from scratch to put "my house in order".
>
> First port of call is the fstab file and within that I believe I may
I'm trying to get udev working functionally so am revisiting my previous
attempts from scratch to put "my house in order".
First port of call is the fstab file and within that I believe I may
have some problems.
From my notes to myself:
**
20 matches
Mail list logo
