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

Bug#255103: partconf: failed to create mount points



On Wed, Sep 29, 2004 at 11:16:08AM +0200, martin f krafft wrote:
> also sprach Gaudenz Steinlin <gaudenz@soziologie.ch> [2004.09.27.1731 +0200]:
> > Sorry for the late reply. It seems to mee that discover1 is the culprit
> > and it probably deleted the directories created in prebaseconfig. 
> > Please send the output of "discover --device cdrom" on this machine. It
> > should contain the path to your cdrom device. 
> 
> # discover --device cdrom
> discover: unrecognized option `--device'
It seems that you upgraded to discover 2.0.4 in the meantime. This bug
is only present on some systems which use the old discover1 package. The
newer version does not manage mount points at all. You can either
install discover1 and I will try to find out why discover does not
detect your cdrom device or if you don't have the time to do this I will
have to close this bug report. 

If you install discover1 could you please also tell me which kind of
cdrom you use and the device node of this device. The command "discover
--device cdrom" should output this device node.

Thanks Gaudenz

P.S.: d-i still uses (and will use for the sarge release) discover1. By
default it installs discover1 on new installs. The reason for this is
that the new version of discover became stable enough to late for the
sarge release to migrate d-i to a new hardware detection system. 

> 
> ii  discover       2.0.4-5        hardware identification system
> 
> -- 
> Please do not CC me when replying to lists; I read them!
>  
>  .''`.     martin f. krafft <madduck@debian.org>
> : :'  :    proud Debian developer, admin, and user
> `. `'`
>   `-  Debian - when you have better things to do than fixing a system
>  
> Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!


Attachment: signature.asc
Description: Digital signature


Reply to: