LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   So you want to be a Slacker! What do I do next? (https://www.linuxquestions.org/questions/slackware-14/so-you-want-to-be-a-slacker-what-do-i-do-next-644746/)

onebuck 05-25-2008 11:03 PM

So you want to be a Slacker! What do I do next?
 
Hi,

Welcome to SlackwareŽ and the SlackwareŽ LQ Forum!

Edit2: 10-19-09 so READ on! My last edit to the original post was on 12-08-08 as I belief the continuity of the thread should be fluid without edits other than to correct major mistakes.

SlackwareŽ 13 which supports x86_32 & x86_64 has been released. You can utilize a lot of the information contained within this sticky that relates to SlackwareŽ in general and the releases for SlackwareŽ 12, 12.1, 12.2, 13. The later posts do have information for SlackwareŽ 13 x86_32 & x86_64. HTH! /edit2 end/

SlackwareŽ 12.1 distribution is available at the SlackwareŽ store. By purchasing the distribution through the store you will be supporting SlackwareŽ directly therefore insuring the continuance of the best Linux distribution.

If You don't purchase SlackwareŽ 12.1 at this time then you will first need to download the SlackwareŽ 12.1 Distribution via a SlackwareŽ 12.1 official mirror or 'Official List of Mirrors'. Be sure to get the '.md5' file(s) for your iso(s). For a M$ user you can use 'WGET for Windows (win32)' or bittorent;

Quote:

Torrents for 12.1

Slackware 12.1 Install ISO disc 1 (A/AP/D/E/L/N, installers, kernels, Slackbook)
Slackware 12.1 Install ISO disc 2 (F/K/T/TCL/X/XAP/Y, L source)
Slackware 12.1 Install ISO disc 3 (KDE/KDEI)
Slackware 12.1 ISO disc 4 (A/AP/D/E/F/installer source, extra/, pasture/, patches/, testing/)
Slackware 12.1 ISO disc 5 (K/KDE/KDEI source)
Slackware 12.1 ISO disc 6 (N/T/TCL/X/XAP/Y source)

Slackware 12.1 DVD ISO (everything)
Please note the cd contents above. You will need cd1,cd2 and cd3(KDE/KDEI) for a installation or download the dvd for everything with any form of download for a installation, either by ftp, bittorrent or other download means. You may need cd4 if you plan to use anything within /extra.

Note: I will be presenting a cd/dvd installation at this time. But note that you can do a network installation if so desired then look here or etherboot.

Once You get the iso downloaded then you should do a md5sum check on the downloaded iso(s) image(s). This can be done using a M$ Windows application such as 'md5sum.exe' to check the md5sum. Or for Linux from the cli you would do;
Code:

~#cd /downloadisolocation      #cdromiso.iso cdromiso.md5

~#md5sum -c cdromiso.md5      #substitute the correct name to check

Once you are sure that everything is OK then you can burn the 'ISO IMAGE' to your selected media. Please note that some users must burn the iso image at a slower speed to insure a good burn. By slowing the burn speed you may insure that a good copy will be created if the image is indeed valid.

Once the image has been burned to the media then a 'CdromMd5sumsAfterBurning' check would be advised. Your burn application can fail so a check of the final media would prevent you from some possible headaches.

Patience!

Don't be in a rush to boot the SlackwareŽ install cd/dvd. I would suggest that you first read the documentation that PV has provided; Announce 12.1, Slackware-Howto, CHANGES_AND_HINTS.TXT, UPGRADE.TXT. Plus the other text files relevant to your needs. All the text files are available on your install cd/dvd.

The above text files have valuable information for you that will aid in the SlackwareŽ installation. You will be presented with information that may prevent you from falling into some pit falls that a lot of new users have fell into. If they had just read the text information file(s) before the install then no ones time would have been wasted.

I have read more than enough threads where a user failed to read the referenced text files because of the M$ mindset that the 'README' type files don't contain pertinent information. SlackwareŽ Linux does require one to be able to READ and investigate in order to complete tasks on or within the system.

Now that the text rant is out of the way then let us get that new SlackwareŽ install going. You should have your BIOS boot order setup so as the 'CD/DVD' is the first order of the BOOT sequence. Place the SlackwareŽ 12.1 install cd1/DVD in your drive. Reboot the machine. You should get the SlackwareŽ boot screen.

Reference: the Slackware 12.1 Howto 3.2 Booting the Slackware CD-ROM;

At this boot screen you will see the 'boot:' line. You will also get booting information along with some prompt information. It is here that you will input a different kernel if you need one along with kernel parameters. The desired information for 'YOUR' install will depend on the hardware that you are installing too. The before mentioned text files will dictate to you as to what should be passed to the install kernels. If you want to use the default kernel and not pass any parameters then just press return at the boot prompt.

Note: Remember that the SlackwareŽ 12.1 install cd1/dvd are bootable and can be used to recover from errors with your install/filesystem errors.

If you anticipate 'acpi' with your equipment then pass the parameter 'apci=off'. If 'apic' then pass 'noapic' to the kernel.

If you have or expect a hdd/sata device probe problem then pass the 'hdn=noprobe' where n=a,b,c,d.

Other possible parameters are nolapic noioapic, you can google or search LQ for any possible parameters that you may need for your specific equipment. Or you could look at 'Linux Kernel Parameters' for a good list of kernel parameters.

Quote:


ACPI = Advanced Configuration and Power Interface

ACPI is the system that controls your dynamic speed fans, the power button behavior, sleep states, other configuration states.

APIC = Advanced Programmable Interrupt Controllers

APIC is the replacement for the old PIC chip that was embedded on motherboards that allowed you to setup interrupts for your soundcard, ide controllers and other subsystems.
Example:

boot: hugesmp.s append = "acpi=off noapic hda=noprobe"<Enter/Return>

Please see 'CHANGES_AND_HINTS.TXT'

Why re-invent the wheel. Please read the files that PV and the SlackwareŽ team have provided. If you read the SlackwareŽ 12.1 Howto and follow the steps you should create a good SlackwareŽ 12.1 installation.

Reference: the Slackware 12.1 Howto Along with the; Announce 12.1, Slackware-Howto, CHANGES_AND_HINTS.TXT, UPGRADE.TXT.

The below reference is abbreviated and can be used as a simple guideline/flowchart to give you an example of a installation. That is why I suggest that you print the 'SlackwareŽ 12.1 Howto'.

Code:

abbreviated so please see Slackware 12.1 Howto for complete information.

3.3  Using Linux fdisk to create Linux partitions

4.0  Installing the Slackware distribution using setup.

4.1 The ADDSWAP option:

4.2 The TARGET option:

4.3 The SOURCE option:

4.4 The SELECT option:

The SELECT option lets you select software to install.

4.5 The INSTALL option:

This option actually installs the selected packages to the hard drive.

4.6 The CONFIGURE option:

The setup's CONFIGURE option does the basic configuration your system needs, such as
setting up your mouse, setting your timezone, and more.

4.7 LILO

LILO is the Linux Loader, a program that allows you to boot Linux (and other operating
systems) directly from your hard drive.  If you installed the LILO package, you now have
an opportunity to set it up.

4.8 Networking

Another configuration menu allows you to configure your machine's networking setup.  First,
enter a hostname for your machine. The default hostname after installation is "darkstar,"
but you can enter any name you like.  Next, you'll be asked to provide a domain name. If
you're running a stand-alone machine (possibly using a dialup link to an Internet Service
Provider) then you can pick any name you like. The default domain name is
"example.net".  If you are going to add the machine to a local network, you'll need to use
the same domain name as the rest of the machines on your network.  If you're not sure
what this is, contact your network administrator for help.  Once you've specified the
hostname and domain name, you'll be asked which type of setup you would like: "static IP",
"DHCP", or "loopback".

5. Booting the installed Slackware system

If you've installed LILO, make sure you don't have a disk in your floppy drive -- when
your machine reboots it should start LILO. Otherwise, insert the bootdisk made for your
system during the configuration process and use it to boot.  Also, make sure to remove
the CD-ROM to avoid booting it, or disable your machine's
CD-ROM booting feature in the BIOS settings.

The kernel will go through the startup process, detecting your hardware, checking your
partitions and starting various processes. Eventually you'll be
given a login prompt:

darkstar login:

Log into the new system as "root".

6. Post-installation configuration
Once the system is running, most of the work is complete. However, there are still a few
programs you'll need to configure. We'll cover the most important in this section.

6.1 /etc/rc.d/rc.modules

This file contains a list of Linux kernel modules.
A kernel module is like a device driver under DOS. You can think
of the /etc/rc.d/rc.modules file as similar to DOS's CONFIG.SYS.
The file specifies which modules the system needs to load to
support the machine's hardware.  After booting your machine, you
may find that some of your hardware isn't detected (usually an
Ethernet card). To provide the support, you'll need to load the
correct kernel module. Note that modern Linux kernels include a
feature that allows the kernel to load its own modules, called
udev. This will load many modules automatically without any need
to edit rc.modules, and when using udev it might be better to
tell it how to load the modules you want automatically rather
than loading them at boot time with rc.modules. This is an
advanced topic, and outside the scope of this document. If
you're interested in this, "man udev" is a good place to start
reading.

In any case, it's best to not edit rc.modules unless you find
that the modules you want to use are not being loaded
automatically by udev.  You can see a list of the modules that
were loaded with the "lsmod" command.  Likewise, in the majority
of cases "alsaconf" is not required to configure sound.

Rather, the "alsamixer" tool is used to unmute the Master and
PCM channels and turn up the volume, and the "alsactl store" is
used to save the sound defaults.

6.2 Configuring the X Window System

Configuring X can be a complex task.

xorgsetup
---------

This is a simple menu driven frontend that's similar in feel to
the Slackware installer.

xorgconfig
----------

This is a text-based X configuration program that's designed for
the advanced system administrator.

xorgconfig

This will present a screen full of information about xorgconfig.
To continue, press enter.

6.3 Hardware acceleration with X

If you've used xorgsetup or xorgconfig to configure for your
card, and it's one that can take advantage of X's direct
rendering support, you'll certainly want to enable this.

6.4 User Accounts

You should make a user account for yourself.  Using "root" as
your everyday account is dangerous, and is considered bad form
(at the very least) since you can accidentally damage your
system if you mistype a command.  If you're logged in as a
normal user, the effects of bad commands will be much more
limited.  Normally you'll only log in as root to perform system
administration tasks, such as setting or changing the root
password, installing, configuring, or removing system software,
and creating or deleting user accounts.

To make an account for yourself, use the 'adduser' program.
To start it, type 'adduser' at a prompt and follow the
instructions.  Going with the default selections for user ID,
group ID, and shell should be just fine for most users.
You'll want to add your user to the cdrom, audio, video plugdev
(plugable devices like USB cameras and flash memory) and scanner
groups if you have a computer with multimedia peripherals and
want to be able to access these.  Add these group names, comma
separated, at the following prompt: cdrom, audio, video,
plugdev, lp

Note: plugdev, audio and lp are gotchas' for a lot of newbies. Make sure
to add your users to the right groups. You can use the up-arrow
to see the suggested groups.

7. For more information

For more information, visit our web site at http://www.slackware.com

To shop for fine Slackware products (and help keep the project funded),
please visit http://store.slackware.com.  :-)

        Email: info@slackware.com          (Information or general inquiries)
        FTP:  ftp://ftp.slackware.com    (Updates)
        WWW:  http://www.slackware.com    (News)
        Security issues:  security@slackware.com
        General Hotline:  volkerdi@slackware.com

8. Trademarks

Slackware is a registered trademark of Slackware Linux, Inc.
Linux is a Registered Trademark of Linus Torvalds.
All trademarks are property of their respective owners.

Please read the files that PV and the SlackwareŽ team have provided.

I would suggest that new users at least print out the Slackware 12.1 Howto.

If you are experiencing network headaches (wired or wireless) then I suggest that you look at Alien_Bob's 'Configuring your network in Slackware'. This should help you setup a network that is functional.

These links and others can be found at 'Slackware-Links' .
More than just SlackwareŽ links!

Happy Slacking!

Neither this post nor I (Onebuck) officially represent SlackwareŽ in any way.

shadowsnipes 05-26-2008 12:34 AM

Haha the title of this reminds me of the old Sierra QFG game (Quest for Glory I: So you want to be a Hero).

I didn't read this all of this post, but I skimmed through it enough to get that the main gist is to encourage new Slackware users to read the docs and give them a warm welcome. Sounds like good sticky material. Nice post :)

onebuck 05-26-2008 09:54 AM

Hi,
Quote:

Originally Posted by shadowsnipes (Post 3164610)
Haha the title of this reminds me of the old Sierra QFG game (Quest for Glory I: So you want to be a Hero).

I didn't read this all of this post, but I skimmed through it enough to get that the main gist is to encourage new Slackware users to read the docs and give them a warm welcome. Sounds like good sticky material. Nice post :)

That's my intent! I would like to provide a means for a new user to get some general information. Plus to encourage the new user too READ the available SlackwareŽ documentation.

I know that documentation can be overwhelming but it is good for the user to acquaint themselves to the information. That way at some point the user will be able to use that same information to install/maintain their SlackwareŽ system.

Happy Slacking!

onebuck 05-28-2008 01:46 PM

Hi,

I think I'll turn this into a wiki so as to provide a complete set of information instead of abbreviated.

alan_ri 05-28-2008 02:09 PM

Hi!
That's a really nice thing that you're doing onebuck and I think that it would be good if this thread becomes sticky rather then you turn it into wiki.I suggest adding some info about configuration of sound,grafic,mouse,network and package building and managment.That way I think it would be a good guide for Slackware newbies before they start to read official documentation.
All the best.

onebuck 05-28-2008 09:15 PM

Hi,

I'll think about it. Thanks for your input.

shadowsnipes 05-30-2008 03:51 PM

One advantage for it to be a thread instead of a wiki is that parts of it will be included in the standard LQ search results. That's why I chose to put my "HowTo: Upgrade Slackware 12.0 to 12.1" in a thread instead of a wiki.

Cuetzpallin 05-30-2008 06:56 PM

Any way this is a good post, I think must be a Wiki too.
So, we can participate writing our experience installing a configuring our slackboxes.

Enjoy Slack

bgeddy 05-30-2008 07:13 PM

Yeah - nice on onebuck.

My vote is for a sticky - searchability and ease of access (information being in one place) being a deciding factor for me when it comes to sticky/wiki.

This along with shadowsnipes' excellent http://www.linuxquestions.org/questi...o-12.1-640473/

goes to show how helpful experienced Slackware users are.

Sorry if I've missed someone's good work but these two recent efforts came to mind.

Maybe a sticky of topic sorted links to these and similar posts ?

Edit: Just thinking of this gave me a few suggestions to the new Slackware user...

1. A lot can be learned by looking through /etc and /etc/rc.d directories. Midnight commander (mc from a terminal) gives a nice cli based file system browser. Navigating through /etc /etc/rc.d /usr/doc with mc and reading confs and scripts gives a wonderful insight as to how Slackware and Linux in general works.

2. (realated to (1)) do spend time with the command line. Without wishing to reiterate links advanced bash scripting http://tldp.org/LDP/abs/html/ is an excellent reference.

3. Use the forum search tools when researching a problem.

4. Although IRC has a bad reputation - there is some excellent knowledge to be gleaned by just lurking (passively observing) the conversations on Freenode ##slackware and OFTC #slackware channels. Some of the "Slackware greats" regularly contribute.

5. Learn up on how Slackbuilds and Slackware package management,(yes - it does exist !!), work.

6. Check out your /var/log directory and it's contents.

7. Keep in touch with LQ and don't be scared to ask when in doubt !! This community is without doubt the most helpful I have come across in my 20 odd years of IT experience.

8. There are a lot of useful podcasts available to the linux user. These are free audio recordings a link to some is http://www.thelinuxlink.net/. I would personally recommend an unfortunately discontinued cast - Linux Reality - by Chess Griffin - a Slackware user and contributor here. The previous casts are all good and I hope still available.

9. Give something back - if you see a question asked which you know the answer or can at least help with then do so !

10. Try and use Slackware (or just Linux) for everything. I.e. don't boot to Windows unless absolutely neccesary. OK, sometimes it is, but using Linux in earnest for any length of time will certainly help climb the learning curve.

Have fun !!

unSpawn 05-30-2008 07:39 PM

Stickied this post, I have.

H_TeXMeX_H 05-31-2008 03:39 PM

That's a good post onebuck, I'm sure it'll save a lot of people the trouble of starting a new thread on here that's been started on here many times before. Guess that's what stickies are for.

onebuck 05-31-2008 07:52 PM

Hi,

Thanks H!
I'm hoping others will contribute. Much in the way 'bgeddy' contributed. That way the thread will really be useful to everyone.

pdw_hu 06-01-2008 07:42 AM

Quote:

Originally Posted by H_TeXMeX_H (Post 3170574)
That's a good post onebuck, I'm sure it'll save a lot of people the trouble of starting a new thread on here that's been started on here many times before. Guess that's what stickies are for.

Like stickies ever kept anyone from asking it again and again ;)

(/me is evil :P)

xokaido 06-01-2008 01:29 PM

Yesterday I've posted about installing SLACKWARE on Virtual Machine...
I had got some answers and now see that posts have been deleted...
I've got some kind of problem now:
I have done all well, partitions have been setted up well,
installation began and when I was asked to insert another
disk I've found that all the nessecary options in virtual machine are disabled...
I can't choose another ISO image to boot from that...
Clicking on the "Continue" buton on Slack does not work..
I can't even choose to boot from CD or DVD...
Again, I'm sitting on Debian and I use VMware as virtual machine...
Could anyone help?..
Thanks...

T3slider 06-01-2008 02:01 PM

Quote:

Originally Posted by xokaido
Yesterday I've posted about installing SLACKWARE on Virtual Machine...
I had got some answers and now see that posts have been deleted...

That probably should have been a hint to make a new thread instead of hijacking this one...

XavierP 06-01-2008 02:06 PM

xokaido - I refer you to this post on your own thread: http://www.linuxquestions.org/questi...68#post3170968

Please do not hijack a thread to ask your own, unrelated question. Your own thread is getting responses, you now need to try out the suggestions and post back to your own thread with the results or with further questions.

shadowsnipes 06-02-2008 09:47 AM

Onebuck,

could you underline/bold the audio group under the section for adding users to groups. Like plugdev, it is a group that newbies seem to miss a lot. It is especially confusing for users who see it working in runlevel 3 (because of the CONSOLE_GROUPS in /etc/login.defs), but don't see it working in runlevel 4.

Also, you might want to add the lp group to that list since udev now uses it in Slackware 12.1 for printing.

onebuck 06-03-2008 12:19 PM

Hi,

Done!

onebuck 06-05-2008 08:08 PM

Hi,

Daedra
's, post for 'Beautiful Fonts in 12.1' is a post that everyone should look at. Good reference!

The 'The Perfect Desktop - Slackware 12' is a good install example that may assist in the installing of SlackwareŽ 12.1.

I have listed these links in 'Slackware-Links'. More than just SlackwareŽ links!

SCerovec 06-18-2008 04:05 AM

This is a must-read post so I will probably add it to mi sig ;-)

All i can think of is
Code:

links
for it's ability to cruise over the filesystem with the four arrow keys ;-)

I also enable this on mc by default (LYNKS like motion in [F9]->Options->Configuration )

my 2cents...

anupamsr 07-03-2008 07:06 AM

I have downloaded the Slackware 12.1 DVD. Is there a way to install it without burning it?

Bruce Hill 07-03-2008 07:11 AM

Yes. When you install Slackware, the setup utility asks for the source:
Code:

SOURCE displays a menu offering the choice of installation from CD-ROM, a
hard drive partition, NFS, HTTP/FTP, or a directory (mounted manually).


anupamsr 07-03-2008 07:18 AM

No! Sorry for not being clear.
I have Gentoo installed (and I have a live CD also). I have downloaded Slackware DVD on a partition and I want to install it over Gentoo. The question that I have is, is there a way to get to the setup program without booting into Slackware?

Alien Bob 07-03-2008 07:56 AM

You can install Slackware using an existing patrtition with all the packages if you do not want to burn a DVD.
But you still need to boot into the installer. You can use the USB installer image that fits on a stick to boot, or setup a PXE server.
You can not start the setup from within Gentoo or any other distro.

Eric

shadowsnipes 07-03-2008 11:16 AM

if you downloaded an iso image instead of files for the dvd then you will have to mount it as a loop device so you can access the files.

anupamsr 07-03-2008 12:28 PM

Hi! I solved my problem by using they USB image, which had huge26.s kernel. After that I mounted the ISO as loop and installed Slackware 12.1 flawlessly.

onebuck 07-16-2008 09:59 PM

Hi,

Daedra & Dugan have done some great work for Beautiful fonts within Slackware 12.1. I also must point out the contributions by other posters within the thread. This is how it's supposed to work within a forum.

This is a must read thread for anyone who wants a beautiful font(s) for the Slackware 12.1. A lot of the work is already done for you!

onebuck 12-11-2008 07:11 AM

Hi,

'SlackwareŽ 12.2 Release Announcement'!

You can now download SlackwareŽ 12.2 from several mirrors. I suggest that you look at using the SlackwareŽ 12.2 torrents. Please seed as long as you can, this will help all.

I have included new 'SlackwareŽ 12.2' links in 'Slackware-Links'. More than just SlackwareŽ links!

Goto the 'SlackwareŽ store' now to order SlackwareŽ 12.2. Please be patient as the release has just been made.

EDIT: Be sure to check the md5sum. If you downloaded the dvd iso then be sure to check the md5sum for the original iso. From the cli;

Code:

~#cd /downloadisolocation      #dvdiso.iso dvdiso.md5

~#md5sum -c dvdiso.md5      #substitute the correct name to check

If the iso md5 is ok then you should try 'CdromMd5sumsAfterBurning''.

This way you will know if the burn was OK! This will check the download iso with the known md5sum that you also get with the iso.

Happy Slacking! :)

onebuck 12-29-2008 06:57 AM

Hi,

Now that the dust is settling!

A lot of new SlackwareŽ users are having difficulty with network setup(s). I would suggest that they look at Alien_Bob's 'Configuring your network in SlackwareŽ'. "This article is intended as a reference guide to network card configuration in SlackwareŽ." A very useful wiki!

These links and others can be found at 'Slackware-Links'. More than just SlackwareŽ links!

Gaskilla 01-11-2009 05:42 PM

I have a question.
 
I installed slackware 12.2...etc.

I log in as root and everything is fine.
I run the set command and it returns the standard info.
However there is no profile for root in the root directory.
Where does it get all the info returned in the set command?

Thanks,
MikeG

Alien Bob 01-11-2009 05:45 PM

Quote:

Originally Posted by Gaskilla (Post 3404955)
Where does it get all the info returned in the set command?

From the /etc/profile.d/ directory...

Eric

dywanik 04-13-2009 12:28 PM

Hi all! That's my first post on the forum and I have a small advice for new and maybe old slackers. If you ever want to clean your system a bit and you're using KPackage than please be VERY cautious since it does NOT inform you whether the package you're about to remove is "REQUIRED" or not and you don't want to kill your system like I did...

onebuck 04-13-2009 03:34 PM

Hi,
Quote:

Originally Posted by dywanik (Post 3507534)
Hi all! That's my first post on the forum and I have a small advice for new and maybe old slackers. If you ever want to clean your system a bit and you're using KPackage than please be VERY cautious since it does NOT inform you whether the package you're about to remove is "REQUIRED" or not and you don't want to kill your system like I did...

What problems did you experience? I would never manage my systems with a kde manager of any sort. I use pkgtool as my basic manager. Several others but always fall back on pkgtool. Always from the cli, GUI can get you into trouble if you don't understand their actions or transparency by the author.

Most experienced users are not going to use something that is not open and solid for maintenance of their system. As for any package manager the user must be fully aware of what they are doing. Your problem with dependency is just that you aren't fully aware of your system therefore to remove something without knowing what to remove. This is Slackware and not dependency 'Hell' as is for the *buntus or the like.

BTW, what did you remove that crippled your Slackware system?

dywanik 04-13-2009 03:44 PM

Quote:

Originally Posted by onebuck (Post 3507692)
BTW, what did you remove that crippled your Slackware system?

I believe one of the things was nano (but there were more, however, what I deleted was only sth like multimedia or games-related). What happened was that after typing my login... nothing happened. Neither error nor pass prompt. So I just reinstalled the system (since it was fresh installation). Now I'm more cautious. ;-)

onebuck 04-13-2009 04:55 PM

Hi,

I suggest that you look at 'Slackware Builds, Packages & Scripts' section of 'Slackware-Links'. More than just SlackwareŽ links! Especially the subsection 'Package Management:' which has the 'Overview of SlackwareŽ Package Management'.

The 'Minimal System' would be a good place to look for a method as to what packages to install for a minimal Slackware system.

The list has loads of Slackware links along with other useful links. Take a gander.

01micko 05-19-2009 04:01 AM

G'day

Maybe I wanna be a slacker, BarryK creator of Puppy got me curious with his "Woof" build system. I am a Puppy devotee ATM. But that is another story. :P

Initial Feedback: Posting from 12.2 currently. installation is 1 hour old. I've mainly only used Puppy and Mandriva (and Mandrake), so they are my benchmarks. I had a little problem with my monitor, an Asus VW161D, running an asus A7s8X mobo (athlon2100+) and a raedon 9200. No support for my res ootb, 1380x768. Also wireless is a bit tricky, I can do it from a prompt but I tried the gui tools in KDE. (what? No info? What module am I using?) Hmmmm... Even Mandriva's network tool tells me the module (rt73usb) and Puppy's Network Wizard is better still. Yes, I can hear it now, "Slackware isn't meant to be easy".. but it could be a little more intuitive. Anyway, I'll persevere. :) It's somehow likeable.

Cheers

onebuck 05-19-2009 01:20 PM

Hi,

Welcome to Slackware!

Most system level configurations should be done from the cli as root. I would not rely on KDE.

For you network setup take a look at 'Configuring your network in Slackware' Alien_Bob's excellent article on the way network cards are configured in Slackware.

This link and others are available from 'Slackware-Links'. More than just SlackwareŽ links!

01micko 05-19-2009 06:43 PM

Hi there,

Thanks onebuck for those links. I shall be looking in to those.

See you around;)

onebuck 05-25-2009 08:05 PM

Hi,

This post is from 'SlackwareŽ64 it's about time!'. I'm including a copy here for reference;
Quote:

Hi,

I'm away and doing things here on the farm. Those darn SlackwareŽ team guys slipped SlackwareŽ64 out. :)

WOW!

Thanks!

I've added a torrent link (SlackwareŽ64 Torrent) to the 'Slackware-Links'. More than just SlackwareŽ links!

BTW, don't forget to check that hash!

EDIT: additional information;

samac link for;

Alien_Bob's mirror-slackware-current.sh script works to download it if you modify this line SLACKRELEASE="slackware-${RELEASE}" by adding a 64 like this SLACKRELEASE="slackware64-${RELEASE}"
<- Alien_Bob's reply as to how it should be done

Alien_Bob's helpful nvidia and text issue response.

manwichmakesameal 'link for edit of' mirror-slackware-current.sh. <- samac's reply

SlackwareŽ64 -current iso
+ README.TXT <- As it says!

vonbiber 05-27-2009 04:18 AM

profile
 
@MikeG
>I installed slackware 12.2...etc.
>
>I log in as root and everything is fine.
>I run the set command and it returns the standard info.
>However there is no profile for root in the root directory.
>Where does it get all the info returned in the set command?

slackware uses the /etc/profile
if you want to change some settings for some users you have
to create a .bash_profile in your users home directories
and store there whatever you need to set differently (PS1, ...)

onebuck 05-27-2009 07:36 AM

Hi,

Quote:

Originally Posted by vonbiber (Post 3554126)
@MikeG
>I installed slackware 12.2...etc.
>
>I log in as root and everything is fine.
>I run the set command and it returns the standard info.
>However there is no profile for root in the root directory.
>Where does it get all the info returned in the set command?

slackware uses the /etc/profile
if you want to change some settings for some users you have
to create a .bash_profile in your users home directories
and store there whatever you need to set differently (PS1, ...)

Or you can create a .bashrc along with the .bash_profile for the user within their home.

BTW, it would be better if you use the 'Quote vbcode tag' instead of a indirect quote. That way the post would not be broken. Meaning to see the original (in-bed link) that you are responding too then one doesn't need to scroll back through the thread to find the complete post.

Notice the link reference after your name.

onebuck 06-02-2009 05:17 PM

Hi,

********************************************
* Remember 'Slackware64 -current' is testing not stable.*
********************************************

If you are wanting to get 'Slackware64 -current' then I suggest that you get Alien_Bob's-script;
'mirror-slackware-current.sh'. This script will give you the means to create your iso from '-current'.

You will need to edit the script. It is well documented so you can setup to create your iso. Be sure to setup your targets. Select DVD as that will be the best and the easiest for you. Mirror selection can be from any of the ones from the embedded list or another mirror of choice.

Be patient when you start the script because this will take awhile to get the files, check the hash then create the iso. Be sure to have the space available to store everything. If you want/need updates then just restart the script.

onebuck 07-02-2009 08:22 AM

Hi,

If you are wanting to get the iso RC1 for 'Slackware64 -current' then I suggest that you get Alien_Bob's-script;
'mirror-slackware-current.sh'. This script will give you the means to create your iso from '-current'.

No need to reach out to another site for a possible erroneous generated ISO image. The ISO is sum checked for you but be sure to check the burn media by ''CdromMd5sumsAfterBurning''

This way you will know that your burn is OK!

These links and others can be found at 'Slackware-Links'. More than just SlackwareŽ links!

onebuck 07-04-2009 08:49 AM

Hi,

For those that are having problems getting RC1 using 'mirror-slackware-current.sh'.

You can edit the script and select another mirror. Try it! You'll like it.

Quote:

excerpt from 'mirror-slackware-current.sh';
#
# Examples of use:
# + Show all available options: "mirror-slackware-current.sh -h"
# + A crontab entry which checks for updates every night at 06:00, downloads
# new stuff if present and creates a new DVD ISO (if updates were found):
# 00 6 * * * /usr/local/bin/mirror-slackware-current.sh -q -o DVD
#
#
#
# - Check at our master rsync site if the ChangeLog.txt has been altered
# - If no changes, then no further actions are needed (abort script)
# - If ChangeLog.txt has changed since our last mirror, do the following:
# - Mirror the slackware release tree
# - Create a set of 3 CDROM ISO images
# or a single bootable DVD from the current tree,
# (guidelines are in the ./isolinux/README.TXT)
# CDROM ISO images must be at most 737.280.000 bytes (703 MB)
# in order to fit on a 80min CD medium.
# A typical DVD max size is 4.706.074.624 bytes (4.38GB better known as 4.7G)
#
#
# Good rsync mirrors are:

#
# slackware.mirrors.tds.net::slackware/slackware-current
# rsync.osuosl.org::slackware/slackware-current
# rsync.slackware.pl::slackware/slackware-current
# rsync.slackware.at::slackware/slackware-current
# mirrors.vbi.vt.edu::slackware/slackware-current
# rsync.slackware.no::slackware/slackware-current
# mirror.vbfx.com::slackware/slackware-current
#
# Author: Eric Hameleers <alien@slackware.com>
#



onebuck 07-08-2009 02:02 PM

Hi,

Since 'SlackwareŽ Home' is down. You can use Alien_Bob's script 'mirror-slackware-current.sh'-UK to get rc1. Alien_Bob has graciously provided a mirror for a lot of his tools.

You can edit the script to select your rsync mirrors;

Quote:

# Good rsync mirrors are:
#
# slackware.mirrors.tds.net::slackware/slackware-current
# rsync.osuosl.org::slackware/slackware-current
# rsync.slackware.pl::slackware/slackware-current
# rsync.slackware.at::slackware/slackware-current
# mirrors.vbi.vt.edu::slackware/slackware-current
# rsync.slackware.no::slackware/slackware-current

Once you've got things setup for the script to suit your needs. You can run the script as per the sample;

Code:

sample from Alien_Bob;

sh  mirror-slackware-current.sh -m rsync.slackware.pl::slackware/slackware64-current -l /home/Desktop/slackware -a x86_64 -o DVD -f -v

Since you now have the iso of choice then burn the ISO image. Be sure to check the burnt ISO with 'CdromMd5sumsAfterBurning' or Alien_Bob's 'burnt_iso_md5_check.sh' script.

The above links and others available from 'Slackware-Links'. More than just SlackwareŽ links!

onebuck 07-09-2009 08:11 PM

Hi,

Hopefully now that 'Slackware.com' is back then we can get back to the serious side of slacking. :)

I recently moved to a hardware install of Slackware64. That is one slick Slack! :)

Looking forward to that new Slackware Release. :cool:

onebuck 07-26-2009 08:02 PM

Hi,

It's been about three weeks(Wed Jul 1 16:04:35 CDT 2009) since the Slackware RC1. I've since installed to a AMD64 machine. I'm really delighted and look forward to moving to other machines with the new release. It's about time to move the machines to the newer OS. I'll do a stable install to these just to see how things work out.

I feel that it won't be long before stable is here. :)

joeBuffer 07-31-2009 11:49 AM

Quote:

If you anticipate 'acpi' with your equipment then pass the parameter 'apci=off'. If 'apic' then pass 'noapic' to the kernel.
I'm confused, what do you mean "if you anticipate"? :scratch:

onebuck 08-01-2009 07:58 AM

Hi,

Quote:

Originally Posted by joeBuffer (Post 3626805)
I'm confused, what do you mean "if you anticipate"? :scratch:

I don't think that the word was mis-used;

Quote:

excerpt fro post #1;
If you anticipate 'acpi' with your equipment then pass the parameter 'apci=off'. If 'apic' then pass 'noapic' to the kernel.
Quote:

'Anticipate';
1. To feel or realize beforehand; foresee: hadn't anticipated the crowds at the zoo.
2. To look forward to, especially with pleasure; expect: anticipated a pleasant hike in the country.
3. To deal with beforehand; act so as to mitigate, nullify, or prevent: anticipated the storm by boarding up the windows. See synonyms at expect.
4. To cause to happen in advance; accelerate.
5. To use in advance, as income not yet available.
6. To pay (a debt) before it is due.
For clarity sake when you quote something in the future please provide the full quote with reference/link.

joeBuffer 08-01-2009 08:03 AM

No, I'd apologize if this seems like an insult, I'm just saying ...
Anticipating a storm and doing something, that I'd understand, but anticipating acpi in general wouldn't make much sense, since it should be there in most cases ... meaning if you expect that acpi will be doing things, and you turn it off, that doesn't make any sense, if you anticipate that it's going to cause problems, that's different.
It just seems like it might be confusing to someone, if they didn't understand what you mean.


All times are GMT -5. The time now is 08:27 PM.