Slackware 13.0 with KDE 3.5.10?
in [Slackware]
|
Prev: useradd, upgrading Feunster
Next: Qemu help
From: Tuxedo on 26 Dec 2009 08:05 On Dec 26, 12:17 am, Eric Hameleers <er...(a)sox.homeip.net> wrote: [...] > Easy... download and install these packages which Pat made for people > like you who are not ready for KDE4:http://slackware.osuosl.org/unsupported/kde-3.5.10-for-slack13.0/ > > They are compiled on Slackware 13.0. Their status is "unsupported", > meaning there is no guarantee they will work on slackware-current or > any future stable release. > > Eric Thanks for the tip - I will give this a try on a 13.0 installation!
From: Tuxedo on 26 Dec 2009 08:36 On Dec 26, 12:39 pm, Henrik Carlqvist <Henrik.Carlqv...(a)deadspam.com> wrote: > Eric Hameleers <er...(a)sox.homeip.net> wrote: [...] > What about security patches? I suppose that unsupported packages will not > get any security patches? On the other hand as there is no longer any > upstream support for kde 3 there will probably not be much patches for the > official kde 3 packates in earlier versions of Slackware either. Thanks for the above note as well as your previous comments on whether to upgrade or not to upgrade. The answer to your question as to why I prefer 13.0 over 12.2 is indeed what you suggested: I do not know. Not having used either or having read or compared the release notes in detail, except for the window manager version difference, I guess my preference for a 13.0 version would be based on a notion that newer is better, or more specifically in software, the assumption that some things may last a bit longer in terms of compatibility with future applications. Otherwise, kde-3.5.10 sounds like the perfect window manager, no more updates, no more bugs, nothing new to learn. Finally I can get some real work done!
From: Eef Hartman on 29 Dec 2009 06:35 Henrik Carlqvist <Henrik.Carlqvist(a)deadspam.com> wrote: > Eric Hameleers <eric1(a)sox.homeip.net> wrote: >> Their status is "unsupported", meaning there is no guarantee they will >> work on slackware-current or any future stable release. > > What about security patches? I suppose that unsupported packages will not > get any security patches? No, they don't. It is an "as is" (then) compilation for 13.0 (both versions). > upstream support for kde 3 there will probably not be much patches for the > official kde 3 packates in earlier versions of Slackware either. There never were any for 12.2 either, even when 3.5.10 was still supported. The last KDE patch Pat supplied was for 12.1 (and KDE 3.5.9), in 2008: kdenetwork-3.5.9-i486-3_slack12.1.tgz And there were 3 updates for KDE 3.5.7 in Slackware 12.0 -- ******************************************************************* ** Eef Hartman, Delft University of Technology, dept. SSC/ICT ** ** e-mail: E.J.M.Hartman(a)tudelft.nl - phone: +31-15-278 82525 ** *******************************************************************
From: john on 30 Dec 2009 11:45 On Dec 29, 6:35 am, Eef Hartman <E.J.M.Hart...(a)tudelft.nl> wrote: > Henrik Carlqvist <Henrik.Carlqv...(a)deadspam.com> wrote: > > Eric Hameleers <er...(a)sox.homeip.net> wrote: > >> Their status is "unsupported", meaning there is no guarantee they will > >> work on slackware-current or any future stable release. > > > What about security patches? I suppose that unsupported packages will not > > get any security patches? > > No, they don't. It is an "as is" (then) compilation for 13.0 (both versions). > > > upstream support for kde 3 there will probably not be much patches for the > > official kde 3 packates in earlier versions of Slackware either. > > There never were any for 12.2 either, even when 3.5.10 was still supported. > The last KDE patch Pat supplied was for 12.1 (and KDE 3.5.9), in 2008: > kdenetwork-3.5.9-i486-3_slack12.1.tgz > And there were 3 updates for KDE 3.5.7 in Slackware 12.0 > -- > ******************************************************************* > ** Eef Hartman, Delft University of Technology, dept. SSC/ICT ** > ** e-mail: E.J.M.Hart...(a)tudelft.nl - phone: +31-15-278 82525 ** > ******************************************************************* The only reason I have for using 13 instead of 12.2 is Qt4, which is required by the latest versions of some applications such as Scribus. Just FYI I doubt if I will be ever ready for KDE 4. It is about as clunky as can be. Bad initial design can't be patched. I have gone over to XFCE and will stay with that GUI for as long as it is available. Someday someone or several someones will get the message and put KDE 4 in the bit bucket along with Vista and the other failed projects. John Culleton Slack since 1996 or thereabouts.
From: Tuxedo on 30 Dec 2009 20:16
john(a)wexfordpress.com wrote: [...] > The only reason I have for using 13 instead of 12.2 is Qt4, which is > required by the latest versions of some applications > such as Scribus. > > Just FYI I doubt if I will be ever ready for KDE 4. It is about as > clunky as can be. Bad initial design can't be patched. I have gone > over to XFCE and will stay with that GUI for as long as it is > available. Someday someone or several someones will get the message > and put KDE 4 in the bit bucket along with Vista and the other failed > projects. Same here. I doubt I will ever switch to KDE 4! There's a KDE 3 for Slackware 13 linked above in the thread. I just installed Slackware 13 but couldn't make X windows run with DRI as I don't master the fine art of xorg configuration, so I didn't get a chance to test this bundle. Instead, I will bluntly revert to Slackware 12.2 in order to run X windows in DRI mode. I believe my system has a fairly standard Intel on-board 82852/8255 GM Graphics Controller, but none of the auto-config tools, such as "X -configure" or "xorgsetup" generated an X windows config file with the result of direct graphic rendering working on the system. Does anyone here happen to have the same type of hardware and an xorg.conf file with DRI configured and working? My screen is 1024x768 True Color (60 Hz) although I'm not sure what vertical and horizontal refresh rates and other necessary values may be. In fact, I haven't found much documentation in relation to the graphics hardware and screen configuration for any Linux system. Alternatively, does anyone know of a procedure to run a Windows based driver in Slackware using some kind of third-party program wrapper application? I think the main file for the graphics driver in Windows XP is located in c:\windows\system32\drivers\ialmnt5.sys. This is in an ntfs partition on the same disk as my Slackware, mounted somewhere in /media/hda4/WINDOWS/.... As far as I understand, it is an "Intel Extreme Graphics 2" driver, which doesn't come with Windows itself but is supplied by Intel or whoever sells the hardware and then installed separately, also to speed up direct graphic rendering in Windows (without XP works sluggish). So far only the vesa powered X windows works for me in most Linux's for the hardware, which is a Samsung Q25 notebook. In fact, I found that the graphics of many distros are either broken while attempting to run DRI on this hardware. The effect is a kind of erratic screen flickering and other graphical display errors that seems to kick more or less in depending on what or how many applications are running at the same time. If left unattended, sooner or later the hardware would probably get damaged. An example of where graphics work including DRI is Knoppix 5. Knoppix uses an auto-generated xorg.conf for the i810 driver. Also, the exact same Knoppix generated xorg.conf file runs fine with DRI in Slackware 12.2, but not in Slackware 13 for some reason. I understand some X things has changed between the two versions. The graphics will work Ok with any window manager which doesn't require DRI, but of course, that doesn't include KDE, nor does it include running programs within any window manager that happens to require 3D effects. If anyone here has the same of type hardware using Slackware or another distro with hardware acceleration working, it would be much appreciated if you can kindly post a copy of your /etc/X11/xorg.conf in this thread. Many thanks, Tuxedo |