Updating packages with xfce in slackware

20-Nov-2017 07:58 by 8 Comments

Updating packages with xfce in slackware - top australian dating websites

sbopkg is an excellent frontend for the Slack repository.Slackware maintainers Eric “Alien Bob” Hameleers and Robby Workman also maintain high-quality repositories. One only needs to be run after installing a new font, the other after installing a new library; neither needs to be run every single boot.

Go to Slack and install When alsaconf asks for permission to modify modprobe.conf, grant it. First set up Ti Midity with my Ti Midity Slack Build.

Note, however, that kdm already has such support for every window manager under the sun, and thus no work should be necessary. Want to set up VLC to play RTSP streaming media in Firefox? They split the TV image up into two alternating sets of horizontal lines, called , and display the even set, then the odd set, then the even set, and so on.

For a media player, Alien Bob’s patent-encumbered version of the VLC media player will serve most people best. NTSC countries use 60Hz AC and therefore NTSC switches between fields 60 times per second. There are many resources about this, and Xiph’s Digital Media Primer for Geeks is currently the most entertaining. The x86 Wine package is for the 32-bit version of Slackware, and the x86-64 package is for the 64-bit version with a multilib subsystem set up.

After installing said window manager from source, add an entry for it in “/etc/X11/xinit” to get it to appear in . The “choose a program to handle this protocol” window will pop up. This is covered in the Mozillazine Knowledgebase’ Register protocol page.

As of Slackware 12.1, you’ll need an appropriate .desktop file in “/usr/share/apps/kdm/sessions” to get it to appear in kdm’s menus. If you see horizontal lines in your video, then read on: Interlaced TV standards such as NTSC and PAL are designed for countries that use AC power.

To use a Slack Build, you make it executable and run it, as root, in the same directory as its corresponding source tarball. Slack Builds are written to make this easy, and the most commonly changed flags are stored in variables initialized at their beginnings.

These include the following: In the past, most Slackware users built their packages from source, after downloading them from the package maintainers’ websites.

Installed packages are logged in “/var/log/packages”. If you look in Slackware’s /source tree, you will find source tarballs with . The Slack Builds are shell scripts for building the packages, while the .builds are for a package building program called slacktrack.

This makes upgrading or rebuilding Slackware’s packages very easy (just edit and rerun the Slack Builds).

I’m assuming a certain level of Slackware knowledge.

As is standard for Linux, these files are named with capital letters.

This uses a lot of CPU power, so make sure you disconnect the ports when you’re done.