On Thu, 15 Jul 1999, you wrote:
> John Aldrich wrote:
>
> > On Thu, 15 Jul 1999, you wrote:
> > > Ken Wilson wrote:
> > > >
> > > > for Xwindows type 'startx &'
> > > >
> > >
> > > Excuse me but...
> > > (showing glaringly my newbie status :-))
> > > What's the ampersand for? I normally just type "startx" and hey presto! It
> > > starts.
> > >
> > The "&" means run it in "background mode." Why you'd do
> > that with X, I don't know (mine always works fine the
> > standard way... if I need to do something else, I just hit
> > CTRL+ALT+F1. Typically I log in as "root" on VC1 and log in
> > as my "user account" on VC2, running X from VC2. Then, if I
> > HAVE to do something in console mode, it's easy enough to
> > change around w/o having to log in again, plus if it's
> > something that requires "root" priveleges, I am already
> > logged in as "root." :-)
>
> one quick question for you, While trying to configure a few things I've
> managed to lock up the terminal I'm using,x most often it seems, now how do
> you go about killing something from a different login/term?
> I've read (skimmed) through the man kill,and the ps(? running processes,
> still not all in memory yet) pages,and it wasn't all that clear,plus I'm
> primarily trying to get the system running right first,then learning the
> nuances afterwards,my philosophy being that if I know how to get it up and
> running right,it won't be so terrible if I screw it up.
well, logi in on another console as root. Enter "ps ax" (no quotes)
at the prompt, which should give a list of the running processes.
Each one is identified by a PID number (Process IDentification).
So type kill PID, substuting the actual pid number for PID.
There are at least two stages of kill, with kill -9 PID being the
most severe.Use it with caution, though; I've heard it can possibly
corrupt your filesystem.
