summaryrefslogtreecommitdiffstats
path: root/CHANGES_AND_HINTS.TXT
blob: 9ce8a6737e9fa27265465195218d0ab366b9331b (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
This file documents the instructions for upgrading to Slackware 14.1, the 
packages added, removed, renamed, and/or split during the development cycle 
from Slackware 14.0 through 14.1, and some potential "gotchas" that users 
can avoid by arming themselves with a little knowledge.


*** INSTRUCTIONS FOR UPGRADING FROM 14.0 ***

Follow the instructions detailed in the UPGRADE.TXT located in this
  directory.  

Note that upgrading from a Slackware version earlier than 14.0 is NOT 
  supported at all and will most likely not work.


*** PACKAGE ADDITIONS SINCE 14.0 ***

a/efibootmgr
a/elilo
a/grub
a/os-prober
ap/itstool
ap/mariadb
ap/terminus-font
ap/tmux
d/help2man
d/open-cobol
kde/audiocd-kio
kde/bomber
kde/bovo
kde/dragon
kde/granatier
kde/juk
kde/kapman
kde/katomic
kde/kblackbox
kde/kblocks
kde/kbounce
kde/kbreakout
kde/kde-base-artwork
kde/kdevelop-php
kde/kdevelop-php-docs
kde/kdiamond
kde/kfourinline
kde/kgoldrunner
kde/kigo
kde/killbots
kde/kio-mtp
kde/kiriki
kde/kjumpingcube
kde/klickety
kde/klines
kde/kmahjongg
kde/kmines
kde/kmix
kde/knavalbattle
kde/knetwalk
kde/kolf
kde/kollision
kde/konquest
kde/kpat
kde/kreversi
kde/kross-interpreters
kde/kscreen
kde/kshisen
kde/ksirk
kde/ksnakeduel
kde/kspaceduel
kde/ksquares
kde/ksudoku
kde/ktuberling
kde/kubrick
kde/libkcddb
kde/libkcompactdisc
kde/libkdegames
kde/libkmahjongg
kde/libkscreen
kde/lskat
kde/mplayerthumbs
kde/nepomuk-core
kde/nepomuk-widgets
kde/oxygen-gtk3
kde/pairs
kde/palapeli
kde/picmi
kde/print-manager
kdei/calligra-l10n-bs
kdei/calligra-l10n-gl
kdei/calligra-l10n-ia
kdei/calligra-l10n-sl
kdei/calligra-l10n-tr
kdei/kde-l10n-hi
kdei/kde-l10n-mr
l/at-spi2-atk
l/at-spi2-core
l/dconf
l/gnome-themes-standard
l/gnu-efi
l/harfbuzz
l/libsecret
l/libunistring
l/gc
l/qjson
l/libevent
n/ulogd
n/nfacct
n/ebtables
n/libqmi
n/libmbim
n/ipset
n/conntrack-tools
n/libnetfilter_queue
n/libnetfilter_log
n/libnetfilter_cttimeout
n/libnetfilter_cthelper
n/libnetfilter_conntrack
n/libnetfilter_acct
n/libnfnetlink
n/libmnl
x/glu
x/xcb-util-cursor
x/xcm
x/xf86-video-sisusb
x/xf86-video-tseng
x/xf86-video-xgi
x/xf86-video-xgixp
xap/ddd
xfce/xfce4-terminal



*** PACKAGE REMOVALS SINCE 14.0 ***

ap/aumix (moved to /pasture)
ap/mysql (replaced with mariadb)
ap/rexima (moved to /pasture)
kde/kdegames (split into multiple packages)
kde/kdemultimedia (split into multiple packages)
kde/ksecrets (??)
kde/printer-applet (replaced with kde/print-manager)
kde/quanta (fails to compile; dead upstream)
x/scim-bridge (functionality included with x/scim)
xap/xxgdb (replaced with xap/ddd)
xfce/Terminal (replaced with xfce/xfce4-terminal)



*** OTHER NOTABLE CHANGES AND HINTS ***

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 
  generic kernels.  You will need to create an initrd in order to boot
  the generic kernels - see /boot/README.initrd for instructions.
  The huge kernels are primarily intended as "installer" and "emergency" 
  kernels in case you forget to make an initrd.  For most systems, you 
  should use the generic SMP kernel if it will run, even if your system is 
  not SMP-capable.  Some newer hardware needs the local APIC enabled in the 
  SMP kernel, and theoretically there should not be a performance penalty 
  with using the SMP-capable kernel on a uniprocessor machine, as the SMP 
  kernel tests for this and makes necessary adjustments.  Furthermore, the 
  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 
  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-3.10.17-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 with 14.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 addressed in 
  the upstream source.  However, you can override default rules by placing 
  one with an identical name inside /etc/udev/rules.d/  The rules 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.

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 (or
  just remove them and reboot to create new ones).

Both printing and scanning require that your user account be a member of the 
  "lp" group (membership in the "scanner" group is no longer needed by any
  of the included scanner drivers, though some third party drivers may still
  need it); we had to configure sane to use the "lp" group or else
  multifunction devices (e.g. print/scan/copy units) would only do one or the
  other (depending on whether the group ownership was "lp" or "scanner").

Xorg no longer uses /etc/X11/xorg.conf by default (and in most cases, there
  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 
  specific contents that you wish to override (as an example, to use a binary
  video driver) as separate files in the /etc/X11/xorg.conf.d/ directory.

  /usr/share/X11/xorg.conf.d/ is the "packaged" configuration directory; all
  files ending with ".conf" in this directory are used by the X server 
  unless there is an identically-named file in the local sysadmin directory.
  The local sysadmin config directory is /etc/X11/xorg.conf.d/ - all files
  ending with ".conf" in this directory are parsed.  

  There are several default config files in /usr/share/X11/xorg.conf.d/:
    * 10-evdev.conf
        a "catchall" file for input devices using the evdev driver; this 
        should work for most hardware in the absence of a better driver
    * 50-synaptics.conf
        overrides the earlier 10-evdev.conf file and uses the synaptics 
        driver for all touchpads
    * 50-wacom.conf
        overrides the earlier 10-evdev.conf file and uses the wacom driver 
        for Wacom tablets
    * 90-keyboard-layout.conf
        this sample ("normal" en layout) keeps the "old" default of 
        allowing Zap'ing the Xserver.
  If you need to modify any of these defaults, then copy the relevant file
  from /usr/share/X11/xorg.conf.d/ to /etc/X11/xorg.conf.d/ and edit the
  copy.

  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).  Place the following content in
  a file at /etc/X11/xorg.conf.d/disable-composite.conf:
    Section "Extensions"
      Option "Composite" "Disable"
    EndSection

Now that KMS (Kernel Mode Setting) for graphics cards has (mostly) stabilized,
  it is enabled by default for intel, ati, and nvidia graphics chipsets.  It
  is possible to disable it use "nomodeset" as a kernel append in lilo.conf,
  but Xorg will not work at all on intel and 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:
    append="video=1024x768"

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

If your cd/dvd drive is not visible inside a gtk-based desktop environment
  (e.g. Xfce), you may need to add "comment=x-gvfs-show" to the /etc/fstab 
  line for the device.  For more information, see this document:
  http://git.gnome.org/browse/gvfs/tree/monitor/udisks2/what-is-shown.txt

The version of logrotate in Slackware 14.0 added an "su" option to define 
  user/group for rotation.  Logrotate now skips directories which are world 
  writable or writable by a group which is not "root" unless the "su" 
  directive is used.  This has ramifications for third party packages that
  installed e.g. /var/log/somedir owned by a non-root user and/or group.

If you have set up an encrypted root partition, you will need to have access 
  to your keyboard in order to type the passphrase.  This may require you to 
  add the uhci-hcd and usbhid modules to your initrd image if you have a USB 
  keyboard.  Also note that if you are using a non-US keyboard, you can use the
  '-l' parameter to the 'mkinitrd' command in order to add support for this
  keyboard to your initrd.

If you have permission errors when attempting to burn a cdrom or dvd image,
  such as the following:
    /usr/bin/cdrecord: Operation not permitted. Cannot send SCSI cmd via ioctl
  then cdrecord almost certainly needs root privileges to work correctly.
  One potential solution is to make the cdrecord and cdrdao binaries suid root,
  but this has possible security implications.  The safest way to do that is 
  to make those binaries suid root, owned by a specific group, and executable
  by only root and members of that group.  For most people, the example below
  will be sufficient (but adjust as desired depending on your specific needs):
    chown root:cdrom /usr/bin/cdrecord /usr/bin/cdrdao
    chmod 4750 /usr/bin/cdrecord /usr/bin/cdrdao
  If you don't want all members of the 'cdrom' group to be able to execute the
  two suid binaries, then create a special group (such as 'burning' which is
  recommended by k3b), use it instead of 'cdrom' in the line above, and add
  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,
  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).