[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: discover1 vs discover vs discover2 debian installer bug



On Mon, 2005-05-16 at 10:30 -0400, Mitchell Laks wrote:
> On Monday 16 May 2005 10:04 am, Mitchell Laks wrote:
> > discover issues:
> >
> > I have seen references to /media/cdrom0 and /media/cdrom2 not being created
> > as a result of a bug in discover.
> 
> >
> > apt-cache show discover1 is what i have loaded. it is credited to the
> > debian installer team version 1.7.7 is current.
> >
> > discover2 is version 2.0.7-2.1
> > credited to the discover workers and is in conflict with discover1.
> >
> > i did a debian sarge install with i guess discover1. is my problem the need
> > to switch to discover2 which fixed the bug?
> 
> Even though I googled and found a ubunto thread that claimed that 
> the /media/cdom0 was fixed with later discover versions, and 
> 
> 
> i tried this solution and I am running sid, and upgraded to discover = 
> discover2 from discover1, i still have the problem. 


Desktop System Setup with Debian GNU/Linux 3.1 'Sarge' located at
http://thegoldenear.org/toolbox/unices/desktop-system-setup-debian-sarge.html#installation
mentions this problem abd suggests work around.

(In Installation section):

When asked during the installation if you want 'discover' to
manage /media/cdrom0, choose 'no' otherwise gnome-volume-manager won't
be able to auto-mount discs for you when inserted and logged in as a
normal user. (this may now be fixed).

In troubleshooting section.

gnome-volume-manager won't be able to auto-mount discs when inserted if
discover/discover1 is managing /media/cdrom0 because that directory will
get removed by discover/discover1. To fix this, either choose not to
have discover/discover1 do this at installation (see note in the
'Installation' section; or uninstall discover/discover1 (but we don't
yet know of other ramifications of doing this); or there should be a way
of disabling this aspect of discover/discover1 once its installed, but
we don't know of it yet)

I wonder if one should simple reconfigure discover to stop it from
removing CDROM.

sudo dpkg-reconfigure discover1


> 
> >
> > if so has this been passed to the debian installer team?
> 
> i am suprised to have to do mkdir /media/cdrom[01] each time i reboot. I know 
> how to write my own init script to do this, and yet it seems stupid to have 
> to do this. what is overwriting /media or over mounting /media???
> >
> > mitchell
> 

-- 
______________________________________________________________________

Ivan Teliatnikov                phone: +61 2 9351 2031
F05, Edgworth David Bld.          fax: +61 2 9351 0184
School of Geosciences           email: ivan@geosci.usyd.edu.au
Univrsity of Sydney               www: http://www.geosci.usyd.edu.au
Australia
______________________________________________________________________
-- 
______________________________________________________________________

Ivan Teliatnikov                phone: +61 2 9351 2031
F05, Edgworth David Bld.          fax: +61 2 9351 0184
School of Geosciences           email: ivan@geosci.usyd.edu.au
Univrsity of Sydney               www: http://www.geosci.usyd.edu.au
Australia
______________________________________________________________________



Reply to: