Bug#67771: modconf or not?

To: Debian Bugs Control <done@bugs.debian.org>
Cc: Debian Bugs Control <67771@bugs.debian.org>
Subject: Bug#67771: modconf or not?
From: Martin Schulze <joey@finlandia.Infodrom.North.DE>
Date: Tue, 15 Aug 2000 20:38:55 +0200
Message-id: <[🔎] 20000815203855.C30982@finlandia.infodrom.north.de>
Reply-to: Martin Schulze <joey@infodrom.north.de>, 67771@bugs.debian.org
In-reply-to: <20000813143433.Y8132@finlandia.infodrom.north.de>; from joey on Sun, Aug 13, 2000 at 02:34:33PM +0200
References: <20000813143433.Y8132@finlandia.infodrom.north.de>

reopen 67771
thanks

Martin Schulze wrote:
> The bug was fixed by reinstalling whiptail...

Sorry, tausq is right.  The bug is persitant.  After a brandnew installation
I was not able to run modconf after I rebooted the system.

Randolph Chung wrote:
> please try running modconf as
>         bash -x modconf

[...]
+ directory=modconf: /dev/tty: Device not configured
[...]

Regards,

	Joey

-- 
Life is too short to run proprietary software.  -- Bdale Garbee

Please always Cc to me when replying to me on the lists.

Reply to:

Follow-Ups:
- Bug#67771: modconf or not?
  - From: Adam Di Carlo <adam@onshore.com>

Prev by Date: Re: /boot nonexistant on sun4cdm install disk set
Next by Date: Bug#69197: base: Inadequate backup instructions and tools
Previous by thread: Re: Potato now stable
Next by thread: Bug#67771: modconf or not?
Index(es):
- Date
- Thread