Line 1: |
Line 1: |
− | May also be written as NeXTStep or NEXTSTEP. | + | May also be written as NeXTStep or NEXTSTEP. This is an operating system from [[NeXT]] originally designed for their m68k hardware. |
| | | |
| | | |
Line 233: |
Line 233: |
| (including the pty's). Otherwise, you're probably missing a setuid bit on | | (including the pty's). Otherwise, you're probably missing a setuid bit on |
| the OpenSesame binary itself.... | | the OpenSesame binary itself.... |
| + | </pre> |
| + | |
| + | ===loginwindow issues=== |
| + | <pre> |
| + | > I've got a problem when I boot my NextCube (NS 3.0): |
| + | > |
| + | > At the end of the booting session, a "console" window appears, instead |
| + | > of the loginwindow. |
| + | > I tried to launch the loginwindow by hand, but nothing happens. I tried |
| + | > also to launch the WindowServer, but I've got a Memory Fault. |
| + | > |
| + | > The strange thing is that I've done nothing on config files. I thought |
| + | > my disk was corrupted, but fsck didn't find an error. |
| + | > |
| + | > Has anyone got a clue about this ? Do I need to re-install the system ?? |
| + | |
| + | |
| + | That's pretty strange that it just started doing that. Control over this |
| + | is in the /etc/ttys file. The first two data lines should look like this: |
| + | |
| + | |
| + | # console "/usr/etc/getty std.9600" NeXT on secure |
| + | |
| + | console /usr/lib/NextStep/loginwindow NeXT on secure window=/usr/li |
| + | b/NextStep/WindowServer onoption="/usr/etc/getty std.9600" |
| + | |
| + | (I seperated them because the second line is long) |
| + | |
| + | It's very important that the first console line be commented out. I think |
| + | uncommenting it will make that other console appear rather than the |
| + | loginwindow. |
| + | |
| + | If something is wrong here and the path isn't the loginwindow or is |
| + | something has happened to the loginwindow permissions-wise or if it has |
| + | gotten corrupted, that could explain why it isn't launching. |
| + | |
| + | You might want to try recopying the loginwindow from your CD if you have |
| + | it. But otherwise, a reinstall may be the easier than tracking down the |
| + | real problem, which you may not be able to fix anyway. |
| </pre> | | </pre> |
| | | |