SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Just upgraded to 12.1 yesterday. I always prefer to wait a bit so that others can find the first glitches ;-)
Thanks for all the info in this thread - upgrade went without problems.
Just had to reconfigure my vmware (as expected because of the new kernel) and find a new vmware-any-any* package on the internet.
I'm glad you had a good upgrade! Are you sure you even needed an any-any-update tarball for your version of vmware? Back when I upgraded to Slackware 12.1 I upgraded to VMware-server-1.0.6-91891 and it did not need an any-any-update. This probably isn't true if you are using a newer custom kernel, however. Also, with vmware I recommend that you move the vmware startup script (SysV style) links in /etc/rc.d/rc5.d/ to /etc/rc.d/rc4.d/ so that they work properly (in case you use runlevel 4).
Are you sure you even needed an any-any-update tarball for your version of vmware?
Well, I haven't upgraded my vmware yet, still using an older version (1.04.???? I think).
My vmware script is in init.d and is started from rc.local (if [ -x ...] etc.). Any reason to change this setup?
I am still having a minor problem with the font in runlevel 3. I mostly use runlevel 4, but for maintenance etc. I boot in runlevel 3.
Using the console, some international characters won't display correctly (õ / ã), others will (é / ó / á). In X/KDE everything works fine. Since I live in Brazil, some filenames can have these characters.
Tried changing the font with setfont but no satisfactory results up to now.
I guess it has someting to do with the change to UTF?
It's nothing urgent, just something that annoys me a bit
Well, I haven't upgraded my vmware yet, still using an older version (1.04.???? I think).
My vmware script is in init.d and is started from rc.local (if [ -x ...] etc.). Any reason to change this setup?
By default vmware installs its init script under /etc/init.d and creates SysV style symlinks in /etc/rc.d/rc?.d. Because of this you don't really have to use Slackware style init scripts for it. You just need to move the symlinks in rc5.d to rc4.d so runlevel 4 will make use of them. However, if you do prefer Slackware init scripts for this, then you should remove all the vmware links under rc?.d and move the init script under init.d to /etc/rc.d/rc.vmware. Also, in addition to calling the start routine in rc.local, you should call a stop routine in rc.local_shutdown (you will probably need to create this file- make it executable of course).
Quote:
Originally Posted by niels.horn
I am still having a minor problem with the font in runlevel 3. I mostly use runlevel 4, but for maintenance etc. I boot in runlevel 3.
Using the console, some international characters won't display correctly (õ / ã), others will (é / ó / á). In X/KDE everything works fine. Since I live in Brazil, some filenames can have these characters.
Tried changing the font with setfont but no satisfactory results up to now.
I guess it has someting to do with the change to UTF?
It's nothing urgent, just something that annoys me a bit
You probably just need to set your UTF-8 locale. Here is a section of the CHANGES_AND_HINTS.TXT that may be of some help.
Quote:
Originally Posted by CHANGES_AND_HINTS.TXT
Input methods for complex characters (CJK, which is shorthand for Chinese,
Japanese, Korean) and other non-latin character sets have been added. These
input methods use the SCIM (Smart Common Input Method) platform.
The environment variables for SCIM support are set in /etc/profile.d/scim.sh
The requirements for getting SCIM input methods to work in your X session
are as follows:
(1) Use a UTF-8 locale. Look in /etc/profile.d/lang.sh for setting your
language to (for instance) en_US.UTF-8. As a word of warning: maybe you
should leave root with a non-UTF-8 locale because you don't want root's
commands to be misinterpreted. You can add the following line to your
~/.profile file to enable UTF-8 just for yourself:
export LANG=en_US.UTF-8
(2) Make the scim profile scripts executable. These will setup your
environment correctly for the use of scim with X applications. Run:
chmod +x /etc/profile.d/scim.*
(3) Start the scim daemon as soon as your X session starts. The scim daemon
must be active before any of your X applications. In KDE, you can add a
shell script to the ~/.kde/Autostart folder that runs the command
"scim -d". In XFCE you can add "scim -d" to the Autostarted Applications.
If you boot your computer in runlevel 4 (the graphical XDM/KDM login)
you can simply add the line "scim -d" to your ~/.xprofile file.
This gives you a Desktop Environment independent way of starting scim.
When scim is running, you will see a small keyboard icon in your system tray.
Right-click it to enter SCIM Setup. In 'Global Setup' select your keyboard
layout, and you are ready to start entering just about any language
characters you wish! Press the magical key combo <Control><Space>
in order to activate or deactivate SCIM input. The SCIM taskbar in the
desktop's corner allows you to select a language. As you type, SCIM will show
an overview of applicable character glyphs (if you are inputting complex
characters like Japanese).
/etc/profile.d/lang.sh has some nice comments as well.
By default vmware installs its init script under /etc/init.d and creates SysV style symlinks in /etc/rc.d/rc?.d. Because of this you don't really have to use Slackware style init scripts for it. You just need to move the symlinks in rc5.d to rc4.d so runlevel 4 will make use of them. However, if you do prefer Slackware init scripts for this, then you should remove all the vmware links under rc?.d and move the init script under init.d to /etc/rc.d/rc.vmware. Also, in addition to calling the start routine in rc.local, you should call a stop routine in rc.local_shutdown (you will probably need to create this file- make it executable of course).
Ok, understood. I am so used to the "Slackware" way of doing things that I put it in the rc.local script. I did clean up the rc.? scripts. I might study this SysV style of starting things. It seems that it may have some advantages like starting some scripts only in runlevel 3, others only in runlevel 4. Is this correct?
Quote:
Originally Posted by shadowsnipes
You probably just need to set your UTF-8 locale. Here is a section of the CHANGES_AND_HINTS.TXT that may be of some help.
/etc/profile.d/lang.sh has some nice comments as well.
Well, this part is a bit more complicated... But I solved my problem today.
Since I exchange files with a Windows notebook (sorry... from the company I work for... ), I use the ISO-8859-1 character set (export LANG=pt_BR.ISO8859-1 in /etc/profile.d/lang.sh) to copy files in both directions, maintaining all special characters in the filenames. I have this setup since Slackware 10.x I think, including some Samba shares etc. Changing completely to UTF seems complicated now, since I have tons of files with names I won't be able to list.
What worked for me is the following:
Code:
#!/bin/bash
kbd_mode -a
echo -ne '\033%@'
setfont LatArCyrHeb-16
Where:
kbd_mode -a --> sets the keybord to ASCII mode (as oposed to UTF mode)
echo -ne '\033%@' --> resets the tty configuration
setfont LatArCyrHeb-16 --> sets a nice font with all the special characters I need
I put this in a small script I start from /etc/rc.d/rc.local so my console works fine without affecting my X/KDE settings.
By the way, I do read the CHANGES_AND_HINTS.TXT file But no offense taken! And thanks for all the help until now.
Ok, understood. I am so used to the "Slackware" way of doing things that I put it in the rc.local script. I did clean up the rc.? scripts. I might study this SysV style of starting things. It seems that it may have some advantages like starting some scripts only in runlevel 3, others only in runlevel 4. Is this correct?
You can actually do all the same stuff with Slackware style init scripts, so it really just boils down to what you like best. For instance, if you want runlevel 3 specific actions then you could create a rc.3 script to handle it. inittab might run this file out of the box, but if it doesn't for some reason then you could always check the runlevel (use runlevel command) in rc.M and then call rc.3 if it's needed. For runlevel 4 specific actions there already is a rc.4 file.
At first glance, SysV style scripts may be seem more suited if you need to have some runlevel-specific funky order to shutdown or start services, but you can easily accomplish this by hacking the Slackware init scripts as well (and without learning the link naming conventions for SysV). So, again, it all boils down to preference. That being said, I definitely recommend you become familiar with SysV scripts, because pretty much every distro uses them.
Edit:
I thought I would add (since the thread is about upgrading) that one disadvantage of hacking the Slackware init scripts versus using provided SysV scripts is that you have to spend more time merging changes from the upgrade. Of course, using rc.local, rc.local_shutdown, and rc.netdevice would not require any script hacking, and they are usually sufficient for most needs.
Last edited by shadowsnipes; 07-30-2008 at 01:01 AM.
That being said, I definitely recommend you become familiar with SysV scripts, because pretty much every distro uses them.
For me, the essence of Linux is having options to choose from
Any suggestion on where to find some not-too-basic documentation on SysV scripts? I mean, I don't need to learn what's a runlevel or how to write a shell script... But I would like to understand the logic of SysV scripts - what calls what, in which order, etc.
Thanks again!
For me, the essence of Linux is having options to choose from
Any suggestion on where to find some not-too-basic documentation on SysV scripts? I mean, I don't need to learn what's a runlevel or how to write a shell script... But I would like to understand the logic of SysV scripts - what calls what, in which order, etc.
Thanks again!
Thanks for the link to the explanation of SysV scripts.
In the meantime, today I upgraded my third Slackware 12 machine to 12.1
It is an 'older' desktop (PIII-600MHz board) and I had some problems for which I would like to share the solutions.
First of all I ended up without a working network interface. After checking the logs (/var/log/messages) I found out all the IRQs were mixed up and there were conflicts between the NIC, video and sound card.
Solved it adding the following line to lilo.conf:
Code:
append = "acpi=force"
Second problem was that my mouse had stopped working.
This was a silly problem and I remembered vaguely reading something somewhere... It was in the CHANGES_AND_HINTS.TXT:
Code:
Also, you must NOT leave a backup of the old blacklist file (such
as blacklist.orig) in /etc/modprobe.d/ -- ALL files in that directory are
checked, so if a module is blacklisted in *any* of them, it won't be
loaded.
I had a blacklist.orig file there that stopped my mouse from working... Serves me well... Should have read the xxxx manual again, even the third time
I'll try to go!
I actually live in Rio, about 500km from São Paulo. But I'll be in São Paulo on the 21st so I might stay for another day. The agenda looks interesting, especially the one about Netfilter/IPtables the one about 'encrypted systems' (Alien_Bob).
Just wanted to say good job on the How To! Thanks for take the time to write it all up. Since it was never stickied, have you placed all this info on a webpage or something yet by chance? Not that this would ever get lost but it would be nice to have it all on one page and then a nice quick link in a signature for future reference.
Just wanted to say good job on the How To! Thanks for take the time to write it all up. Since it was never stickied, have you placed all this info on a webpage or something yet by chance? Not that this would ever get lost but it would be nice to have it all on one page and then a nice quick link in a signature for future reference.
Thank you for your appreciation I have not put this HowTo on a personal web page as of yet. I may do so in the future if I decide to maintain a personal site. The main reason I decided to post it here instead of the wiki was so that the contents would show up in the LQ forum searches. I believe that more people search LQ threads than the Wikis. Plus, it is nice for there to be a place for discussion.
Hopefully when future Slackware versions come out I will have time to generate similar threads (or web pages).
Ha ha, i wasn't requesting that you do it. I was going to throw it in mine but i held off just in case you had a webpage with it looking a little cleaner, since it's broken up a bit in the post.
Just wanted to say good job on the How To! Thanks for take the time to write it all up. Since it was never stickied, have you placed all this info on a webpage or something yet by chance? Not that this would ever get lost but it would be nice to have it all on one page and then a nice quick link in a signature for future reference.
Perhaps if we rated it, it would become a sticky?
Click "Rate Thread" just above the top post on the right and give it the five stars it deserves. I have.
Thank you, thank you...to Shadowsnipes your are a gentle person and a scholar as is Rob....Plez dear moderator sticky this most important and useful post
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
), I use the ISO-8859-1 character set (export LANG=pt_BR.ISO8859-1 in /etc/profile.d/lang.sh) to copy files in both directions, maintaining all special characters in the filenames. I have this setup since Slackware 10.x I think, including some Samba shares etc. Changing completely to UTF seems complicated now, since I have tons of files with names I won't be able to list.
But no offense taken! And thanks for all the help until now.
again, even the third time 
