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

Eric

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...

Hi,
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?

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. ;-)

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.

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

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!

Hi there,

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

See you around

Hi,

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

@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, ...)

Hi,

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.

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.

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!

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.

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;

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

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!