Please consider a donation to the Higher Intellect project. See or the Donate to Higher Intellect page for more info.

Difference between revisions of "NeXTSTEP"

From Higher Intellect Vintage Wiki
Jump to navigation Jump to search
Line 168: Line 168:
and avoid the problem altogether.
and avoid the problem altogether.
==See Also==
* [[Installing NEXTSTEP/OPENSTEP On A Laptop]]
[[Category:Operating Systems]]
[[Category:Operating Systems]]

Revision as of 12:17, 10 July 2019

May also be written as NeXTStep or NEXTSTEP.



Reset root password

You need to interrupt the bootloader when the machine is turned on so you see a "boot:" prompt or something similar depending on the type of computer. Type "-s" without the quotes and hit enter. If this is NeXT hardware, type "bsd -s" without the quotes. When the system drops you into a single mode root shell, type "sh /etc/rc &" to start the normal services. Now do "passwd root" and enter your new password. Reboot the system.

Basic TCP/IP Config

Create /etc/resolv.conf and add your desired nameserver, so something like "nameserver" and save the file. Go to NextAdmin directory and open, click Local in the menu, use local domain only and readable, set your desired IP/router/netmask info and reboot.

NIS Client

You have to convince lookupd to look for information via NIS:

% nidump -r /locations/lookupd /
name = lookupd;
LookupOrder = (CacheAgent, NIAgent);
MaxThreads = 12;
    name = hosts;
    LookupOrder = (CacheAgent, NIAgent, DNSAgent);
    ValidateCache = NO;
}, {
    name = users;
    LookupOrder = (CacheAgent, NIAgent, YPAgent);

However, I forget whether 3.3 is recent enough to do this type of
configuration.  If not, you might try enabling the YPDOMAIN in
/etc/hostconfig and/or niloading a /etc/passwd file with just a "+" in
it to enable YP-based passwd lookups.

>If not, you might try enabling the YPDOMAIN in
>/etc/hostconfig and/or niloading a /etc/passwd file with just a "+" in
>it to enable YP-based passwd lookups.
There's no need to load /etc/passwd into NetInfo, the login program looks in
the flat file for information.

The line in /etc/passwd should be a "+:", I think (that's the way I'm using

and if there are any NIS groups, adding the same line to the end of
/etc/group would be a good idea.

So, the steps are as follows for 3.3:

Make sure there's a line YPDOMAIN=DOMAIN in /etc/hostconfig
Make sure NIS login and group lookup is enabled by editing /etc/passwd and
Reboot, or set domainname and run ypbind.

PCMCIA Support

: My question is what PCMCIA card is known to work ( besides the
: impossible to find Xircom for which drivers are available at NexTanswers.) 
: If  someone has been able to make the 3C589 ( of which I see many 
:variations ) work, what has to be done ?
for us, after chosing the right(!) interrupt (experiment a little bit
there), any 3Com589 card did - the last one we used was a version 'D'
(iirc, it might also be 'E').

The important part is to add the 'letter' behind 589 to the drivers'
id-strings (something like manufactuerer="3Com", type="589D") in the
/private/drivers/i386/"589-driver".config directory. I don't have a
version of these notebooks available, but it was quite trivial.

Not so trivial was to find the right interrupt. With the "wrong", so
allowed ones, the card was detected but simply wouldn't work (i.e. it
wouldn't send, iirc). That was a decision between an IRQ either below or
above IRQ8 (so 3, 4, 5(used by PCIC-driver), 7, or 9, 10, 11), only one
group worked (for us); I think it were the 'lower ones' and I decided
to use '3', swapping it for the second serial port, but I'm not sure.

: Hmmm, I may did something wrong, but I am not able to get a 589E to run.  
: It is some kind of 'Megahertz', up to D the cards work fine.
No, caveat emptor, my memory could play me a trick; I'm just sure a
'bunch of 589 cards' did work, not of the up to 'E' statement. For
certain I also do know it of the 'D' version, as I've put them into
to Toshibas (a Tecra 750 and a Satellite 4000) successfully.


Make: Don't know how to make /usr/include/sys/signal.h

You'll find this file under the path name /usr/include/bsd/sys/signal.h. The problem is that Makefile contains an incorrect absolution path name to signal.h (line 36):

SIGNAL = /usr/include/sys/signal.h

Change it to read:

SIGNAL = /usr/include/bsd/sys/signal.h

and then say "make".

Boot Issues

That works, once I'm in the ROM Monitor I tell it to bsd(0,0,0)sdmach rootdev=sd0
which boots the CDROM, after I tell it to reinstall it looks for the drive and bombs because it
tries to install to the CDROM. I also used p and told it not to boot en. But when I tell it to boot
sd t boots my CDROM again. I'm beginning to think that harddisk is bad.
        Once it has rebooted it no longer tries to boot from network, but it still doesn't find a device to
boot from and gives me a "blk0 boot:" prompt. I guess I don't really know what the prompt is asking
for because sd, sd0, sd0a, and /dev/sd0 or variations of that don't work..  

Well, I have finally installed NeXTStep.. I installed it on my 100MB harddisk, sd1a. Now I cannot
get it to boot, with the boot device set to sd (from prefs) it boots the CD, or tries if I remove
it, with it set to fd it will boot a floppy.. but I don't know how to get it to boot my harddisk..
I've tried bsd(0,0,0)mach rootdev=sd1a, bsd(0,1,0)mach rootdev=sd1.. and many other combinations.
Does someone know what to set to boot it?


You must set the device SCSI ID order of HD to be lower than 
that of the CD.  Long ago I tried to coax installs on floppyless systems by putting the CD-ROM lower 
than the SCSI drive.  It will install but won't boot -even after you swap SCSI ID's.  I didn't dig 
much deeper and this was long ago as I thought this might be a way to install on the older floppyless 
systems.  I suspect that one would have to do some manual file tweaking..  Even so

rootdev must be device 0 AFAIK..


I also went down this path some years ago.  The install script that
gets run when you boot from CD-ROM is called
/NEXTSTEP_3.3/private/etc/rc.cdrom .  Under normal conditions, after
installing lots of stuff on the hard disk, it prepares for the reboot
by creating "on the fly" a special /private/etc/fstab file on the HD.
This file would normally contain two entries:
        /dev/sd0a / 4.3 rw,noquota,noauto 0 1
        /dev/sd1a /NEXTSTEP_INSTALL ro,noquota 0 2
Then when the reboot happens, the HD gets mounted as / and the
CD-ROM gets mounted as /NEXTSTEP_INSTALL and the installation 
procedure continues.

However, if the device numbers are swapped initially, the install
goes fine, but the new fstab file also has the devices swapped, i.e.,
it becomes
        /dev/sd1a / 4.3 rw,noquota,noauto 0 1
        /dev/sd0a /NEXTSTEP_INSTALL ro,noquota 0 2
Now if you try to reboot, it again boots from CD-ROM and restarts
the installation from the beginning.  If you change device numbers and
reboot, it boots from the HD but then attempts to mount the HD as
/NEXTSTEP_INSTALL and the CD-ROM as /.  This also causes the boot to

It might be possible to continue the installation at this point by
NOT changing the device numbers but using a special boot command:
    bsd(1,0,0)sdmach rootdev=sd1a
However, I think I may have tried this and found that it also doesn't
work.  I'm not sure though.

Another way to recover (short of starting all over) is to somehow get
booted into single-user mode, remount the HD in read-write mode (if
necessary), and edit /private/etc/fstab.  Then swap the device numbers
and reboot normally.  I don't remember any more how I managed to get
into single user mode with the messed-up fstab file.  I think I
unplugged the CD-ROM, booted into single-user mode, found that / was
mounted read-only, and remounted it read-write so that I could fix

It's nice to know you can do these things in an emergency, but the
best advice is, set the CD-ROM to a higher device number than the HD
and avoid the problem altogether.

See Also