On Fri, 9 Oct 1998, Farmwagon Grafx wrote:
> I just upgraded from r5.1 to r7.1 on both my alpha UDB (RH5.0) and Intel
> (RH5.1) servers. On both, the devel package installed cleanly. On both, I
> had to exit the upgrade with ^C after getting 3 lines that said "---no tty
> available---linuxconf exiting---" followed by a linefeed and inactivity.
>
> On both machines, after changing the modules listings to .7, linuxconf
> appears to be operating properly. What is this no tty message all about?
The tty message appears when linuxconf is trying to output an error
message, but can't because stdout and stderr are not a tty and there is no
controlling tty. I am not sure why it happened on your system. I know it
can happen when you install linuxconf as part as the linux installation.
During linuxconf installation, it calls itself to register few modules.
During an initial install, some libraries are missing and linuxconf can't
execute properly. But this situation does not happen when you upgrade
linuxconf (all support libraries are there).
hum...
thinking further
When you configure some modules in linuxconf, you do not have to enter the
full path and release (unless the module is locate in a special path). All
you need to do is enter the module name and linuxconf will find the proper
version to load.
This may explain the error message. Linuxconf was trying to load missing
modules (from previous linuxconf install) and was signaling errors for
each. This probably explain the "no tty" message.
--------------------------
Jacques Gelinas
[EMAIL PROTECTED]
---
You are currently subscribed to linuxconf as: [[email protected]]
To unsubscribe, forward this message to [EMAIL PROTECTED]
