Re: minimum X packages?

1999-02-09 Thread Branden Robinson
On Mon, Feb 08, 1999 at 06:31:35PM -0600, Oleg Krivosheev wrote:
> hi
> 
> why -10 insists on having tons of stuff installed i really
> don't use?
> 
> like xfs, or rstart(d), or twm (is there any person alive who
> uses twm?), or xmh, or xterm, or...

It doesn't.  Read the extended description of the xbase package.

-- 
G. Branden Robinson  |I have a truly elegant proof of the
Debian GNU/Linux |above, but it is too long to fit into
[EMAIL PROTECTED]   |this .signature file.
cartoon.ecn.purdue.edu/~branden/ |


pgpe939CP3U9R.pgp
Description: PGP signature


Re: minimum X packages?

1999-02-09 Thread Oleg Krivosheev
On Mon, 8 Feb 1999, Branden Robinson wrote:

> On Sun, Feb 07, 1999 at 11:19:07AM -0800, Paul Nathan Puri wrote:
> > I recently upgraded to potato.
> > 
> > Now X starts and immediately dies.  Why would this be?
> 
> This is (probably) a known bug in -9.  Upgrade to -10.
> 
> > What are the minimum packages necessary to run X under potato (or in 
> > general)?
> 
> xfree86-common
> xlib6g
> xbase-clients
> xserver-common
> xserver-(svga, s3v, mach64, ? -- depends on your video card)
> xfonts-base
> xfonts-75dpi (depending on your X clients you *might* be able to scrape by
> without this one)
> 
> You will probably want a window manager and a terminal emulator as well.
> 
> Read the extended description of xfree86-common as well.
> 

hi

why -10 insists on having tons of stuff installed i really
don't use?

like xfs, or rstart(d), or twm (is there any person alive who
uses twm?), or xmh, or xterm, or...

regards

OK


Re: minimum X packages?

1999-02-08 Thread Branden Robinson
On Sun, Feb 07, 1999 at 11:19:07AM -0800, Paul Nathan Puri wrote:
> I recently upgraded to potato.
> 
> Now X starts and immediately dies.  Why would this be?

This is (probably) a known bug in -9.  Upgrade to -10.

> What are the minimum packages necessary to run X under potato (or in general)?

xfree86-common
xlib6g
xbase-clients
xserver-common
xserver-(svga, s3v, mach64, ? -- depends on your video card)
xfonts-base
xfonts-75dpi (depending on your X clients you *might* be able to scrape by
without this one)

You will probably want a window manager and a terminal emulator as well.

Read the extended description of xfree86-common as well.

-- 
G. Branden Robinson  |   I just wanted to see what it looked like
Debian GNU/Linux |   in a spotlight.
[EMAIL PROTECTED]   |   -- Jim Morrison
cartoon.ecn.purdue.edu/~branden/ |


pgpSJGnzB8b93.pgp
Description: PGP signature


Re: minimum X packages?

1999-02-08 Thread MallarJ
In a message dated 2/8/99 1:13:54 PM Central Standard Time,
[EMAIL PROTECTED] writes:

> I'd like to know the answer to the question: "What is a minimal set 
>  of packages necessary to run X?" 
>  

I'd say (for hamm) xbase, xserver-svga (or other depending on your card),
xserver-vga16, and xfnts75 at minimum...


Re: minimum X packages?

1999-02-08 Thread David B. Teague
On Sun, 7 Feb 1999, Daniel Martin wrote:

> Paul Nathan Puri <"<[EMAIL PROTECTED]>"@office.law-counsellor.com>
> writes: 
> >[...] What are the
> > minimum packages necessary to run X under potato (or in general)?

[snipped: useful answer by Daniel to the Potato X problem]

I'd like to know the answer to the question: "What is a minimal set 
of packages necessary to run X?" 

--David Teague [EMAIL PROTECTED]
Debian GNU/Linux Because software should not be *expected* to crash.



Re: minimum X packages?

1999-02-08 Thread Daniel Martin
Paul Nathan Puri <"<[EMAIL PROTECTED]>"@office.law-counsellor.com> writes:

> I recently upgraded to potato.
> 
> Now X starts and immediately dies.  Why would this be?  What are the
> minimum packages necessary to run X under potato (or in general)?

It would probably be because the X maintainer left a typo in
/etc/X11/Xsession that means X starts and immediately dies.

About lines 45-51 of /etx/X11/Xsession, change:

  fi
fi
  default)
;;
  *)
program=$(which $1)

to:

  fi
fi
;;
  default)
;;
  *)
program=$(which $1)

(notice the extra line with ;; in it).  Methinks the X maintainer was
releasing packages after having not slept sufficiently the night
before (at least, when I have errors like this in fvwm95 packages,
that's what the cause is).