[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
playground:changeshints [2012/08/19 19:00 (UTC)] – created rinias | playground:changeshints [2012/08/19 19:31 (UTC)] (current) – rinias | ||
---|---|---|---|
Line 6: | Line 6: | ||
- | ===== *** INSTRUCTIONS FOR UPGRADING FROM 13.37 *** ===== | + | < |
- | Follow the instructions detailed in the UPGRADE.TXT located in this | + | Follow the instructions detailed in the UPGRADE.TXT located in this directory. |
- | | + | |
- | Note that upgrading from a Slackware version earlier than 13.37 is NOT | + | Note that upgrading from a Slackware version earlier than 13.37 is NOT supported at all and will most likely not work.</ |
- | | + | |
- | ==== *** PACKAGE ADDITIONS SINCE 13.37 *** ==== | + | ===== PACKAGE ADDITIONS SINCE 13.37 ===== |
Line 169: | Line 167: | ||
- | *** PACKAGE REMOVALS SINCE 13.37 *** | + | ===== PACKAGE REMOVALS SINCE 13.37 ===== |
- | a/gdisk - renamed to gptfdisk | + | * a/gdisk - //renamed to gptfdisk// |
- | a/ | + | |
- | ap/ | + | |
- | kde/kdeaccessibility \ | + | //KDE packages have been split up - notice all of the new packages in the " |
- | kde/kdebase | + | |
- | kde/ | + | |
- | kde/ | + | |
- | kde/ | + | |
- | kde/kdeedu | + | |
- | kde/ | + | |
- | kde/ | + | |
- | kde/ | + | |
- | kde/ | + | |
- | kde/ | + | |
- | l/hal-info - obsolete; replaced by various udev components | + | * kde/ |
- | l/hal - obsolete; replaced by upower, udisks, various others | + | * kde/ |
+ | * kde/ | ||
+ | * kde/ | ||
+ | * kde/ | ||
+ | * kde/ | ||
+ | * kde/ | ||
+ | * kde/ | ||
+ | * kde/ | ||
+ | * kde/ | ||
+ | * kde/ | ||
+ | |||
+ | |||
+ | * l/hal-info - //obsolete; replaced by various udev components// | ||
+ | | ||
+ | * l/jre - //removed due to licensing issues// | ||
+ | * l/wv2 - //no longer used by anything in Slackware// | ||
+ | * l/raptor - //no longer used (everything links raptor2 instead)// | ||
- | l/jre - removed due to licensing issues | + | //All of these firmwares (except some *old* ones are now included in the kernel-firmware package -- if you need an older firmware, use an older Slackware.// |
- | l/wv2 - no longer used by anything in Slackware | + | * n/rt2860-firmware |
+ | * n/ | ||
+ | * n/ | ||
+ | * n/ | ||
+ | * n/ | ||
+ | * n/ | ||
+ | * n/ | ||
+ | * n/ | ||
+ | * n/ | ||
+ | * n/ | ||
+ | * n/ | ||
+ | * n/ | ||
+ | * x/ | ||
- | l/raptor - no longer used (everything links raptor2 instead) | + | //All of these are obsolete and/or will not build with recent Xorg and/or toolchains:// |
- | n/rt2860-firmware | + | * x/xf86-video-sisusb |
- | n/ | + | |
- | n/rt61-firmware | + | * x/xf86-video-xgi |
- | n/rt71w-firmware | + | * x/xf86-video-radeonhd |
- | n/iwlwifi-100-ucode \ | + | * x/scripts |
- | n/iwlwifi-1000-ucode | + | |
- | n/ | + | |
- | n/iwlwifi-4965-ucode | + | |
- | n/ | + | |
- | n/ | + | |
- | n/ | + | |
- | n/ | + | |
- | x/radeon_ucode | + | |
- | x/xf86-video-sisusb --\ | + | //All of these are moved to the new xfce/ set:// |
- | x/xf86-video-tseng | + | |
- | x/ | + | |
- | x/ | + | |
- | x/ | + | |
- | x/xaw3d -------------/ | + | |
- | xap/ | + | * xap/ |
- | xap/ | + | |
- | xap/ | + | * xap/ |
- | xap/ | + | |
- | extra/jdk - removed due to licensing issues | ||
+ | * extra/jdk - //removed due to licensing issues// | ||
+ | |||
- | *** OTHER NOTABLE CHANGES AND HINTS *** | + | ===== OTHER NOTABLE CHANGES AND HINTS ===== |
Use one of the provided generic kernels for daily use. Do not report | Use one of the provided generic kernels for daily use. Do not report | ||
- | | + | bugs until/ |
- | generic kernels. | + | generic kernels. |
- | the generic kernels - see / | + | the generic kernels - see / |
- | The huge kernels are primarily intended as " | + | The huge kernels are primarily intended as " |
- | kernels in case you forget to make an initrd. | + | kernels in case you forget to make an initrd. |
- | should use the generic SMP kernel if it will run, even if your system is | + | should use the generic SMP kernel if it will run, even if your system is |
- | not SMP-capable. | + | not SMP-capable. |
- | SMP kernel, and theoretically there should not be a performance penalty | + | SMP kernel, and theoretically there should not be a performance penalty |
- | with using the SMP-capable kernel on a uniprocessor machine, as the SMP | + | with using the SMP-capable kernel on a uniprocessor machine, as the SMP |
- | kernel tests for this and makes necessary adjustments. | + | kernel tests for this and makes necessary adjustments. |
- | kernel sources shipped with Slackware are configured for SMP usage, so you | + | kernel sources shipped with Slackware are configured for SMP usage, so you |
- | won't have to modify those to build external modules (such as NVidia or | + | won't have to modify those to build external modules (such as NVidia or |
- | ATI proprietary drivers) if you use the SMP kernel. | + | ATI proprietary drivers) if you use the SMP kernel. |
- | | + | If you decide to use one of the non-SMP kernels, you will need to follow the |
- | instructions in / | + | instructions in / |
- | kernel sources for non-SMP usage. | + | kernel sources for non-SMP usage. |
- | using the Slackware-provided non-SMP kernel - if you build a custom kernel, | + | using the Slackware-provided non-SMP kernel - if you build a custom kernel, |
- | the symlinks at / | + | the symlinks at / |
- | correct kernel source so long as you don't (re)move it. | + | correct kernel source so long as you don't (re)move it. |
As with 13.37, the system udev rules now reside in / | As with 13.37, the system udev rules now reside in / | ||
- | | + | of / |
- | to edit anything in / | + | to edit anything in / |
- | where this is required, either you're wrong or it needs to be addressed in | + | where this is required, either you're wrong or it needs to be addressed in |
- | the upstream source. | + | the upstream source. |
- | one with an identical name inside / | + | one with an identical name inside / |
- | / | + | / |
- | local system administrators, | + | local system administrators, |
- | devices will still be placed there. | + | devices will still be placed there. |
Speaking of udev, pay particular attention to 70-persistent-net.rules and | Speaking of udev, pay particular attention to 70-persistent-net.rules and | ||
- | | + | 70-persistent-cd.rules in / |
- | generated by the system. | + | generated by the system. |
- | (specifically network cards and/or optical drives) in a machine, you will | + | (specifically network cards and/or optical drives) in a machine, you will |
- | probably need to edit one or both of the rules files mentioned above. | + | probably need to edit one or both of the rules files mentioned above. |
If you are upgrading (as opposed to a new install), there are some stale files | If you are upgrading (as opposed to a new install), there are some stale files | ||
- | | + | in / |
- | bluetooth.conf, | + | bluetooth.conf, |
- | See / | + | See / |
Both printing and scanning require that your user account be a member of the | Both printing and scanning require that your user account be a member of the | ||
- | | + | " |
- | | + | to configure sane to use the " |
- | | + | (e.g. print/ |
- | | + | whether the group ownership was " |
Xorg no longer uses / | Xorg no longer uses / | ||
- | | + | is absolutely no need for it). You can still create an xorg.conf file if |
- | you wish, or you can create some minimal xorg.conf snippets with only the | + | you wish, or you can create some minimal xorg.conf snippets with only the |
- | specific contents that you wish to override (as an example, to use a binary | + | specific contents that you wish to override (as an example, to use a binary |
- | video driver) as separate files in the / | + | video driver) as separate files in the / |
- | | + | / |
- | files ending with " | + | files ending with " |
- | unless there is an identically-named file in the local sysadmin directory. | + | unless there is an identically-named file in the local sysadmin directory. |
- | The local sysadmin config directory is / | + | The local sysadmin config directory is / |
- | ending with " | + | ending with " |
- | | + | There are several default config files in / |
- | * 10-evdev.conf | + | * 10-evdev.conf |
- | | + | * 50-synaptics.conf |
- | | + | * 50-wacom.conf |
- | * 50-synaptics.conf | + | * 90-keyboard-layout.conf |
- | | + | |
- | | + | |
- | * 50-wacom.conf | + | |
- | | + | |
- | | + | |
- | * 90-keyboard-layout.conf | + | |
- | | + | |
- | | + | |
- | If you need to modify any of these defaults, then copy the relevant file | + | |
- | from /usr/share/ | + | |
- | copy. | + | |
- | | + | If you need to modify any of these defaults, then copy the relevant file |
- | crashes on startup, try disabling the Composite extension (which will also | + | from / |
- | disable all of the fancy desktop effects). | + | copy. |
- | a file at / | + | |
+ | Regardless of your chipset (though it seems more common with intel), if KDE | ||
+ | crashes on startup, try disabling the Composite extension (which will also | ||
+ | disable all of the fancy desktop effects). | ||
+ | a file at / | ||
Section " | Section " | ||
Option " | Option " | ||
Line 314: | Line 312: | ||
Now that KMS (Kernel Mode Setting) for graphics cards has (mostly) stabilized, | Now that KMS (Kernel Mode Setting) for graphics cards has (mostly) stabilized, | ||
- | | + | it is enabled by default for intel, ati, and nvidia graphics chipsets. |
- | is possible to disable it use " | + | is possible to disable it use " |
- | but Xorg will not work at all on intel (and some ati) chips if you do that. | + | but Xorg will not work at all on intel (and some ati) chips if you do that. |
| | ||
- | | + | If you want to change the resolution of the KMS console, that can be done |
- | with something like this as a kernel append in lilo.conf: | + | with something like this as a kernel append in lilo.conf: |
append=" | append=" | ||
- | | + | Speaking of lilo.conf and KMS, make sure you use either vga=normal or |
- | vga=extended -- some of the framebuffers don't like KMS very much... | + | vga=extended -- some of the framebuffers don't like KMS very much... |
If you see some log messages like this: | If you see some log messages like this: | ||
mdadm: sending ioctl 1261 to a partition! | mdadm: sending ioctl 1261 to a partition! | ||
- | | + | They' |
- | http:// | + | http:// |
The version of logrotate in Slackware 14.0 added an " | The version of logrotate in Slackware 14.0 added an " | ||
- | | + | user/group for rotation. |
- | writable or writable by a group which is not " | + | writable or writable by a group which is not " |
- | directive is used. This has ramifications for third party packages that | + | directive is used. This has ramifications for third party packages that |
- | installed e.g. / | + | installed e.g. / |
If you are using a KVM switch, you might experience problems with the mouse | If you are using a KVM switch, you might experience problems with the mouse | ||
- | | + | when switching from one system to another. |
- | using the imps protocol for the psmouse driver, and that's a simple fix: | + | using the imps protocol for the psmouse driver, and that's a simple fix: |
- | Copy / | + | Copy / |
- | uncomment the following line in / | + | uncomment the following line in / |
#options psmouse proto=imps | #options psmouse proto=imps | ||
- | | + | Next, unload and reload the psmouse module (do this as root): |
modprobe -r psmouse ; modprobe psmouse | modprobe -r psmouse ; modprobe psmouse | ||
If you have set up an encrypted root partition, you will need to have access | If you have set up an encrypted root partition, you will need to have access | ||
- | | + | to your keyboard in order to type the passphrase. |
- | add the uhci-hcd and usbhid modules to your initrd image if you have a USB | + | add the uhci-hcd and usbhid modules to your initrd image if you have a USB |
- | keyboard. | + | keyboard. |
- | ' | + | ' |
- | keyboard to your initrd. | + | keyboard to your initrd. |
If you have permission errors when attempting to burn a cdrom or dvd image, | If you have permission errors when attempting to burn a cdrom or dvd image, | ||
- | | + | such as the following: |
/ | / | ||
- | | + | then cdrecord almost certainly needs root privileges to work correctly. |
- | One potential solution is to make the cdrecord and cdrdao binaries suid root, | + | One potential solution is to make the cdrecord and cdrdao binaries suid root, |
- | but this has possible security implications. | + | but this has possible security implications. |
- | to make those binaries suid root, owned by a specific group, and executable | + | to make those binaries suid root, owned by a specific group, and executable |
- | by only root and members of that group. | + | by only root and members of that group. |
- | will be sufficient (but adjust as desired depending on your specific needs): | + | will be sufficient (but adjust as desired depending on your specific needs): |
chown root:cdrom / | chown root:cdrom / | ||
chmod 4750 / | chmod 4750 / | ||
- | | + | If you don't want all members of the ' |
- | two suid binaries, then create a special group (such as ' | + | two suid binaries, then create a special group (such as ' |
- | recommended by k3b), use it instead of ' | + | recommended by k3b), use it instead of ' |
- | to it only the users you wish to have access to cdrecord and cdrdao. | + | to it only the users you wish to have access to cdrecord and cdrdao. |
Input methods for complex characters (CJK, which is shorthand for Chinese, | 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. | + | input methods use the SCIM (Smart Common Input Method) platform. |
- | The environment variables for SCIM support are set in / | + | The environment variables for SCIM support are set in / |
- | The requirements for getting SCIM input methods to work in your X session | + | The requirements for getting SCIM input methods to work in your X session |
- | are as follows: | + | are as follows: |
- | | + | |
- | | + | |
- | | + | |
- | | + | When scim is running, you will see a small keyboard icon in your system tray. |
- | | + | Right-click it to enter SCIM Setup. In ' |
- | | + | layout, and you are ready to start entering just about any language |
- | | + | characters you wish! Press the magical key combo < |
- | | + | in order to activate or deactivate SCIM input. The SCIM taskbar in the |
- | | + | desktop' |
- | | + | an overview of applicable character glyphs (if you are inputting complex |
- | | + | characters like Japanese). |
- | | + | |
- | | + | |
- | | + | |
- | | + | |
- | | + | |
- | When scim is running, you will see a small keyboard icon in your system tray. | + | |
- | Right-click it to enter SCIM Setup. In ' | + | |
- | layout, and you are ready to start entering just about any language | + | |
- | characters you wish! Press the magical key combo < | + | |
- | in order to activate or deactivate SCIM input. The SCIM taskbar in the | + | |
- | desktop' | + | |
- | an overview of applicable character glyphs (if you are inputting complex | + | |
- | characters like Japanese). | + | |
If you have an older machine (with a BIOS released prior to 2001) and it will | If you have an older machine (with a BIOS released prior to 2001) and it will | ||
- | | + | not power off on shutdown, try adding this to your kernel' |
append = " | append = " | ||
If you have a Thinkpad T400 or T500, you probably want to append " | If you have a Thinkpad T400 or T500, you probably want to append " | ||
- | | + | to the kernel boot parameters. |
- | https:// | + | https:// |
- | TODO: | + | =====TODO:===== |
Not sure if/where these belong yet: | Not sure if/where these belong yet: |