http://pastebin.com/gy0MdPyR was a new adeskbar.install but it wasn't enough
to make a working adeskbar.
I downloaded adeskbar , extracted the packages, edited main.py changed python in the first line to python2, copied the adeskbar folder to usr/share/, copied default.conf to home/paul/.config/adeskbar/ and created a symlink:
ln -s /usr/share/adeskbar/adeskbar.sh /usr/bin/adeskbar
Had to install all the many python deps:python-keybinder python2-pyinotify python-pyalsaaudio python-vte python-xlib pyhon-gio python2-wnck python-gmen. But it works now!!
Monday, March 4, 2013
Autologin while having systemd in Arch
I have researched diverse options to realize autologin after systemd came to Arch.
The simplest way is to have slim installed and edit /etc/slim.conf . Change
#auto_login no
to: auto_login yes
and
#default_user live
to
default_user username
The simplest way is to have slim installed and edit /etc/slim.conf . Change
#auto_login no
to: auto_login yes
and
#default_user live
to
default_user username
Sunday, March 3, 2013
Packages from AUR need to be rebuild - Arch
Update warning from Arch:
To know which package need to be rebuild you can use pkgtools
After installation (#pacman -S pkgtools) do
Then do
to determine which packages are installed from AUR.
As the official packages are rebuild for you, you only have to rebuild the AUR packages.
For me it means I have to rebuild: cdcat fontmatrix qbittorrent sir syncbackup.
This is an example why pacman is so fantastic:
:: Replace qt with extra/qt4? [Y/n] y
resolving dependencies...
looking for inter-conflicts...
error: failed to prepare transaction (could not satisfy dependencies)
:: cdcat: requires qt
:: fontmatrix: requires qt>=4.3.0
:: qbittorrent: requires qt
:: sir: requires qt
:: syncbackup: requires qt
qt4 replaces qt
2013-03-01
A new qt4 package is in [extra]. This replaces the current qt package.
All packages depending on qt need to be rebuilt to depend on qt4. We have done this for all official packages, but you will need to rebuild packages installed from the AUR that depend on qt.
To know which package need to be rebuild you can use pkgtools
After installation (#pacman -S pkgtools) do
whoneeds qt
pacman -Qqm
As the official packages are rebuild for you, you only have to rebuild the AUR packages.
For me it means I have to rebuild: cdcat fontmatrix qbittorrent sir syncbackup.
This is an example why pacman is so fantastic:
:: Replace qt with extra/qt4? [Y/n] y
resolving dependencies...
looking for inter-conflicts...
error: failed to prepare transaction (could not satisfy dependencies)
:: cdcat: requires qt
:: fontmatrix: requires qt>=4.3.0
:: qbittorrent: requires qt
:: sir: requires qt
:: syncbackup: requires qt
Wednesday, February 27, 2013
What defines the qualities of a certain distro
When I installed Salix it was a new distro for me and it was interesting to note what made a difference for me in the process of getting to know a new Linux branch.
First you have to make a distinction between the different Linux branches; installing a different flavor of Debian or Arch does make a difference but the differences between Arch, Debian, Gentoo, Fedora and Slackware are more profound.
I made a wish list before about what my ideal distro would be:
1. systemd free,
2. rolling release ( I don't want a regular re-installation);
3. binaries, no need to build everything like in gentoo,
4. good dependency handling,
5. a good package manager ( I hate synaptic but updating in aptosid should be done in init 3 and works great, although slower than pacman.
6. not the latest packages are needed but also not too slow updating of packages.
Aptosid or siduction are the only ones that fit the full bill, but I am open to experiences of others and heard from Archvortex much good things about Slackware that I wanted to try it out. Although it doesn't have automatic dependency handling and much less binaries than deb and Arch. And it isn't a rolling release.
But there was one problem: Slack comes with Lilo and I hate Lilo from bad experiences in the past. I like grub legacy the best but can settle for grub2. Anyway I found a solution for the grub/lilo problem. As you can read here. I like to prepare the partition before the installation process with gparted; again after a bad experience with some partition manager ruining my rather complicated partition table. I like best to install from a liveCD, so I get a preview what the installation will look like and then to be able to partition form that liveCD (the extended partition has to be unmounted to do repartitioning). Even ArchBang doesn't have that option any more.
The version I installed first was Slackel, had problems booting the installation and retried with Salix. I had no clue if the problems were caused by some hardware incompatibility or because I did something wrong in the boot process (this was before I had installed the bootloader). That is another reason why a liveCD is nice, because then that possible problem of incompatibility can be excluded.
So what is important for me during or preparing installation are: the availability of a liveCD 2. preferable with gparted on it 3. choice of bootloaders.
I choose the LDXE version as this is closest to the openbox set up I always want to realize. With the *Box window manager I'm home; completely satisfied and no reason to look any further. Salix doesn't have a liveCD version of this one.
The Salix 13.37 OS LDXE set up is nice. Maybe I should have gone for the fluxbox version, but I was curious to see what they have made of it. And with gslapt and sourcery they made it quite user-friendly regarding package management.
And here we come to the second element of what makes a distro interesting and good.
How the system is configured. What I notice directly is that the video or the graphic card is not configured at its best; font rendering is mediocre, there is some lag in using some applications. The system is not so responsive as I 'm used to in aptosid and Archbang.
Also the way the sound card is configured gives some problems; I have to kill one program to get sound from another. The mixer (volti) doesn't work exactly as it should. And it is the same when installing all kinds of applications I face small problems.
The lack dependency handling gives a lot of problems. I'm only able to install fontmatrix after I install k3b. Viewnior is no problem to install but gthumb is. Google Chrome is only installed after quite some research and so on.
The best package manager (pacman) and package distribution system is at Arch's imho; with AUR and the official packages; the wonderful packer for building packages; the dependency handling in Arch is quite good. I have the impression much better than in Ubuntu where I faced a lot of problems, although that was when I started with Linux, so maybe I tried foolish things.. aptosid is also great in this respect.
So why I bother with Slackware?
Probably because of its conceptual clarity and the consequence they adhere to it.
The KISS principle, that was left by the Arch devs, is still a reality. The anti-fashionlike stability of the whole project attracts me too it, its anti-commercialism ( one of the reasons I lost interest in Ubuntu and was never attracted to RedHat, Mandriva or Fedora).
So they don't use systemd!!
What also is important in choosing a distro is its community and its products: forums and wiki. The Arch forums are very problematic as are the aptosid forums. Forums should be open and non-conformistic in the sense of open to new and critical questions. Diversification, dissent and experiment are essential to a thriving community.
The Arch wiki is great, although not as up to date as it used to be. I'm not ready to give an opinion on the Slackware community and documentation and forums. Great point of Salix is its Startup Guide that is also available as a free PDF download.
To be continued, I hope..
First you have to make a distinction between the different Linux branches; installing a different flavor of Debian or Arch does make a difference but the differences between Arch, Debian, Gentoo, Fedora and Slackware are more profound.
I made a wish list before about what my ideal distro would be:
1. systemd free,
2. rolling release ( I don't want a regular re-installation);
3. binaries, no need to build everything like in gentoo,
4. good dependency handling,
5. a good package manager ( I hate synaptic but updating in aptosid should be done in init 3 and works great, although slower than pacman.
6. not the latest packages are needed but also not too slow updating of packages.
Aptosid or siduction are the only ones that fit the full bill, but I am open to experiences of others and heard from Archvortex much good things about Slackware that I wanted to try it out. Although it doesn't have automatic dependency handling and much less binaries than deb and Arch. And it isn't a rolling release.
But there was one problem: Slack comes with Lilo and I hate Lilo from bad experiences in the past. I like grub legacy the best but can settle for grub2. Anyway I found a solution for the grub/lilo problem. As you can read here. I like to prepare the partition before the installation process with gparted; again after a bad experience with some partition manager ruining my rather complicated partition table. I like best to install from a liveCD, so I get a preview what the installation will look like and then to be able to partition form that liveCD (the extended partition has to be unmounted to do repartitioning). Even ArchBang doesn't have that option any more.
The version I installed first was Slackel, had problems booting the installation and retried with Salix. I had no clue if the problems were caused by some hardware incompatibility or because I did something wrong in the boot process (this was before I had installed the bootloader). That is another reason why a liveCD is nice, because then that possible problem of incompatibility can be excluded.
So what is important for me during or preparing installation are: the availability of a liveCD 2. preferable with gparted on it 3. choice of bootloaders.
I choose the LDXE version as this is closest to the openbox set up I always want to realize. With the *Box window manager I'm home; completely satisfied and no reason to look any further. Salix doesn't have a liveCD version of this one.
The Salix 13.37 OS LDXE set up is nice. Maybe I should have gone for the fluxbox version, but I was curious to see what they have made of it. And with gslapt and sourcery they made it quite user-friendly regarding package management.
And here we come to the second element of what makes a distro interesting and good.
How the system is configured. What I notice directly is that the video or the graphic card is not configured at its best; font rendering is mediocre, there is some lag in using some applications. The system is not so responsive as I 'm used to in aptosid and Archbang.
Also the way the sound card is configured gives some problems; I have to kill one program to get sound from another. The mixer (volti) doesn't work exactly as it should. And it is the same when installing all kinds of applications I face small problems.
The lack dependency handling gives a lot of problems. I'm only able to install fontmatrix after I install k3b. Viewnior is no problem to install but gthumb is. Google Chrome is only installed after quite some research and so on.
The best package manager (pacman) and package distribution system is at Arch's imho; with AUR and the official packages; the wonderful packer for building packages; the dependency handling in Arch is quite good. I have the impression much better than in Ubuntu where I faced a lot of problems, although that was when I started with Linux, so maybe I tried foolish things.. aptosid is also great in this respect.
So why I bother with Slackware?
Probably because of its conceptual clarity and the consequence they adhere to it.
The KISS principle, that was left by the Arch devs, is still a reality. The anti-fashionlike stability of the whole project attracts me too it, its anti-commercialism ( one of the reasons I lost interest in Ubuntu and was never attracted to RedHat, Mandriva or Fedora).
So they don't use systemd!!
What also is important in choosing a distro is its community and its products: forums and wiki. The Arch forums are very problematic as are the aptosid forums. Forums should be open and non-conformistic in the sense of open to new and critical questions. Diversification, dissent and experiment are essential to a thriving community.
The Arch wiki is great, although not as up to date as it used to be. I'm not ready to give an opinion on the Slackware community and documentation and forums. Great point of Salix is its Startup Guide that is also available as a free PDF download.
To be continued, I hope..
Tuesday, February 26, 2013
Installing packages in Salix
Gslapt is a nice
addition to working in the terminal and sourcery is nice for working
with Slackbuilds. The best program seems for those sbopkg as it gives you a lot of information about available packages and available uploads and more.
Sbopkg can be found at http://code.google.com/p/sbopkg/ Download the latest version (sbopkg-version-noarch-1.tgz) to your Desktop. Open a terminal: and do as root: # installpkg sbopkg-version-noarch.
Dependency handling or better the lack of it is the big drawback of Slackware and stability seems less than in Debian or Arch.
Sbopkg can be found at http://code.google.com/p/sbopkg/ Download the latest version (sbopkg-version-noarch-1.tgz) to your Desktop. Open a terminal: and do as root: # installpkg sbopkg-version-noarch.
Dependency handling or better the lack of it is the big drawback of Slackware and stability seems less than in Debian or Arch.
Install Google Chrome slackware
First install the dependencies with gslapt or slapt-get -i
GConf ORBit2 google-chrome-pam-solibs
Then go to the Google Chrome site:
http://www.google.com/chrome
Click the download button, and select either:
32 bit .deb (for Debian/Ubuntu)or 64 bit .deb (for Debian/Ubuntu)
Download the SlackBuild from here and execute it as root
while being in the same folder as the just downloaded Chrome deb.
It will convert the deb to a txz in your tmp folder.If all goes well you get:
Slackware package /tmp/google-chrome-25.0.1364.97-x86_64-1.txz created.
Now do again as root: # upgradepkg --install-new google-chrome-25.0.1364.97-x86_64-1.txz
Output:
+============================================
| Installing new package ./google-chrome-25.0.1364.97-x86_64-1.txz
+============================================
Verifying package google-chrome-25.0.1364.97-x86_64-1.txz.
Installing package google-chrome-25.0.1364.97-x86_64-1.txz:
PACKAGE DESCRIPTION:
Executing install script for google-chrome-25.0.1364.97-x86_64-1.txz.
Package google-chrome-25.0.1364.97-x86_64-1.txz installed.
Monday, February 25, 2013
Installing Salix without Lilo but with Grub2
I wanted to try slcakware but without the dreaded Lilo with which I have bad experiences.
After preparing the installation partition with gparted (with a differentCD) I installed without installing the bootloader.
Rebooted with the install cdrom and this boot specification:
huge.s root=/dev/sda15 rdinit= ro
Note the space after the last = sign.
In this way I was able to boot into the new installation.
Installed grub2 after updating the repos:
slapt-get -u && slapt-get -i grub2
Then: #grub-install /dev/sda15
Then updated grub in my main Archbang system with grub-optimizer.
After that I updated the Slackbuilds repolist with slapt-src -u and
installed my fav filemanager Spacefm with: slapt-src -i spacefm.
I failed to build chromium, see in next post how I succeeded with Google Chrome.
After preparing the installation partition with gparted (with a differentCD) I installed without installing the bootloader.
Rebooted with the install cdrom and this boot specification:
huge.s root=/dev/sda15 rdinit= ro
Note the space after the last = sign.
In this way I was able to boot into the new installation.
Installed grub2 after updating the repos:
slapt-get -u && slapt-get -i grub2
Then: #grub-install /dev/sda15
Then updated grub in my main Archbang system with grub-optimizer.
After that I updated the Slackbuilds repolist with slapt-src -u and
installed my fav filemanager Spacefm with: slapt-src -i spacefm.
I failed to build chromium, see in next post how I succeeded with Google Chrome.
Subscribe to:
Posts (Atom)