diff options
author | Patrick J Volkerding <volkerdi@slackware.com> | 2010-05-19 08:58:23 +0000 |
---|---|---|
committer | Eric Hameleers <alien@slackware.com> | 2018-05-31 22:43:05 +0200 |
commit | b76270bf9e6dd375e495fec92140a79a79415d27 (patch) | |
tree | 3dbed78b2279bf9f14207a16dc634b90995cbd40 /CHANGES_AND_HINTS.TXT | |
parent | 5a12e7c134274dba706667107d10d231517d3e05 (diff) | |
download | current-b76270bf9e6dd375e495fec92140a79a79415d27.tar.gz current-b76270bf9e6dd375e495fec92140a79a79415d27.tar.xz |
Slackware 13.1slackware-13.1
Wed May 19 08:58:23 UTC 2010
Slackware 13.1 x86_64 stable is released!
Lots of thanks are due -- see the RELEASE_NOTES and the rest of the
ChangeLog for credits. The ISOs are on their way to replication,
a 6 CD-ROM 32-bit set and a dual-sided 32-bit/64-bit x86/x86_64 DVD.
We are taking pre-orders now at store.slackware.com, and offering
a discount if you sign up for a subscription. Consider picking up
a copy to help support the project. Thanks again to the Slackware
community for testing, contributing, and generally holding us to a
high level of quality. :-)
Enjoy!
Diffstat (limited to 'CHANGES_AND_HINTS.TXT')
-rw-r--r-- | CHANGES_AND_HINTS.TXT | 352 |
1 files changed, 171 insertions, 181 deletions
diff --git a/CHANGES_AND_HINTS.TXT b/CHANGES_AND_HINTS.TXT index f4dbb456e..2f980b8f3 100644 --- a/CHANGES_AND_HINTS.TXT +++ b/CHANGES_AND_HINTS.TXT @@ -1,154 +1,150 @@ -This file documents the instructions for upgrading to Slackware 13.0, the
+This file documents the instructions for upgrading to Slackware 13.1, the
packages added, removed, renamed, and/or split during the development cycle
-from Slackware 12.2 through 13.0, and some potential "gotchas" that users
+from Slackware 13.0 through 13.1, and some potential "gotchas" that users
can avoid by arming themselves with a little knowledge.
-*** INSTRUCTIONS FOR UPGRADING FROM 12.2 ***
+*** INSTRUCTIONS FOR UPGRADING FROM 13.0 ***
Follow the instructions detailed in the UPGRADE.TXT located in this
- directory. Note that upgrading from a Slackware version earlier
- than 12.2 is NOT supported at all and will most likely not work.
-
-Also note that upgrading from 12.2 to 13.0 (64bit) is not supported.
-
-
-*** PACKAGE ADDITIONS SINCE 12.2 ***
-
-a/xz
-ap/cupsddk
-ap/dc3dd
-d/swig
-kde/guidance-power-manager
-kde/kaudiocreator
-kde/kdebase-runtime
-kde/kdebase-workspace
-kde/kdepimlibs
-kde/kdeplasma-addons
-kde/kdevelop
-kde/kdevplatform
-kde/konq-plugins
-kde/ktorrent (moved from /extra)
-kde/mplayerthumbs
-kde/skanlite
-l/M2Crypto
-l/PyQt
-l/QScintilla
-l/akonadi
-l/automoc4
-l/babl
-l/boost
-l/chmlib
-l/clucene
-l/djvulibre
-l/eigen2
-l/exiv2
-l/gegl
-l/gmm
-l/ilmbase
-l/iso-codes
-l/jasper
-l/libarchive
-l/libdvdread
-l/libical
-l/libmcrypt
-l/libmsn
-l/libnl
-l/libspectre
-l/libvncserver
-l/libxklavier
-l/libzip
-l/openexr
-l/phonon
-l/pil
-l/pycups
-l/qca-cyrus-sasl
-l/qca-gnupg
-l/qca-ossl
-l/qimageblitz
-l/qtscriptgenerator
-l/raptor
-l/rasqal
-l/redland
-l/seamonkey-solibs
-l/sip
-l/soprano
-l/strigi
-l/taglib-extras
-l/urwid
-n/crda
-n/iw
-n/iwlwifi-5150-ucode
-n/snownews
-x/intel-gpu-tools
-x/scim-input-pad
-x/xcb-util
-x/xorg-server-xephyr
-x/xpyb
-x/xscope
-xap/MPlayer
-xap/electricsheep
-xap/thunar-volman
-xap/xfce4-power-manager
-
-extra/kde3-compat/arts
-extra/kde3-compat/kdelibs3
-extra/kde3-compat/qca-tls1
-extra/kde3-compat/qca1
-extra/kde3-compat/qt3
-extra/xf86-video-intel-alternate/xf86-video-intel-* (several alternate
- versions of the Xorg intel driver just in case the default doesn't work
- properly for you)
-
-
-*** PACKAGE REMOVALS SINCE 12.2 ***
-
-kde/kdeaddons
-kde/knemo
-l/arts
-l/beecrypt
-l/dbus-qt3
-l/qca-tls
-l/svgalib_helper (won't build on 2.6.28+ kernels)
-n/bitchx
-x/liboldX
-x/xf86-input-calcomp
-x/xf86-input-digitaledge
-x/xf86-input-dmc
-x/xf86-input-dynapro
-x/xf86-input-elo2300
-x/xf86-input-jamstudio
-x/xf86-input-magellan
-x/xf86-input-magictouch
-x/xf86-input-microtouch
-x/xf86-input-palmax
-x/xf86-input-spaceorb
-x/xf86-input-summa
-x/xf86-input-tek4957
-x/xf86-input-ur98
-x/xf86-video-cyrix
-x/xf86-video-fbdev
-x/xf86-video-i810 (use xf86-video-intel instead)
-x/xf86-video-imstt
-x/xf86-video-nsc
-x/xf86-video-vga
-x/xf86-video-via (use xf86-video-openchrome instead)
-x/xphelloworld
-x/xrx
-xap/gimp-help-2
+ directory. You will also need to read the "LIBATA SWITCHOVER" section
+ later in this document.
+Note that upgrading from a Slackware version earlier than 13.0 is NOT
+ supported at all and will most likely not work.
-*** OTHER NOTABLE CHANGES AND HINTS ***
-l/dbus moved to a/dbus
+*** PACKAGE ADDITIONS SINCE 13.0 ***
-New system user accounts:
- oprofile (uid=51)
+a/cpufrequtils
+a/usb_modeswitch
+ap/mpg123 (moved from /extra)
+ap/powertop
+kde/kdepim-runtime
+kde/kopete-cryptography
+kde/oxygen-icons
+kde/polkit-kde-1
+kde/polkit-qt-1
+l/ConsoleKit
+l/QScintilla
+l/attica
+l/ebook-tools
+l/eggdbus
+l/fftw
+l/giflib
+l/gst-plugins-good
+l/hunspell
+l/libdiscid
+l/libiodbc
+l/liblastfm
+l/libnotify
+l/libsamplerate
+l/v4l-utils
+l/loudmouth
+l/notify-python
+l/polkit
+l/polkit-gnome
+l/shared-desktop-ontologies
+l/system-config-printer
+l/virtuoso-ose
+n/epic5 (replaces epic4)
+n/iwlwifi-1000-ucode
+n/iwlwifi-6000-ucode
+n/bluez
+n/obex-data-server
+n/obexfs
+n/rt2860-firmware
+n/rt2870-firmware
+x/xf86-input-wacom
+x/xf86-video-nouveau-blacklist
+xap/blueman
+xap/geeqie
+xap/xfce4-notifyd
+/testing/btrfs-progs
+
+
+*** PACKAGE REMOVALS SINCE 13.0 ***
+
+a/device-mapper (part of lvm2 now)
+a/loadlin (mostly unneeded now)
+ap/cupsddk (part of cups now)
+ap/mpg321 (replaced by mpg123)
+l/libgtkhtml (obsolete)
+l/libungif (replaced by giflib)
+n/bluez-libs (part of bluez now)
+n/bluez-utils (part of bluez now)
+n/epic4 (replaced by epic5)
+x/lbxproxy (obsolete)
+x/liblbxutil (obsolete)
+x/proxymngr (obsolete)
+x/xf86-input-citron (does not compile)
+x/xf86-input-elographics (does not compile)
+x/xf86-input-fpit (does not compile)
+x/xf86-input-hyperpen (does not compile)
+x/xf86-input-mutouch (does not compile)
+x/xf86-video-newport (unneeded)
+x/xf86-video-xgixp (at least partially breaks X)
+xap/gqview (replaced with geeqie)
+kde/mplayerthumbs (part of kdemultimedia now)
+extra/mpg123 (moved to AP series)
+
+
+*** LIBATA SWITCHOVER ***
+
+The "old" ide subsystem in the the linux kernel is now deprecated in favor
+ of the newer libata subsystem, and this affects the naming of device nodes
+ for almost all types of disk drives -- hard drives in particular will now
+ have an "sd" named node. The following information should allow you to
+ handle that changeover gracefully.
+
+ 1. Upgrade the kernel and kernel-modules packages normally.
+
+ 2. Edit /etc/fstab to reflect the change from hd* to sd*.
+
+ If you have multiple SATA devices, and especially if you have some of
+ both hd* and sd* devices present already, then you're basically going
+ to be playing a guessing game right now, and you probably want to
+ consider using some of the persistent symlinks in the /dev/disk/by-*/
+ directories instead of raw device nodes -- for example, the links in
+ /dev/disk/by-id/ should always point to the same device, even if its
+ raw device node changes from e.g. sda1 to sdc1 or some such across
+ reboots.
+
+ * If you are using one of the generic kernels (requiring an initrd),
+ then use the sd* name for the root device when creating the image.
+
+ * You will almost surely want to remove the udev rules file for cdrom
+ devices (it will be regenerated on the next boot with correct
+ information reflecting the new libata stuff):
+ # rm -f /etc/udev/rules.d/70-persistent-cd.rules
+
+ * Speaking of optical devices, if you have multiple disk drives and an
+ optical drive using the old ide subsystem, then be aware that the
+ optical drive will get a /dev/sr* name instead of /dev/sd* -- this is
+ relevant because you might see something like this (if your optical
+ drive is currently /dev/hdb):
+
+ Old Name --> New Name
+ /dev/hda /dev/sda
+ /dev/hdb /dev/sr0
+ /dev/hdc /dev/sdb
+
+ 3. Run lilo. Note that you have made no edits at all to it yet, unless
+ you needed to edit it for the new kernel. Specifically, do not make
+ any changes with respect to hd* --> sd*.
+
+ 4. Reboot. At the lilo prompt, press <TAB> and add an append for the
+ real root device (which will no longer be /dev/hd*). For example, if
+ the old root device was /dev/hda1, and it will now be /dev/sda1, and
+ the name of your kernel image is "Linux" then you would do this:
+
+ Linux root=/dev/sda1
+
+ 5. Once the system comes back up, then fix /etc/lilo.conf, run lilo, and
+ reboot again to be sure everything is correct.
-New system group accounts:
- oprofile (gid=51)
- dialout (gid=16)
- netdev (gid=86)
+
+*** OTHER NOTABLE CHANGES AND HINTS ***
The Slackware installer now uses udev to initialize your hardware, including
the network interface card(s). This has positive consequences for network
@@ -168,6 +164,7 @@ The Slackware installer now uses udev to initialize your hardware, including your card. If you do not want to use udev, you must add the parameter
"noudev" to the command line that boots the Slackware installer, and the
original ("old") Slackware hardware configuration scripts will be used.
+ Also note that this is not supported...
Use one of the provided generic kernels for daily use. Do not report
bugs until/unless you have reproduced them using one of the stock
@@ -185,14 +182,14 @@ Use one of the provided generic kernels for daily use. Do not report 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 /extra/linux-2.6.29.6-nosmp-sdk/README.TXT to modify your
+ instructions in /extra/linux-2.6.33.4-nosmp-sdk/README.TXT to modify your
kernel sources for non-SMP usage. Note that this only applies if you are
using the Slackware-provided non-SMP kernel - if you build a custom kernel,
the symlinks at /lib/modules/$(uname -r)/{build,source} will point to the
correct kernel source so long as you don't (re)move it.
As usual, there are changes in udev packaging that need mentioning...
- As with 12.2, the system udev rules now reside in /lib/udev/rules.d/
+ As with 13.0, the system udev rules now reside in /lib/udev/rules.d/
instead of /etc/udev/rules.d/ in older versions. There should never be
a reason to edit anything in /lib/udev/rules.d/, so if you think you have
a case where this is required, either you're wrong or it needs to be
@@ -201,22 +198,12 @@ As usual, there are changes in udev packaging that need mentioning... files in /etc/udev/rules.d/ are still intended to (maybe) be edited as
needed by local system administrators, and as such, the rules for optical
and network devices will still be placed there.
- Also, be sure to have the new dialout group added to your system, or udev
- will kindly remind you in the system logs...
-Due to the upgrade of kde from 3.5.10 to 4.2.4, you will need to move your
- existing $HOME/.kde/ out of the way (either completely remove it or back
- it up somewhere else if you think you might need it again for whatever
- reason); otherwise, you will almost surely experience odd configuration
- problems with kde applications.
-
-If mailto: links don't work properly (or at all) in firefox, you may have
- to remove an existing $HOME/.mozilla/mimeTypes.rdf file and restart Firefox.
-
-If you are unable to access the cups configuration web interface from your
- browser, you may have to blacklist the ipv6 module and reboot. This is
- not an acceptable solution, of course, but it's the only one we have at
- the moment.
+Speaking of udev, pay particular attention to 70-persistent-net.rules and
+ 70-persistent-cd.rules in /etc/udev/rules.d/ -- these two are automatically
+ generated by the system. If you remove, add, and/or replace some hardware
+ (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.
HP multifunction printer/scanners require that your user account be a member
of the "lp" group for hp-toolbox to work properly, and to use the scanner
@@ -224,8 +211,8 @@ HP multifunction printer/scanners require that your user account be a member This is because hplip's udev rules set the device with group "lp" ownership.
HAL is not new anymore, but here are a few notes related to it:
- 1. User accounts with permission to mount removable devices must be in at
- least the "plugdev" group.
+ 1. User accounts with permission to mount removable devices and manipulate
+ bluetooth devices must be in at least the "plugdev" group.
2. User accounts with permission to do power-management tasks, such as
suspend, hibernate, reboot, and shutdown, via HAL methods should be in
the "power" group.
@@ -237,7 +224,7 @@ HAL is not new anymore, but here are a few notes related to it: cdrom/dvd drive includes the "owner" option, you will not be able to
mount it as a normal user.
4. If you find a need for modified fdi files, those should be placed in the
- relevant directories in /etc/hal/ instead of /usr/share/hal/
+ relevant directories in /etc/hal/fdi/ instead of /usr/share/hal/fdi/
If you notice Xfce's Terminal and perhaps some other applications being drawn
very slowly in X, then you should try explicitly disabling the Composite
@@ -247,7 +234,7 @@ If you notice Xfce's Terminal and perhaps some other applications being drawn We've also gotten a report of some other things (such as VirtualBox) that
might benefit from this.
-Speaking of Xorg, the version of Xorg shipped with Slackware 13.0 will not
+Speaking of Xorg, the version of Xorg shipped with Slackware 13.1 will not
(in most cases) require an /etc/X11/xorg.conf file at all. Configuration of
input devices and such is handled by HAL, and the X server autoconfigures
everything else. You can still create an xorg.conf file if you wish, or you
@@ -270,13 +257,29 @@ If you need to use a non-US keyboard layout, then copy the file located at reason.
If you are using input hotplugging via HAL and a synaptics touchpad, then you
- might need to copy /usr/share/hal/fdi/policy/11-x11-synaptics.fdi to
- /etc/hal/fdi/policy/ and edit it to suit your needs. You can also use
- synclient(1) to make changes "on the fly."
-
-If you want to try the new kernel mode setting (KMS), you don't have to
- build a custom kernel; add this to your kernel's lilo stanza:
- append = "i915.modeset=1"
+ might need to copy /usr/share/hal/fdi/policy/10osvendor/11-x11-synaptics.fdi
+ to /etc/hal/fdi/policy/ and edit it to suit your needs. You can also use
+ synclient(1) to make changes "on the fly."
+Also note that any touchpads that include actual buttons as part of the
+ touchpad hardware will not have tap-to-click enabled by default.
+
+In KDE, you can access the "System Settings" menu in Administrator mode by
+ running "kdesu systemsettings" as your normal user.
+
+If you see errors like this related to alsa during boot:
+ Loading ALSA mixer settings: /usr/sbin/alsactl restore
+ Unknown hardware: "HDA-Intel" ...
+ Hardware is initialized using a guess method
+ /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #31
+ /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #32
+ then you will need to remove /etc/asound.state, reboot (so that it is
+ regenerated with correct information), and reset the volume and such.
+
+If you see warnings like this when logging in:
+ configuration error - unknown item 'DIALUPS_CHECK_ENAB' (notify administrator)
+ configuration error - unknown item 'NOLOGIN_STR' (notify administrator)
+ then you need to move/merge /etc/login.defs.new with /etc/login.defs (and
+ also move/merge the other .new files that you have obviously neglected).
If you are using a KVM switch, you might experience problems with the mouse
when switching from one system to another. If so, you probably need to be
@@ -358,16 +361,3 @@ 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's lilo stanza:
append = "acpi=force"
-If you have a Dell Optiplex 760 (or perhaps some other machine that has the
- newer ICH10 chipset), and it won't boot, try one of these:
- 1. Update the BIOS image to at least A03
- 2. Turn C-States control off in the BIOS
- 3. Boot with "hpet=disabled"
-
-If your wireless and/or bluetooth radios are not turned on by default after
- booting up, you might need to load the rfkill-input module. If that solves
- the problem for you, edit /etc/rc.d/rc.modules.local or /etc/rc.d/rc.local
- to load the module on boot, or create /etc/modprobe.d/rfkill.conf and put
- the following line in it:
- install rfkill /sbin/modprobe -i rfkill ; /sbin/modprobe -i rfkill-input
-
|