home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!moe.ksu.ksu.edu!matt.ksu.ksu.edu!news
- From: probreak@matt.ksu.ksu.edu (James Michael Chacon)
- Newsgroups: comp.os.linux
- Subject: Re: Help Needed for Linux.
- Date: 21 Dec 1992 18:07:17 -0600
- Organization: Kansas State University
- Lines: 106
- Message-ID: <1h5m7lINNko8@matt.ksu.ksu.edu>
- References: <1992Dec21.063353.6903@sfu.ca>
- NNTP-Posting-Host: matt.ksu.ksu.edu
-
- wonge@fraser.sfu.ca (Edmund Wong) writes:
-
-
- > I have a few questions to ask about Linux. Here goes.
-
- > 1) What procedures do I need to go through in order to make my
- > linux system 'available' for remote log-ins?
-
- In the FAQ there is a section on how to do this with getty. Also you can
- download the getty_ps package from tsx-11.mit.edu in the /pub/linux/sources/..
- (somewhere in there).
-
- > 2) When a non-root user logs on and does a 'elm' command, the system
- > says "You have no password entry!" and throws the non-root user(me)
- > to the system prompt. What is the problem?
-
- Don't know here, haven't installed elm yet. (Need another line for my uucp
- feed :-)
-
- > 3) Where can I get the extra man-pages for the 'w' command..?
-
- > 4) (related to 3). When a non-root user does a 'w' command, the system
- > gives the user a '/dev/kmem: Permission denied' message. Why and
- > how do I get rid of it and allow the user to use the 'w' command.
-
- As root, issue the following command.
-
- chown root.mem /bin/w; chmod 2755 /bin/w. (If that's where w is on your system
- of course. otherwise change the path accordingly).
-
- >
- > 5) (related to 'w' command). When a root user does a 'w' command,
- > it gives the normal list of users on, and the necessary headings,
- > but it does not display what each user is really doing. ie.
-
- > User tty login@ idle JCPU PCPU what
- > root tty1 10:05pm
- > wonge tty2 10:11pm
-
- > It doesn't show anything in the JCPU, PCPU and what columns.
- > Why?
-
- Sounds like you need to recompile the ps package as mine shows up fine.
- You can get that from tsx-11.mit.edu in the /pub/linux/sources/sbin I believe.
-
- > 6) Also, when I do a 'w' command(as the root user), I also get
- > THREE extra LOGIN devices. What are they for?
-
- > i.e.
- > User tty login@ idle JCPU PCPU what
- > root tty1 10:05pm
- > LOGIN tty4 10:04pm 10
- > LOGIN tty3 10:04pm 10
- > wonge tty2 10:11pm
- > * LOGIN tty6 21Jan804647days
- > * LOGIN tty5 21Jan804647days
- > * LOGIN ttyp1 16Nov9289days
-
- > The LOGINs with the *'s are the EXTRA devices that I'm not sure
- > of. When I do a ALT-F6 for example, I only get a blank screen.
- > What are these extra LOGIN's for?
-
- Check /etc/inittab and see if its spawning getty's on those devices. That
- may be the default as an example.
-
- >
- > 7) I've installed the base system and X11 as well as the compilers
- > to /dev/hda2. How do I install the TeX package from my
- > 3 1/2 floppy? Whenever I do a 'sysinstall -series t' it
- > ALWAYS reads from my A: drive. I want it to install from my
- > B drive. I also have tried the 'sysinstall -instdev /dev/fd1'
- > command(if that's how I use it) and it still doesn't work, in
- > fact, it only displays the same help screen for 'sysinstall'.
-
- > 8) I can't seem to get the X11 to work. When I do a 'startx'
- > command, the following screen appears:-
-
- > Creating TCP socket: Invalid argument
- > XFree86 Version 1.0Ya / X Window System
- > (protocol Version 11, revision 0, vendor release 5000)
- > Configured drivers:
- > VGA256 (256 colour SVGA);
- > et4000, et3000, pvga1, gvga, ati, tvga8900
- > VGA256: et4000 (mem: 0k numclocks: 16)
- > VGA256: clocks: 25 28 36 27 30 33 20 24 50 57 72 45 60 65 40 47
- > VGA256: Too little memory for virtual resolution
- > I have a Trident 8900 card(?), with 512k, a CTX SVGA monitor
- > for a 486/33 clone with 8megs of ram.
- > **
- > I hope someone out there can help me with the above questions..
- >--
- >InterNet: wonge@fraser.sfu.ca | "Fail not; Learn Not.
-
- From what I see, X thinks you have an et4000 chipset on your card and so
- it can't figure out how to work with your trident. In /usr/X386/lib/X11
- there is a file named Xconfig. In the vga256 and vga2 sections add the
- following line:
-
-
- chipset tvga8900
-
- And see if that works now. Your card has to be an 8900c or it won't work.
- There isn't any planned work on the 8800 or 8900b cards either, sorry.
-
- James
-
-