• Please review our updated Terms and Rules here

Questions on AT&T System V release 4 .0 v 2.1

douglasfir

New Member
Joined
Jan 31, 2024
Messages
5
I decided to give System V a shot, since I've wanted to for so long. I am somewhat familiar with Slackware command line, and OpenBSD, but this is quite an old Unix, and there's some simple things I need some help with. Firstly, is there a guide that anyone can point me to that lists the commands for the default shell? second, I have installed the editing, and networking package, and would like to get TCP/IP connectivity, can someone point me to a hardware compatibility list or somewhere that can show me what network card would be compatible? also, my one really dumb question is, how can I run the equivalent command of "dir /p" in System V, I know it'd be "ls xxx" but I cant seem to find out what exactly. I really haven't been able to find a lot of useful information in my searching so far. Please be patient with me, I'm new to this distribution :-) Thank you for any help!
 
Thank you Alex, I really appreciate you taking the time to help me :-) I'm just installing packages now, and searching for information on a compatible network interface card. Kind of neat to use a Unix that's so old, and on a 270mb hard drive at that! the smallest drive I've used since I had a 386SX in the early 90s! if anyone knows anything about setting up networking in System V, I'd love to have more information! Thanks again!
 
In Korn shell, it is fairly easy to implement 'dir' : do it as a function which runs /bin/ls.

somehthing like this:
---
dir()
{
/bin/ls "@$"
}
--
 
hi all! I'm trying to get a wd8013 to work on a SVR4 2.0 install in my at&t 6386WGS. the original ESDI drive has bitten the dust. I replaced it with an adaptec AHA15xx SCSI controller + zuluscsi that i had laying around. unfortunately, since i installed the scsi controller, i don't seem to be able to get the wd8013 to ping. the wd driver loads fine and it seems like the driver is configured correctly. is it possible that the scsi controller is somehow interfering with the network card?
 
If I remember correctly, the WD8013-based cards require an I/O address range, an IRQ and a memory window in UMB; the SCSI controller may also require a DMA channel.

The traditional ne2000 or 3c509 do not use memory windows, so make sure that none of these ranges conflict and that your UNIX kernel is configured for the correct addresses. Otherwise you will get conflicts, causing the network card to fail. (The SCSI card most likely will not fail, as it uses the memory window for its BIOS - which UNIX likely does not use while running.)
 
Back
Top