Comments for Pimp my Slack! http://slackware.ponce.cc/blog Ponce Slackware Stuff Thu, 03 Nov 2011 14:00:16 +0000 hourly 1 http://wordpress.org/?v=3.3.1 Comment on easily build yourself LXDE with sbopkg by ponce http://slackware.ponce.cc/blog/2010/08/23/easily-build-yourself-lxde-with-sbopkg/comment-page-1/#comment-3022 ponce Thu, 03 Nov 2011 14:00:16 +0000 http://slackware.ponce.cc/blog/?p=178#comment-3022 https://wiki.archlinux.org/index.php/Openbox#Openbox_as_a_stand-alone_WM https://wiki.archlinux.org/index.php/Openbox#Openbox_as_a_stand-alone_WM

]]> Comment on easily build yourself LXDE with sbopkg by voltron http://slackware.ponce.cc/blog/2010/08/23/easily-build-yourself-lxde-with-sbopkg/comment-page-1/#comment-2981 voltron Tue, 25 Oct 2011 09:45:27 +0000 http://slackware.ponce.cc/blog/?p=178#comment-2981 Great work, thanks. Is it possible to use this packages to build pure OpenBox environment with automount support in PCManFM? As I understand, I need to download and install only openbox and pcmanfm packages with dependencies (udisks et al). But what I should add to the .xinitrc file: exec openbox-session or ck-launch-session openbox-session? Great work, thanks.
Is it possible to use this packages to build pure OpenBox environment with automount support in PCManFM? As I understand, I need to download and install only openbox and pcmanfm packages with dependencies (udisks et al). But what I should add to the .xinitrc file: exec openbox-session or ck-launch-session openbox-session?

]]> Comment on easily build yourself LXDE with sbopkg by ponce http://slackware.ponce.cc/blog/2010/08/23/easily-build-yourself-lxde-with-sbopkg/comment-page-1/#comment-2842 ponce Wed, 12 Oct 2011 05:50:03 +0000 http://slackware.ponce.cc/blog/?p=178#comment-2842 you're just too kind, I don't deserve that :) you’re just too kind, I don’t deserve that :)

]]> Comment on easily build yourself LXDE with sbopkg by eXpander http://slackware.ponce.cc/blog/2010/08/23/easily-build-yourself-lxde-with-sbopkg/comment-page-1/#comment-2835 eXpander Tue, 11 Oct 2011 14:26:10 +0000 http://slackware.ponce.cc/blog/?p=178#comment-2835 Man you are the Prince of Slackware. Thanks. Man you are the Prince of Slackware. Thanks.

]]> Comment on lxc containers on slackware 13.37 by ponce http://slackware.ponce.cc/blog/2011/07/17/lxc-containers/comment-page-1/#comment-2748 ponce Fri, 16 Sep 2011 16:08:52 +0000 http://slackware.ponce.cc/blog/?p=267#comment-2748 <em><strong>1:</strong></em> the old package set (the list, not the packages) shouldn't be cached, it should use the PACKAGES variable as you export it, like in the example at the end of the post; <em><strong>2 and 3:</strong></em> this post has been done to let people start playing with lxc containers, but the installation procedure I come up with has to be revised. I thought about it and prepared <a href="https://raw.github.com/Ponce/lxc/lxc-slackware-slackpkg/templates/lxc-slackware.in" rel="nofollow">another template</a> that doesn't use <strong>wget</strong> and <strong>installpkg</strong> but instead uses <strong>slackpkg</strong> to install the packages in a folder: slackpkg is the optimal choice for this, because it supports cleaner (and working) templates, it checks downloaded packages, it supports local mirrors, etc. But unfortunately, in its current version it doesn't fully support installing packages in a $ROOT folder in the filesystem (installpkg can do it) nor the possibility to specify a custom folder for the configuration files: I wrote two small patches for let it do this that I proposed (hope they're ok) to Piter Punk, author and maintainer of the utility. You can try an <a href="http://ponce.cc/slackware/testing/other/slackpkg-2.82.0-noarch-6ponce.txz" rel="nofollow">already patched slackpkg</a> with this feature integrated, to use with the template above on the host where you create the containers. the correct syntax for using a local mirror with slackpkg is (example with slackware64-13.37) <code>cdrom://path/to/slackware64-13.37/</code> 1: the old package set (the list, not the packages) shouldn’t be cached, it should use the PACKAGES variable as you export it, like in the example at the end of the post;

2 and 3: this post has been done to let people start playing with lxc containers, but the installation procedure I come up with has to be revised.
I thought about it and prepared another template that doesn’t use wget and installpkg but instead uses slackpkg to install the packages in a folder: slackpkg is the optimal choice for this, because it supports cleaner (and working) templates, it checks downloaded packages, it supports local mirrors, etc.
But unfortunately, in its current version it doesn’t fully support installing packages in a $ROOT folder in the filesystem (installpkg can do it) nor the possibility to specify a custom folder for the configuration files: I wrote two small patches for let it do this that I proposed (hope they’re ok) to Piter Punk, author and maintainer of the utility.
You can try an already patched slackpkg with this feature integrated, to use with the template above on the host where you create the containers.

the correct syntax for using a local mirror with slackpkg is (example with slackware64-13.37)
cdrom://path/to/slackware64-13.37/

]]> Comment on lxc containers on slackware 13.37 by FeyFre http://slackware.ponce.cc/blog/2011/07/17/lxc-containers/comment-page-1/#comment-2747 FeyFre Fri, 16 Sep 2011 14:50:34 +0000 http://slackware.ponce.cc/blog/?p=267#comment-2747 Good articel, and good template. At second or third retry I have managed to setup and run container. Now have some questions and notes: 1. In first retry I build contain from unmodified container - all done good. As the second retry I decide to add some packages into template(particularly mc and nc), but it seem container builder does not noticed that, and built new container with old package set(cached). Is it possible add validation checks? 2. I'm working in 32-bit environment. So template sets arch=i486 , but I have found 7 packages in slackware-13.37 with arch part equal i386 in package name(particularly n/nc-1.10-i386.txz which I tried to add). Just giving notice. 3. I have local mirror of slackware packages so I want to target package source as local path i.e. MIRROR=/mnt/slackware lxc-create -n test -t slackware -f /path/to/config but template uses wget which does not understand such path. It would be good to have such ability. Good articel, and good template. At second or third retry I have managed to setup and run container.
Now have some questions and notes:
1. In first retry I build contain from unmodified container – all done good. As the second retry I decide to add some packages into template(particularly mc and nc), but it seem container builder does not noticed that, and built new container with old package set(cached). Is it possible add validation checks?
2. I’m working in 32-bit environment. So template sets arch=i486 , but I have found 7 packages in slackware-13.37 with arch part equal i386 in package name(particularly n/nc-1.10-i386.txz which I tried to add). Just giving notice.
3. I have local mirror of slackware packages so I want to target package source as local path i.e. MIRROR=/mnt/slackware lxc-create -n test -t slackware -f /path/to/config but template uses wget which does not understand such path. It would be good to have such ability.

]]> Comment on lxc containers on slackware 13.37 by Chroot with X http://slackware.ponce.cc/blog/2011/07/17/lxc-containers/comment-page-1/#comment-2693 Chroot with X Sat, 27 Aug 2011 14:26:33 +0000 http://slackware.ponce.cc/blog/?p=267#comment-2693 [...] Yeah ponce, I've had a look at lxc and looks like it's what I'm looking for, thanks. Your blog was helpful too http://slackware.ponce.cc/blog/2011/...xc-containers/ [...] [...] Yeah ponce, I've had a look at lxc and looks like it's what I'm looking for, thanks. Your blog was helpful too http://slackware.ponce.cc/blog/2011/…xc-containers/ [...]

]]> Comment on lxc containers on slackware 13.37 by ponce http://slackware.ponce.cc/blog/2011/07/17/lxc-containers/comment-page-1/#comment-2574 ponce Mon, 18 Jul 2011 21:11:52 +0000 http://slackware.ponce.cc/blog/?p=267#comment-2574 - for OpenVZ you need kernel patches, LXC uses cgroups, already in vanilla kernels; - I don't reccomend one or the other, as I use both :D but I personally prefeer what's already available in slackware ;) ; - LXC has a smaller userbase as it's younger than OpenVZ, it lacks some extensive documentation and some tools that OpenVZ already has, but the fun should be also getting into the internals and manage to do something in that direction :) you can write comments also in italian, but obviously posting in english will increase the chance that other people partecipate in the discussion with help and ideas ;) - for OpenVZ you need kernel patches, LXC uses cgroups, already in vanilla kernels;
- I don’t reccomend one or the other, as I use both :D but I personally prefeer what’s already available in slackware ;) ;
- LXC has a smaller userbase as it’s younger than OpenVZ, it lacks some extensive documentation and some tools that OpenVZ already has, but the fun should be also getting into the internals and manage to do something in that direction :)

you can write comments also in italian, but obviously posting in english will increase the chance that other people partecipate in the discussion with help and ideas ;)

]]> Comment on lxc containers on slackware 13.37 by danix http://slackware.ponce.cc/blog/2011/07/17/lxc-containers/comment-page-1/#comment-2571 danix Mon, 18 Jul 2011 18:22:31 +0000 http://slackware.ponce.cc/blog/?p=267#comment-2571 Hi ponce, I don't know if you like comments in italian, so I'll write it in english.. :P what are the main differences between lxc and openvz?? why would you recomment one instead of another? Hi ponce, I don’t know if you like comments in italian, so I’ll write it in english.. :P
what are the main differences between lxc and openvz?? why would you recomment one instead of another?

]]> Comment on lxc containers on slackware 13.37 by ponce http://slackware.ponce.cc/blog/2011/07/17/lxc-containers/comment-page-1/#comment-2568 ponce Mon, 18 Jul 2011 08:22:24 +0000 http://slackware.ponce.cc/blog/?p=267#comment-2568 sure, but you already know I will be lan-partying with ET all the time, don't you? ;) sure, but you already know I will be lan-partying with ET all the time, don’t you? ;)

]]>