-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Yeap, that's right. Work has begun on a new Slackware Book to replace
Slackware Linux Essentials 2nd Edition. Very little details have been
released just yet. The new book is a complete rewrite from scratch with
nothing[0]. A license has not yet been determined. Likely the book
will be released under the GNU FDL or a BSD license, but Creative
Commons licenses have not been ruled out entirely yet.[1] Any major
updates will be announced here as well as on the book's website.

http://www.slackbook.org/

[0] Well, not quite nothing. I've discussed including at least one
chapter with simple updates with the author of those pieces due to the
new license.
[1] Honestly I haven't really looked into Creative Commons licenses as
the FDL or BSD license are well-known and seem to fit my needs well
enough.

- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAki0nlMACgkQrZS6hX/gvjpF2ACgkdRW7wMZkC8V5SSxeGFAZFja
itEAoI8/5QaLjRWtivIK3edAazotSDKU
=vpK2
-----END PGP SIGNATURE-----

+Alan Hicks+ <alan@lizella.network> trolled:

[pgp trash troll delete]

> Yeap, that's right. Work has begun on a new Slackware Book to
> replace Slackware Linux Essentials 2nd Edition. Very little
> details have been released just yet.

The last one has an excellent section on printing. Will the new
book's section on printing be just as good?

> The new book is a complete rewrite from scratch with nothing[0].
> A license has not yet been determined. Likely the book will be
> released under the GNU FDL or a BSD license, but Creative Commons
> licenses have not been ruled out entirely yet.[1] Any major
> updates will be announced here as well as on the book's website.

Double or single-ply? How many sheets to the roll?


cordially, even to hillbillies,

rm

+Alan Hicks+ wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Yeap, that's right. Work has begun on a new Slackware Book to replace
> Slackware Linux Essentials 2nd Edition. Very little details have been
> released just yet. The new book is a complete rewrite from scratch with
> nothing[0]. A license has not yet been determined. Likely the book
> will be released under the GNU FDL or a BSD license, but Creative
> Commons licenses have not been ruled out entirely yet.[1] Any major
> updates will be announced here as well as on the book's website.
>
> http://www.slackbook.org/
>
> [0] Well, not quite nothing. I've discussed including at least one
> chapter with simple updates with the author of those pieces due to the
> new license.
> [1] Honestly I haven't really looked into Creative Commons licenses as
> the FDL or BSD license are well-known and seem to fit my needs well
> enough.
>

Just my luck, I finally get around to ordering book 2 and now 3 is on
the way. I'm thinkin conspiracy here...*puts on tinfoil hat* :D
MikeinAK

+Alan Hicks+ <alan@lizella.netWORK> writes:

> Yeap, that's right. Work has begun on a new Slackware Book to replace
> Slackware Linux Essentials 2nd Edition. Very little details have been
> released just yet. The new book is a complete rewrite from scratch with
> nothing[0].

Really good news :-)

atb


Glyn
--
RTFM http://www.tldp.org/index.html
GAFC http://slackbook.org/ The Official Source :-)
STFW http://groups.google.com/groups?hl=e...inux.slackware
JFGI http://jfgi.us/

Glyn Millington <wistanswick@linuxmail.org> wrote:
> Alan Hicks <alan@lizella.netWORK> writes:
>> Yeap, that's right. Work has begun on a new Slackware Book to replace
>> Slackware Linux Essentials 2nd Edition. Very little details have been
>> released just yet. The new book is a complete rewrite from scratch with
>> nothing[0]. Any major updates will be announced here as well as on the
>> book's website http://www.slackbook.org/
>
> Really good news :-)

Ditto. Could I add a suggestion/request?...
Less general Unix info, e.g., chaps 16,17 about vi,emacs,
and much more info about Slackware-specific stuff, e.g., the
scripts in /etc/rc.d I've had to modify those to accommodate
stuff like http://linux-decnet.wiki.sourceforge.net/ (decnet
for linux), with no "official" information (besides comments in
the scripts, which are occasionally out-of-date, or out-of-sync,
with the actual code). Similarly, there's lots more /etc stuff
tailored for Slackware that's not documented in the book, and
for which an authoritative reference would be very valuable (for
me, anyway).
If you still want to write the non-Slackware-specific stuff
in chaps 8-17 (and scattered elsewheres), then that's great.
But make it a separate publication. I'd really like a book
dedicated to Slackware installation and configuration info,
without having to dig through a much larger book (containing
lots of general Unix info) to find what I'm looking for,
and then to sometimes not find it at all.
Meanwhile, thanks for all the great work.
--
John Forkosh ( mailto: j@f.com where j=john and f=forkosh )

On 2008-08-27, <rm@big.justlinux.ca> <rm@big.justlinux.ca> wrote:
>
>
> cordially, even to hillbillies,
>
> rm

ESADA

On 2008-08-27, JohnF <john@please.see.sig.for.email.com> wrote:
> Less general Unix info, e.g., chaps 16,17 about vi,emacs,
> and much more info about Slackware-specific stuff, e.g., the
> scripts in /etc/rc.d I've had to modify those to accommodate
> stuff like http://linux-decnet.wiki.sourceforge.net/ (decnet
> for linux), with no "official" information (besides comments in
> the scripts, which are occasionally out-of-date, or out-of-sync,
> with the actual code). Similarly, there's lots more /etc stuff
> tailored for Slackware that's not documented in the book, and
> for which an authoritative reference would be very valuable (for
> me, anyway).
> If you still want to write the non-Slackware-specific stuff
> in chaps 8-17 (and scattered elsewheres), then that's great.
> But make it a separate publication. I'd really like a book
> dedicated to Slackware installation and configuration info,
> without having to dig through a much larger book (containing
> lots of general Unix info) to find what I'm looking for,
> and then to sometimes not find it at all.

If I may, the point of The Book is to be one book for a relative
beginner to get started with Slackware. So it pretty much needs to
cover the non-Slackware specific parts of linux/UNIX or a newbie would
be pretty lost.

The book itself could be divided into "Slackware" and "Linux", though
that may not be an easy division to make.

Can you give specific examples of stuff in /etc that is tailored to
Slackware? From what I know of /etc it's pretty much *not* tailored to
Slackware; it's other distros that muck about with what files go where
in /etc. Okay, it's true that /etc/slackware-version is pretty
Slackware-specific. :)

--keith

--
kkeller-usenet@wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt
see X- headers for PGP signature information

On Wed, 27 Aug 2008 11:45:58 -0700, Keith Keller wrote:

> Can you give specific examples of stuff in /etc that is tailored to
> Slackware? From what I know of /etc it's pretty much *not* tailored to
> Slackware; it's other distros that muck about with what files go where
> in /etc.

Pretty much everything wireless-related is eccentr^H^H^H^H^H^H^H
characteristically Slackware. This will be hard to make clear in the
book because it isn't clear in /etc, and there are normally several
choices for where one can alter a given parameter.

I love Slackware but trying to solve wireless issues is almost always
more trouble than laying a run of Cat5....

> Okay, it's true that /etc/slackware-version is pretty
> Slackware-specific.

LOL. There are occasional other distros that pop up Slackware-specific
bits too, normally those that claim to have been built from scratch by
the creator.

Keith Keller wrote:

> Can you give specific examples of stuff in /etc that is tailored to
> Slackware?

The contents of /etc/rc.d are pretty Slackware-specific.

Let's see ... other files in /etc whose contents are in some way
specific to Slackware (despite that in some cases the files themselves,
or their locations aren't):

/etc/ld.so.conf
/etc/profile.d/coreutils-dircolors.csh
/etc/profile.d/coreutils-dircolors.sh
/etc/X11/xdm/Xsession
/etc/udev/rules.d/40-slackware.rules
/etc/udev/rules.d/65-permissions.rules
/etc/dialogrc
/etc/mail/sendmail.cf
/etc/inittab

Some of those might be a bit of a stretch ... Whether all this amounts
to a book is, of course, another question entirely.

--
----------------------------------------------------------------------
Sylvain Robitaille syl@alcor.concordia.ca

Network and Systems analyst Concordia University
Instructional & Information Technology Montreal, Quebec, Canada
----------------------------------------------------------------------

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2008-08-27, Keith Keller <kkeller-usenet@wombat.san-francisco.ca.us> wrote:
> If I may, the point of The Book is to be one book for a relative
> beginner to get started with Slackware. So it pretty much needs to
> cover the non-Slackware specific parts of linux/UNIX or a newbie would
> be pretty lost.

Keith's hit the nail on the head here. The book must be of use not
only to people new to Slackware, but to people new to Linux (and maybe
even new to computers all together). Leaving out things like vi and
emacs[0] would make the book very useless to them. "Open your text
editor." "What the hell's a text editor?"

> The book itself could be divided into "Slackware" and "Linux", though
> that may not be an easy division to make.

It's not. The book is being organized not to differentiate between
what's Slackware and what's generic, but rather to begin with what a
newbie most likely needs to know and work up to harder concepts.
Basically after the prelude we get to the installer, then booting (I
have no idea how many newbies messed up dual-boot stuff with the old
book, but I suspect it's a lot), basic shell stuff and bash, then onto
X, and printing. This should be all the newbie needs to know to get
his hardware setup correctly.[1] From there we go into basic sysadmin
stuff like managing users and groups, filesystem permissions, mounting,
vi, emacs, etc. Some of this will be touched on earlier in a simpler
manner of course, with references to these chapters.

After that we'll discuss networking (including wireless) and basic
networking commands. We round it out with pkgtool, keeping up with
- -stable, and compiling a kernel (as well as when to do so and when NOT
to do so). Somewhere in here I need to discuss using the generic
kernel and mkinitrd. I considered putting that in the Installation
chapter, or perhaps Booting, but felt that would be too intimidating to
a new user.

[0] Ok yeah, real Slackers don't use emacs. ;^)
[1] Mental note: Add chapter for help and something on audio. If
anyone could give me an idea of where to work in alsa* I would
appreciate it. I suppose it might best fit with a multimedia chapter,
but I don't have anything planned there.

- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAki1uWMACgkQrZS6hX/gvjr7cwCgml5WjHzTewKr0cY1lbk2vTcr
KkYAnj7yM3GJQq0G1XLUpiLas38DSRqD
=nGFM
-----END PGP SIGNATURE-----