From: ichi@ihug.co.nz
To: linux-newbie <linux-newbie@vger.kernel.org>
Subject: Re: XFree86 crash log
Date: Thu, 14 Nov 2002 13:14:04 +0000 [thread overview]
Message-ID: <3DD3A19C.7E0838B3@ihug.co.nz> (raw)
In-Reply-To: 5.1.0.14.1.20021112183621.02114990@celine
Ray Olszewski wrote:
>
> 4. Does your kernel support Unix domain sockets?
> If you are using any stock Slackware kernel, it probably
> supports Unix sockets.
James was using the stock lowmem.i kernel from Slackware.
-------------------------------
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
# CONFIG_NETLINK_DEV is not set
# CONFIG_NETFILTER is not set
# CONFIG_FILTER is not set
CONFIG_UNIX=y
# CONFIG_INET is not set
--------------------------------
> If you are using one from BasicLinux ... well, the BasicLinux
> home page says it supports X installs, so I suppose the kernel
> includes what is needed
BasicLinux uses a stock Slackware kernel (bare.i).
> 5. BasicLinux has a page that lists the Slackware packages
> needed to run X. Did you include everything this page says
> to install?
Sorry for the confusion. BasicLinux is not the problem. James
is running pure, unadulterated Slackware 8.1. Yes, it is a
mini-installation (26mb of HD space) -- but it's 100% Slackware.
The confusion arises because the author of BasicLinux (who is
a strong supporter of using Linux on old PCs) produced a special
installation routine to enable old PCs to install Slackware 8.1.
The normal installation routine for Slackware 8.1 requires 16mb
RAM. The special installation routine runs happily on a system
with 4mb RAM and 80mb HD.
-------------------------------------------
http://www.volny.cz/basiclinux/slack81.html
-------------------------------------------
Although this installation package for Slackware 8.1 is stored
at the BasicLinux site, it is quite different from BasicLinux.
Cheers,
Steven
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2002-11-14 13:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-13 2:23 XFree86 crash log james miller
2002-11-13 3:02 ` Ray Olszewski
2002-11-14 13:14 ` ichi [this message]
2002-11-13 16:28 ` ichi
2002-11-13 5:04 ` James Miller
2002-11-13 19:23 ` more X problems James Miller
2002-11-13 19:33 ` hackob
2002-11-13 20:29 ` James Miller
2002-11-13 21:07 ` hackob
[not found] ` <Pine.LNX.4.44.0211131425440.21708-100000@localhost.localdo main>
2002-11-13 21:00 ` Ray Olszewski
2002-11-13 21:37 ` James Miller
2002-11-14 12:22 ` ichi
2002-11-14 1:34 ` James Miller
[not found] ` <Pine.LNX.4.44.0211131911530.21708-100000@localhost.localdo main>
2002-11-14 1:39 ` Ray Olszewski
2002-11-14 2:41 ` James Miller
2002-11-14 16:23 ` ichi
2002-11-14 16:49 ` ichi
2002-11-14 4:36 ` James Miller
[not found] ` <Pine.LNX.4.44.0211131215130.21708-100000@localhost.localdo main>
2002-11-13 20:13 ` Ray Olszewski
2002-11-13 20:55 ` James Miller
2002-11-14 2:13 ` XFree86 crash log Peter
2002-11-14 2:45 ` James Miller
2002-11-15 0:53 ` Peter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3DD3A19C.7E0838B3@ihug.co.nz \
--to=ichi@ihug.co.nz \
--cc=linux-newbie@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox