From: "Littlefield, tyler" <compgeek13@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Trying out Slackware
Date: Sun, 24 Jun 2007 19:48:03 -0700 [thread overview]
Message-ID: <006c01c7b6d3$43fbd240$6c01a8c0@tdsportable> (raw)
In-Reply-To: <BAY141-DAV9430536F4DBA388C253DD8F140@phx.gbl>
Slackware is usually known for building everything from source. :)
That's what is usually done, then if you want, you can make packages for
future.
HTH,
----- Original Message -----
From: "Zachary Kline" <Z_kline@hotmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Sunday, June 24, 2007 7:43 PM
Subject: Trying out Slackware
> Hiya,
> Since I don't technically have an actual computer running Linux to
> speak of, in some ways I have an advantage. I'm able to try out new Linux
> distributions on the fly and as I become interested in them. Today I
> tried out Slackware 11.0, and I really like it so far. The only thing I
> have to get used to is the amount that comes preinstalled and the amount
> that isn't available. There are far fewer packages in the Slackware
> repositories than in, say, the Gentoo Portage system or Debian's package
> databases. But I don't know if this is a bad thing or not.
> That being said, could any of you Slackware veterans give me a tip or
> two? What is the method for installing stuff that isn't in the Slackware
> package lists? Do you compile from source, or make a Slackware package
> with makepkg?
> Thanks,
> Zack.
> PS: I love BSD init.
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
Zachary Kline
` Littlefield, tyler [this message]
` Doug Sutherland
` Gaijin
` Littlefield, tyler
` Adam Myrow
` Gaijin
` ace
` Deborah Norling
` Ralph W. Reid
` Steve Holmes
` ace
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='006c01c7b6d3$43fbd240$6c01a8c0@tdsportable' \
--to=compgeek13@gmail.com \
--cc=speakup@braille.uwo.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).