trying to fine-tune SLACKw 12.2 so it's the way I had XP
 

Greetings.

I am fairly new to all OSs other than Windows. Ended up installing Slackware after I added new HDD and I wish I can use my old HDD as a storage only pretty soon.
Anyways..

★How do I make hyperlinks in Thunderbird to be active?
I mean they are, but not those for firefox.

★Where is all the 'program files' schtuff? If is there someone who can shortly explain me the structure of things, it would be very appreciated!
(I am losing my enthusiasm when reading tons of useless material but learning fast)

★I keep re-naming my external USB disk from 'Hard drive device' in few different Konqueror windows already, is this normal? Is the label in properties just on top of other label?

★can I easily change my system hotkeys or do I learn new? Is there >replace ready< file with Microsoft hotkeys for Linux?

★this is good one: how can I tell that I installed new software successfully when I CANNOT SEE IT ANYWHERE

Linux Rock!

All your answers can be found here:

http://www.slackbook.org/html/book.html

http://www.slackbook.org/

Best resources for a Slackware n00b. I recommend bookmarking them for future reference.

As you are using KDE, consider the following:

1. Open the KDE Control Center.
2. Select KDE Components.
3. Select Component Chooser.

a. Change the email client to ThunderBird.
b. For the browser, place the following in the text box:

firefox -new-tab

In KDE, look in the KDE Control Center, Regional & Accessibility, Keyboard Layout and Keyboard Shortcuts.

Slackware is a Linux based system, using the GNU tool chain, which is all based on the Unix model. You should spend about 10 minutes becoming familiar with the file system hiearchy.

Generally, all executable files are stored in /bin, /sbin, /usr/bin, /usr/sbin, /usr/local/bin, and /usr/local/sbin. Some executables are stored in /opt.

Generally, the system equivalent of DLLs usually are stored in /usr/lib.

Most system configuration files are stored in /etc.

User account files are stored somewhere in /home.

In Slackware, open a command terminal and as root, type pkgtool.

Slackware is not a typical operating system where everything is point-and-click. Read a lot and ask a lot of questions. :) Here at LQ, check the links provided in a user's signature and you'll be on your way to learning about Slackware.

the signposts are different here....you can "SEE" what programs and libraries are installed on your system by looking in /var/log/packages...the executable files for applications normally go to a directory, several, ending in bin or sbin, and some to /opt....remember the word 'patience' as it all will pay off for you. :)

Wow, this is brilliant!

I am absolutely amazed by the level of possible 'customization' of Linux!
I don't have to adopt myself, I will adopt OS to me...yay!

I rise my glass on KDE and all its options!!


There's still few things I'm trying to figure out:

★How do I mount .iso? Can I simply add device in K3b? What would be the 'device name'?

★Is it possible do activate/add password protection on folder?

★Is good idea to install Wine? Or is fight for native solution worth the hassle?

★Any 'System Restore' kinda plan B?

Thank you Woodsman!

Hi,

Just a few links to help you with your endeavors;

Slackware® Essentials
Slackware® Basics
Linux Documentation Project
Rute Tutorial & Exposition
Linux Command Guide
Linux Newbie Admin Guide
LinuxSelfHelp
Getting Started with Linux

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

From the command line, like this:

mount -o loop,ro /full/path/name.iso /mnt/iso1

The mount point /mnt/iso1 must first exist. You can create and use any mount point you want, but creating human readable mount point names is helpful.

I'm unsure what you are seeking. If you want only to use K3B to burn an ISO image to a disk, then K3B provides that option directly. You do not need to mount the ISO image to burn the image to disk.

The general approach toward protecting directories and files from certain users is performed with directory and file permissions. If a user account fails to satisfy those permissions then the user will be unable to access the files. The usual approach is to create a group, configure the group permissions, and then add users to the group. Thereafter, group ownership of files can be assigned to that group and all users in that group will have access.

For a quick example, as a normal user try accessing the files in /root. You can't.

Ask 10 people and you'll receive 11 opinions. :) WINE is a challenge for many people to configure. For me, the easier solution is VirtualBox.

Not inherently. If you want to roll back files to a certain date, then you'll need some kind of backup plan. I run such a plan on my box using rsnapshot. Every three hours I run a script through cron that backs up configuration files, certain user files, etc. The rsnapshot utility uses rsync, so after the first backup, most of the subsequent backups are hard links and consume very little disk space. You can read more here: A Backup Strategy.