Main menu:

Sponsoring

Please consider a small donation:

 

Also appreciated: support me by clicking the ads (costs nothing) :-)

 

Or you can donate bitcoin:

 

Thanks to TekLinks in Birmingham, AL, for providing colocation and bandwidth.

Page Rank

Fame

FOSS Force Best Blog--2013 Award

Recent posts

Recent comments

About

Hi!

 

I am Eric Hameleers, or AlienBOB as Slackware users know me. I maintain a Wiki, and a website where I publish Slackware scripts and other goodies, but I lacked a place where I could comment freely on all my activities.

 

This nice WordPress blog using sqlite database proved as portable as my Wiki, and I am glad I created it.

 

I hope you find what you search for. If you want to give feedback and don’t want to write a comment on the blog, then you can always email me: alien at slackware dot com.

 

Comments

Comment from Sid Stautzenberger
Posted: September 8, 2008 at 05:55

Very good website. I’m a long time user of Slackware and I really appreciate the extra packages and scripts that you provide.
Sid

Comment from Willy Sudiarto Raharjo
Posted: September 13, 2008 at 08:35

It seems that more and more Slackware users are open to the public :)

Comment from AlienBOB
Posted: September 13, 2008 at 13:08

I think it is important to show people what goes on in the world of Slackware. We have a semi-closed development model here (only one person commits changes to the tree) and this is often used in discussions to show that Slackware’s development is “non-democratic”. There is no bugzilla, no mailing lists where people can interact with the development team.
So, I try to address this “ivory tower” feeling by showing more about myself and by writing about Slackware in this blog.
My posts on Linuxquestions.org and the articles in my Wiki are focused on helping people by closing the knowledge gaps. By starting a blog I try to reach out to the community in a very different way.

Thanks both of you for taking the time to comment :-)

Eric

Comment from antler
Posted: February 19, 2009 at 04:15

Thank you for all your Slackware-related work, AlienBOB. Your scripts and your how-tos help me a lot. I really appreciate the time you devote to making Slackware more accessible to both new and experienced users alike.

I regard you as a pillar in the community and often think I’m using alien technology whenever I run your scripts. I don’t know how they work, I just know they work well.

So, thanks again.

antler

Comment from Cuetzpallin
Posted: March 4, 2009 at 22:17

Hello Eric:

Nice site, I think you are one of the Pillar of this distribution.
I follow your slackbuilds releases and also from slackbuild.org

Thank you four your time and share your knowledge.

Jose

Comment from Robby Workman
Posted: March 30, 2009 at 19:12

Eric, you’re my hero. ;-)

Comment from Ken
Posted: May 4, 2009 at 04:29

Eric,

I love the site and visit often. How can I get involved in the Slackware development process, I’d like to contribute or help if possible. I know that it’s a close knit group, any pointers?

Thanks,

Ken

Comment from alienbob
Posted: May 4, 2009 at 16:25

Hi Ken

Slackware has no “open development” in the sense that the core team works on Slackware in private. But input from the community is always welcome, and the core team has grown over the past years by accepting several frequent contributors of patches, packages, scripts and ideas (me included).
The best you can do as an “outsider” is install slackware-current, work with it, find bugs, solve these and submit the patches to Pat Volkerding or mention your ideas in the ##slackware channel on Freenode IRC, and join the community at http://www.linuxquestions.org/questions/slackware-14/.
You’ve probably seen in the ChangeLog.txt that appreciation for good bugfixes is shown by mentioning the contributor in the log.

Comment from Bruce Hill
Posted: July 2, 2009 at 08:35

Eric,

If it weren\’t for you, we probably would have gone back to … the darkside. Thanks for your help all these years, and for opening up the World of Slackware to us.

You have truly given sacrificially, without asking for anything in return … and often not getting it. Did Robby even buy you a meal in Brazil?

Best regards,
Bruce

Comment from John
Posted: September 27, 2009 at 21:07

Hi Eric,

Just added the compat libraries to my Slackware system, following your instructions – all went well! Thanks for that.

I do have a problem though: It seems that there is no provision to update /etc/pango/pango.modules. This files is updated on reboot (I think), and contains only links to the 64 bit modules for Pango.

The net result is that Google Earth won’t install (maybe others too), as this installer uses 32 bit packages.

Did you ever stumble over this problem?

Again, thanks for the 32 bit instructions.

Comment from alienbob
Posted: September 27, 2009 at 22:54

Hi John

If you have an up-to-date Slackware64 13.0 you should find that the boot script “/etc/rc.d/rc.M” calls “update-pango-querymodules”. That script regognizes a multilib setup ad will update the pango modules for i486 as well as x86_64 architectures.
You should be aware that the 32bit directory in Slackware 13.0 is now “/etc/pango/i486/pango.modules”. Did you merge all the *.new files (in case you did an upgrade instead of a fresh install)?

Comment from Norton Luiz
Posted: November 1, 2009 at 08:49

Hi, Eric

Good job on slackware and i hope long years with project.

Comment from jaredan
Posted: November 6, 2009 at 12:55

Hello Eric,

I just wanted to drop by and say thank you very much with the great work on Slackware. The new computers are starting to ship with x86_64 by default and I really don’t know what would’ve happen without you. Please keep up the great work!

Comment from gar0t0
Posted: November 15, 2009 at 08:03

Hi Eric,

thank you for all scripts and packages, You make a great work on slackware and the community :)

Thanks you
gar0t0

Comment from sid wilroy
Posted: November 18, 2009 at 15:57

Thanks a ton for your contributions on linuxquestions.org – I had a sendmail issue and your advice fixed it…

Comment from rogue_coder
Posted: November 18, 2009 at 19:00

Your article on a multilib setup for Slackware64 was great!

Comment from sassybax
Posted: November 27, 2009 at 07:32

AlienBOB, you kinda look like the Mac guy.

Comment from John H
Posted: December 12, 2009 at 20:50

Thank you for doing an absolutely fantastic job with your multilib setup! Apart from a few minor problems – because I hadn’t RTFMed carefully enough, it was a breeze getting it set up.
Do you still use rsnapshot for your backups? I have been looking at the backup solutions out there, and to say I am more than a little confused is an understatement!
Once again thank you for all your efforts to make Slackware the great distro it is!

Comment from jaredan
Posted: December 24, 2009 at 11:35

Thank you for the multilib setup tutorial for slackware64 but I wish it would be enabled by default. Seems to be a lot of trouble for some odd reason in not including it since most of us would need it anyway.

Comment from alienbob
Posted: December 24, 2009 at 15:49

Hi Jaredan

Slackware64 is, and will probably remain, a pure 64-bit distribution. We took good care to make it easy adding 32-bit support on top (i.e. make it multilib).
If you really can not do without 32-bit software, perhaps the “normal” 32-bit Slackware would be better for you?

Cheers, Eric

Comment from phrag
Posted: December 31, 2009 at 14:17

nice site mate, keep up the good work =)

Comment from tim (timsoft)
Posted: February 10, 2010 at 17:42

the links on the right hand side on your blog all show a tool-tip saying they were created in 1970. – i presume this is a default 0 for the date value, so thought i’d mention it in case it is considered a bug.

Comment from Sub
Posted: February 15, 2010 at 20:21

Hello AlienBOB and thanks for the great work you’ve done!

Right now I’m playing with KDE 4.4.0 and just found that the kio_sftp is not compiled. I searched the Internet and found this http://forum.kde.org/viewtopic.php?f=18&t=84694&start=0 :
“It is possible that libssh was not available when your distribution configured and built the KDE 4.4 Beta packages.”

Is it possible to be added in a future package build?

Thanks,
Sub

Comment from neuronos
Posted: February 20, 2010 at 10:17

Salut AlienBOB ! Salve Slakware !

i’m from Romania
i try live slax, zenwalk, mint, kiwi and installed ubuntu !
Those build on Slakware i like the most !
It work so fast even on USB much faster than ubuntu on hard drive !
I’m a neuro-null and i was not able to instal a persistant firewall, IM, VoIP on live distributin based on Slakware !

Cu respect !

Comment from Станислав Атанасов
Posted: March 15, 2010 at 14:56

Hi, AlienBOB can I ask you fo a favour?
I’m starting a slackware wiki in my native language. Can I use materials from yours?

Comment from alienbob
Posted: March 19, 2010 at 12:14

Sure, if you copy (parts of) my articles and write in a footnote where you obtained your information (link to my original article) than that would be no problem at all.

Eric

Comment from Vedette
Posted: May 6, 2010 at 14:28

Slackware users are like cancer, spreading and spreading. I like it too.

Slackware rocks!

Comment from samac
Posted: May 9, 2010 at 09:44

Hi, will your 32-bit compatibility layer be re-compiled with the 2.6.33.x kernel, glibc, gcc & binutils that are included in the Slackware 13.1 release?

Comment from alienbob
Posted: May 11, 2010 at 12:35

@samac: there is nothing to be recompiled, because all those compatibility packages are created from original 32bit packages. You can do that yourself if you want, or wait for Slackware 13.1

Comment from samac
Posted: May 11, 2010 at 14:08

Sorry I probably used the wrong terminology, not the libraries but the gcc and glibc bit of the 32-bit compatibility.

samac

Comment from alienbob
Posted: May 13, 2010 at 16:09

The multilib versions of the gcc and glibc packages will be rebuilt or upgraded every time Slackware’s original packages are rebuilt or upgraded. You can get the versions of these packages compatible with Slackware 13.1 (mine were built at the same time as those in Slackware-current) from here: http://slackware.com/~alien/multilib/13.1/

Eric

Comment from Darmawan
Posted: May 14, 2010 at 14:46

Just dropping by to say thanks for the multilib articles, hints and packages. This is very helpful as I’m migrating from Slamd64 12.1 to Slackware64. Well, the glibc in Slamd64 is not thread safe, which is why I decided to migrate ;).

Comment from Hasan SAHIN
Posted: May 18, 2010 at 09:02

Hi Eric,
I believe Slackware will never die :)
and also I always wanted to have a bugzilla, development team, development list and etc…

Comment from alienbob
Posted: May 18, 2010 at 10:00

Hi Hasan

What will never change as long as Pat Volkerding maintains Slackware is that there will not be a public bugtracker or a community based development team like Debian has for instance.

Eric

Comment from Hasan SAHIN
Posted: May 19, 2010 at 07:58

Yes, unfortunatelly you are right :/
So I’d like to ask a question; if you were founder of slackware, do you have any idea above-mentioned issuies?

Comment from Paul Harper
Posted: May 30, 2010 at 03:48

I just want to thank you for your assistance in the past with DM-Crypt and LUKS.

Slackware while challenging initially is well documented and has a great community.

Comment from Russ Whitaker
Posted: June 6, 2010 at 03:24

I’ve been using your mirror script lately – very nice.

Years ago I sent Pat an email suggesting a change from i386 to i486. He replied, pooh-poohing the idea. Six months later he went to i486. Now I think it is about time to go to i586. Makes a nice speed increase.

On the coreboot.org’s mailing list someone commented he was having trouble with gcc-4.4.
So I tried using gcc-4.4.4 to compile glibc with
march=i586. It quit with a strange error message.
Making no other changes I switched to gcc-4.3.5.
Compiled fine, passed the test suite, installed it and it’s working.

That’s it for now.
Russ

Comment from grissiom
Posted: June 8, 2010 at 13:30

When I submit a comment on your blog in a recent post, I forgot to enter the Security Code. But the my comment appeared on the page… I think it’s a bug ;-)

Comment from grissiom
Posted: June 8, 2010 at 13:33

I succeeded to post last comment without entering Security Code :P

Comment from Wed
Posted: July 10, 2010 at 10:56

Your link to the PXE-boot seems dead

Comment from C. Wizard
Posted: July 23, 2010 at 02:51

AlienBob,
Does your latest WINE build now support sound?
Many Thanks.

Comment from slack fan
Posted: August 2, 2010 at 17:10

I came across this comment, and would like to invite your attention to reply to this comment. many are looking forward to your reply.

Comment from alienbob
Posted: August 2, 2010 at 22:09

Ay yes, I had seen that site before. It aggregates articles that have been published by other people before. I had not seen nor expected that someone would post a comment there.

I think the reply is unnecessarily harsh. It;’s OK if you do not like Slackware – for whatever reason. But there is no need for all this anger. I do not force you to use Slackware… my article was meant to make you curious about it and risk a trial run. And for people who already use Slackware, it was meant to provide some more background about myself, my role as a Slackware team member and Slackware in general.

Even though Acid_Test may be right about Kword – the Koffice suite went through a major re-write – I think the KDE4 version of Koffice was worth adding to give it more exposure. This is not a core part of Slackware we are talking about and there are alternatives if you are not happy with it. Sticking with the KDE3 version of koffice – or even, sticking with KDE3 – would not have made any sense. Those programs are not being developed any longer. If you need KDE3 for its functionality or its (perceived) stability, then by all means stay with Slackware 12.2. That release of Slackware gets its security upgrades just as quickly as 13.1.

The rant about kpackage and knetworkmanager strike me as strange. We do not endorse kpackage, and its developers never contacted any of the Slackware team (to my best knowledge) in order to co-operate and make it actually work. And knetworkmanager is pretty useless without networkmanager which we do not ship.

And what about PAM? We did not “re-write” software to get rid of PAM. Functionality was added to PolicyKit (by a Slackware user) to allow the use of another authentication backend than just PAM. I thought that was brilliant, and the patch has since then been incorporated into the PolicyKit source tree. That is how free software development works – by co-operating and enhancing stuff!

You know, I have been working with KDE4 exclusively as my Linux desktop environment since summer of 2008. The 2008 release had its quirks, but I could work around them, and since then a lot of effort went into its development to make it an absolutely _stable_ environment to work in. I wonder if Acid_Test has been running Slackware 13.x at all. If you do not like KDE, there is a choice! Use XFCE, or if that is too barebones for your tastes, get GnomeSlackBuild. It’s not like we do not have an active community where you can seek assistance if things don’t work for you.

However, it _really_ does not help to throw about all these insinuations and innuendo accusations. I wrote this response only because you asked for it ‘slack fan’, and because you deserve an answer. Otherwise I would just have ignored that post if I had come across it.
Trolls are everywhere.

Eric

Comment from alienbob
Posted: August 3, 2010 at 11:41

@linux fan:

Apparently the moderator of that site decided not to post my comment there, in which I point to this blog for a further discussion. A bit of a shame really. If you want to post a comment over there to tell Acid_Test that my reaction is here, that may help.

Eric

Comment from http://pearlin.info
Posted: August 5, 2010 at 12:08

hi,

your comments are posted on http://pearlin.info by the webmaster

Comment from Rajat
Posted: August 15, 2010 at 09:12

Hey AliuenBOB ….
I don’t have words to thank you…Don’t know what I would have done without your wiki and multilib packages.
Slackware Rules !!

Comment from Rajat
Posted: August 15, 2010 at 09:14

Sorry for the Spelling mistake :P

Comment from William B. Doyle
Posted: August 29, 2010 at 02:43

Okay, now I have to do my homework since I found this by accident. What the heck is “slackware”??? Never heard of it-just an enduser of stuff not a developer. I’ll google it and find out. Wow, a whole new world here…

Comment from James Mowery
Posted: September 6, 2010 at 08:13

Hello,

I was wondering if you accept guest post for your blog. If you do, I would like to submit a few. You can see a sample of my work at LaptopComputers.org under the author James Mowery. I’ve also written for several high-profile blogs like Mashable, Performancing, and CMSWire. Thank you for your time.

- James

Comment from staticcola
Posted: October 9, 2010 at 17:10

Have you considered starting your own fork of Slackware? Your versions of the SlackBuild’s are highly functional when compared to the distributions’ and SlackBuild.org’s versions. A high level of automation is nice.

Comment from alienbob
Posted: October 9, 2010 at 18:48

@staticcola -
Why should I do such a thing? Since I am already member of the core Slackware team, why would I break up and create a fork?

I have no desire to do so and scatter the Slackware community even more.

Eric

Comment from alternative health
Posted: October 27, 2010 at 07:52

Thank you for doing an absolutely fantastic job for slackware.. thanks you provide a good information about the blog as well as you are accepting guest posts also thats very fine to us…

Comment from home interiors
Posted: October 28, 2010 at 13:15

Can you please provide your blog details, then we can follow your blog for slackware news. I was seen here you are accepting guest posting in your blogs.

Comment from alienbob
Posted: October 29, 2010 at 15:21

I said I was considering guest postings but have not decided yet. And seeing the hidden spam attempt by linking your names to commercial sites, I will not likely say ‘yes’ either. Possibly I will even remove the previous two comments.

Eric

Comment from Ken Acland
Posted: December 9, 2010 at 12:08

Hi Eric,

Just calling to express my thanks for your rc scripts. My Latitude C400 is better for my legs than my Win98 desktop. After switching to static IPs I had the problem that I could access my LAN if I stopped eth0, but I couldn’t browse. Your scripts have fixed it, but I still don’t know what was spooking Firefox & Konqueror. Thanks, Ken.

Comment from Zhen
Posted: December 27, 2010 at 10:24

THANK YOU VERY MUCH for your labour, your advices help.
I am a beginner in Slackware ,english too bad know beside me on computer is installed Slackware13.1. For interest has installed VirtualBox4 and created the virtual machine (video 128 Mb and RAM 1024 Mb) with Slackware13.1×86 current. XFCE works fine, but KDE 4.5.4 gives the mistake to segmentings and is not loaded.Prompt please that possible to do.

Comment from Ceriousmall
Posted: January 28, 2011 at 05:34

Hey, I’m a Slackware user now studying C and when I’ve improved I would like to contribute to Slackware development.

Comment from Jason Sizemore
Posted: January 28, 2011 at 19:10

Thanks for the scripts and the work on Slackware

Comment from Carlos Morales
Posted: February 21, 2011 at 19:50

Hello, I’ve a little observation, the only thing I have noticed Slackware lacks is a dlna server package; I would recommend adding a build for some good package for example minidlna is a good and light (very basic) project or mediatomb also, which is another c++ developed package which might be added.

In another side, thanks a lot for all your work!

Comment from alienbob
Posted: February 21, 2011 at 20:03

Hi Carlos

I have a package for minidlna myself since I used it: http://slackware.com/~alien/slackbuilds/minidlna/ but since then I have been working with mediatomb for which you’ll find a SlackBuild here: http://slackbuilds.org/repository/13.1/network/mediatomb/ and a sbopkg (see http://sbopkg.org/) build queue-file for mediatomb is here: http://gitorious.org/sbopkg-slackware-queues/sbopkg-slackware-queues/trees/master .

Cheers, Eric

Comment from Mike
Posted: February 22, 2011 at 22:50

Hello there, i’m using your kde 4.6 for slackware current, but now i’m having problems with gtk apps, i remember kde had a “gtk styles and fonts” option on system preferences but i can’t find it on kde 4.6. am i missing something? do i need to install something else?

Comment from Carlos Morales
Posted: February 24, 2011 at 01:46

Hi again Eric, many thanks for the links! :)

btw, do you have any plans to develop a slackpkg-compat32 version? (so a simple update/upgrade process would keep the 32bit libs synced)

Best wishes,
Carlos

Comment from Hard Drive Recovery
Posted: February 28, 2011 at 00:12

Been a huge supporter of slackware since day one. Love your KDE work. Just wanted to give kudos to a really great project.

Thanks,
Maureen

Comment from steve
Posted: March 11, 2011 at 09:35

Hi Eric, just want to give you lots of encouragement to keep up the good work! I’m a long-time slackware user, software developer, slack is the only linux distribution I can stand using. Really really love the kde 4.6 stuff, using it as my main work desktop. Also better say a big thanks to Pat V while I’m here! Cheers!

Comment from krios
Posted: April 4, 2011 at 02:06

Thank you

Comment from V. T. Eric Layton
Posted: April 28, 2011 at 23:47

Eric,

Thanks for all that you do. You and Robby and others put a face on Slackware and make it tad more approachable by the non-guru GNU/Linux user.

Regards,

~Eric, the Nocturnal Slacker

Comment from Brian
Posted: May 25, 2011 at 11:46

Hi,
Nice post, You make a great work on slackware and the community. So thank you.
Sincerelly

Locksmiths Kensington

Comment from Anonymous Coward
Posted: June 1, 2011 at 21:34

Hello , alienbob.

One thing that shocked me was reading somewhere Pat was not making Slackware x86_64 fully multilib because it could kill Slackware x86.

It makes no very much sense, really. 75% of Linux users are said to use x86 software, most of the rest use x86_64. That’s a evidence of x86_64 versions letting live the rest. Anyway, your works in Slackware multilib have proven unable to take Slackware x86 away!

I would dare to say that, by keeping Slackware as a pure 64 bits beast, you are most likely to kill x86_64 version. I myself follow a strict rule: if it is unnofficial, compile it by yourself or don’t install it at all. I know of many people following the same code. That leaves your work out of the question, sorry! That also means I would need to do all the work by hand, which is possible, but not very appealing for me… Yes, I am so stuborn. I learnt it from my horses.

Would it be really so much of a mess to include the few packages needed for enabling a multilib Slackware in an official release? Its not a request, is a question. If your multilib packages work, would be there any thecnologic problem to include them in a folder inside the DVD release? Maybe /testing/multilib?

Maybe you could bribe Pat with a barrel full of beer to accept multilibrering Slacware x86_64? : ^)

Comment from Najib Ibrahim
Posted: June 8, 2011 at 07:15

Hi,

i am new to qemu vde.
i am using qemu with bridge.

i am a little confuse, why we need firewall/routing to setup qemu-vde-bridge?
below is the link to diagram what was i am thinking, is that correct and doable?
http://img534.imageshack.us/img534/4631/networkingqemuvdebridge.png

thank you

Comment from alienbob
Posted: June 8, 2011 at 11:25

Najib, if you bridge your connection to the VM you do not need any firewall rules. Those would be needed to setup a NAT connection.

I have the exact setup on my server that you show in your diagram. This is what I use; a modification to rc.inet1 that allows for the setup of a bridge interface:
http://slackware.com/~alien/rc_scripts/bridging/
And I use a rc script to configure VDE and add the tun interface to the bridge:
http://slackware.com/~alien/slackbuilds/qemu-kvm/build/rc.vdenetwork

Eric

Comment from Najib Ibrahim
Posted: June 8, 2011 at 17:44

Eric, thanks for the scripts :D

I have simplified steps as what I understood here: http://selamatpagicikgu.wordpress.com/2011/06/08/quickhowto-qemu-networking-using-vde-tuntap-and-bridge/

Comment from Neil
Posted: June 18, 2011 at 10:13

Awesome stuff! As a Linux noob (mostly used Ubuntu) Slackware can be a daunting yet satisfying journey and with the scripts and tips here it becomes so much easier, thanks!

Comment from Bert Logan
Posted: August 22, 2011 at 11:50

Just a quick note of thanks on your blog and of course the work on Slackware. I, like many Slack users, am an old timer, indeed been using Slack since kernel 0.9x pl15f, I remember labeling the floppy disk … at least …

Comment from Niki Kovacs
Posted: September 8, 2011 at 11:04

Hi Eric,

A big fat THANK YOU for the multilib stuff for Slackware64. I just had to configure a Brother laser printer that refused to work correctly on a Slackware64 server with any driver except those provided – only for 32bit systems – by the Brother website. So I just added the basic multilib packages, and now the printer works like a charm.

Comment from Alessandro
Posted: September 12, 2011 at 00:14

To update “flashplayer-plugin-11_rc1.090611-i686-1.txz” with upgradepkg you must rename the file as “flash-player-plugin-11_rc1.090611-i686-1.txz”.

Comment from alienbob
Posted: September 12, 2011 at 08:43

@Allesandro

That is wrong if you were upgrading from my previous package. You are somewhat right if you are upgrading from the package created by the script from SBo at http://slackbuilds.org/repository/13.37/multimedia/flash-player-plugin/

If you want to upgrade from theirs to mine, you can run (note the ‘%’ inbetween the old and new package):

# upgradepkg flash-player-plugin%flashplayer-plugin-11_rc1.090611-i686-1.txz

Eric

Comment from Alessandro
Posted: September 12, 2011 at 10:56

Thanks for the explanation.
You are legendary, Eric.

Comment from tim
Posted: September 28, 2011 at 11:53

hi eric, is there any chance of you updating the qemu package to v0.15.0, as your current one appears to be v0.10
thanks

Comment from alienbob
Posted: September 29, 2011 at 09:02

Hi tim

I am focusing on qemu-kvm instead which is a patched version of qemu which works with the Linux Kernel Virtual Machine (KVM). I think the original qemu may have absorbed all their patches by now, I really should check that. The qemu package in my repository is a bit outdated indeed.

Eric

Comment from Cristian
Posted: October 15, 2011 at 04:51

Hi Eric,

This is Cristian. I am having a problem with the restricted VLC build for version 1.1.12. This problem seems to be present in 1.1.11 and 1.1.10 versions too.

The problem I have is that I can not encode in MP3/AAC formats.

I tried the VLC 1.0.6 build under http://slackware.org.uk/people/alien/restricted_slackbuilds/vlc/pkg/13.0/ and I am able to encode in MP3/AAC. For whatever reason the builds under 13.1 and 13.37 seem broken in this regard.

Can you please verify and see if you’re able to encode MP3/AAC with these builds and fix them if they are broken?

Thanks!

Comment from alienbob
Posted: October 15, 2011 at 14:30

Hi Christian

I could successfully transcode an audio track inside a movie to MP3 using my “restricted” version of vlc-1-1.12 as well as using a vlcgit 20111006 snapshot. Both are 64bit versions because I do not run a 32bit Slackware anywhere, but I verified that the Slackware 13.37 package at http://slackware.org.uk/people/alien/restricted_slackbuilds/vlc/pkg/13.37/ is indeed the package with MP3/AAC encoding capability builtin. I checked this by comparing the MD5 sum of the package against the one in my local repository and by examining that package’s build log.

How do you try encoding to MP3 ? Perhaps there is something you should do differently.

Eric

Comment from tim
Posted: October 26, 2011 at 16:22

Hi Eric, is there any chance of your vlc package being built with the option to allow root usage (–enable-run-as-root passed to configure)? I regularly use a test machine to test customers hard drives and can’t check the media as root anymore.

Comment from alienbob
Posted: October 26, 2011 at 20:49

Hi tim

My VLC packages have been built with “–enable-run-as-root ” for a long time now. I checked my installed vlc-1.1.12 package and that runs nicely as root. What version of VLC are you using?

Eric

Comment from tim
Posted: October 27, 2011 at 15:26

woops i’m running 1.0.0 .
You’re right, it works fine with 1.12 (my main test pc is slack 12.2 which I haven’t upgraded because I prefer konqueror to dolphin and kde 3.4 is quicker than kde4) I’ll just have to try getting v1.12 to work on slack 12.2

Comment from Stewie
Posted: October 27, 2011 at 18:53

Hi Eric!…

I’m trying to compile the FFADO “trunk” version… I’ve installed everything is listed as a dependency… also “libconfig” (from source)… but SCons keep me asking “libconfig++” (which I supposed was included in “libconfig”)… any suggestion?…

Thanks in advance :)

Stewie

Comment from alienbob
Posted: October 27, 2011 at 22:55

@Stewie

Unfortunately this blog is not a full-blown Slackware Linux help forum. If you need help compiling ffado (software which I have never looked at and probably never will) then you might want to state your issue over at http://www.linuxquestions.org/questions/slackware-14/ where it will have a better chance at being answered.

Eric

Comment from Stewie
Posted: October 28, 2011 at 02:12

You’re right…

I’m sorry: I was only hoping that you already knew how to install the “libconfig++” library and could point me in the right direction… I was asking here because I searched quite well on the web (so also “linuxquestions.org”) and couldn’t come to a solution…

I’ll look better in the section you linked, or I’ll open a specific thread about it…

This is the second time I ask an “unrelated” question (I also asked something about a “Slackware-current setup”); I hope I didn’t bother too much… :)

Thanks anyway…

Stewie

Comment from alienbob
Posted: October 28, 2011 at 10:43

Hi Stewie

Well, not everything you ask is unrelated! Your previous question was well worth answering. It’s just that I can not give adequate answers to software related issues when I have never touched that software and most likely never will.

Eric

Comment from Pangky Kurniawan
Posted: October 29, 2011 at 08:55

Hi Eric,

Is your vlc/mplayer package support playing video file encoded with AVC Hi10p (10 bit)?

Comment from alienbob
Posted: October 29, 2011 at 13:41

Hi Pangky Kurniawan

I tried my own MPlayer package (not the version in Slackware) as well as my VLC 1.1.12 and a version I compiled from git (http://taper.alienbase.nl/mirrors/people/alien/restricted_slackbuilds/vlcgit/) and all of them playback a Hi10p video sample which I downloaded from http://www.nyaa.eu/?page=search&cats=0_0&filter=0&term=Hi10P

The VLC 1.1.12 version shows blocky artefacts in playback but both MPlayer and VLC 1.2.0git play the Hi10p video just fine.

One remark about subtitles for Hi10p video: the VLC version built from git (the future 1.2.0 release) will not display subtitles for Hi10p videos, unless you set the Video Output to OpenGL. In VLC’s preferences goto Video > Output modules and select “GLX video output (XCB)”. After you select this output mode instead of “default”, close VLC and start it again. The subtitles will show now.
See also this bug report: http://trac.videolan.org/vlc/ticket/5477

Eric

Comment from Stewie
Posted: October 29, 2011 at 14:47

Hi!…

I’m glad to know that I didn’t bother with my first question… :)

For the second one I’ll follow your advice: I’ll open a thread on linuxquestions.org…

Bye…

Stewie

Comment from Pangky Kurniawan
Posted: October 29, 2011 at 18:07

Thanks for the response Eric, you’re the best, upgrading MPlayer now

Comment from Makkuro Kishin
Posted: November 27, 2011 at 21:17

Hello, Eric.

I understand that my question may be left without an answer, yet still I just don’t know whom else I could ask ((

It’s been a while since we’ve last seen some major updates in slackware-current branch. I mean such updates as new kernels, your kde packages and others. I remember you mentioning that Patrick has some personal business to take care about but time passes and we still don’t see any serious changes in -current tree.
I understand that sometimes we all have personal matters to take care of and it would be wrong to push with it with questions like “Why?” and “When?”, yet maybe you can say just a few words so we could know if we should expect any major updates shortly?

Comment from John Culleton
Posted: November 29, 2011 at 22:17

Need a usable version of Quanta+ to run on a Slackware 13.37 installation. I tried trinity but the graphical display part of Quanta is blank. Been chasing my tail on this for many moons.
Is there a download page?

Comment from alienbob
Posted: November 29, 2011 at 22:51

Hi John

I wrote about the new Quanta Plus in this blog post: http://alien.slackbook.org/blog/quanta-plus-for-kde4/.

Basically, if you install my KDE 4.7.x package set (follow the instructions in the README closely) you will have this new Quanta Plus in KDE’s “Applications > Development” menu.

Whether it is functional enough for you, I can not say. It is an alpha release, but the base on which it is built (kdevelop) is mature.

The article in which I announce my KDE 4.7.3 package set is here: http://alien.slackbook.org/blog/kde-updated-to-4-7-3/ and it has links to download mirrors as well as the instructional README.

Good luck, let me know how it worked out. If you should have any issues with the KDE upgrade, please discuss them in the aforementioned KDE blog post so that we can set you straight.

Eric

Comment from alienbob
Posted: November 29, 2011 at 22:53

Hi Makkuro

I am afraid I can not give you any news on Slackware’s ongoing development. That is really Pat Volkerding’s call.
And while he is “busy with life”, I will keep updating my stuff at least.

Eric

Comment from ma131d
Posted: January 18, 2012 at 00:47

will be there slackware with gnu/hurd kernel in
the future ?

and thank you very much

Comment from alienbob
Posted: January 18, 2012 at 01:13

Not likely ma131d… there is no interest at all to go into that direction.

Eric

Comment from 4rp0ck
Posted: January 30, 2012 at 20:55

Hello alienbob

Can you tell to us some notice about the slackware current? is it frozen? Some problem at Pat? We can help with some thing?

Comment from alienbob
Posted: January 30, 2012 at 22:21

Slackware is alive, updates are pending, I am about to test kernel 3.2.2.
Pat requires time for his family and that has impacted the speed of development in Slackware. In the meantime, you can keep yourself busy with my KDE…

Eric

Comment from 4rp0ck
Posted: January 31, 2012 at 16:46

Thanks I really appreciate your work for the project. I’m using kde4,8 and testing the new kernel 3.2.2 from sources.

Comment from AJ Field
Posted: February 1, 2012 at 00:40

Thank you so much for your wonderful work in support of Slackware, from which I have benefited greatly. I visit your site daily.

Comment from Marylene
Posted: February 20, 2012 at 09:05

Though Slackware is the oldest Linux distribution, it is still with me. And i highly appreciate it for the old fashioned virtues of simplicity!

Comment from Kamil
Posted: February 22, 2012 at 10:06

hi Eric, i write here because i cant fit email to you:
there is remedy for problem you describe here:
http://alien.slackbook.org/dokuwiki/doku.php?id=slackware:setup

please look:
http://nil-techno.blogspot.com/2009/10/lilo-warning-initial-ram-disk-is-too.html

Comment from alienbob
Posted: February 22, 2012 at 16:32

Hi Kamil

My email address should be easy to find, I have several and they are all over the internet. But I am glad you posted here, so that I can give an answer that will also help other people

To me that link does not offer a real solution. You would have to recompile your kernel every time you need to change your initrd? Not a realistic option.

The guy in that link talks about “adding more and more functions to his kernel” which causes his kernel to become so huge that it no longer fits into the 15M memory hole together with an initial ramdisk. My question would be: why then do you still use a ramdisk if you are compiling everything into the kernel anyway? Looks terribly inefficient.

The best method is still:
Build your kernel as modular as possible. An initrd is only used to make your root filesystem available to the kernel. All the other kernel modules are not loaded when the kernel boots. As a consequence, a small, modularized kernel (like Slackware’s own “generic” kernel) can use a _big_ initrd and still fit in the 15M memory hole.

Eric

Comment from Kamil
Posted: February 23, 2012 at 09:57

hi,
first:
my problem is to change /dev/sdX in lilo.conf and fstab to UUIDs to make possible adding and removing disks without changing these files.

there is:
/dev/sda – sdf – SATA disks
/dev/sdg – sdh – PATA disks

when remove one of SATA, then /dev/sdg becomes sdf and system cant boot.

i dont have all options compiled in kernel, only requied options without HID, USB, Firewire, Video4Linux etc. :)

second:
solution from this guy, does not work for me.

Comment from Makkuro Kishin
Posted: March 8, 2012 at 17:37

Hi, Eric.
First of all, thanks for KDE 4.8.1 packages, I’m always impressed with how fast you react on new KDE releases. Keep it up, you’re the best.

I wanted to ask you something. In your KDE 4.8.1 news post you’ve written that you had a discussion with Patrick and with high probability we may soon see fresh KDE release in -current branch. So my question is “Are there any assumptions concerning XFCE 4.8 ?”. It had been released quite long ago and lots of users were expecting to see it in Slackware 13.37 but that was not the case, unfortunatelly.
If Pat had told you anything about it, I would be most greatful if you shared it with us.

Thanks in advance,
Best regards.

Comment from Ardham Grace
Posted: March 15, 2012 at 14:36

Hi, Eric!
First of all I’d like to thank you for sharing your time and knowledge with us. Slackware rules!!

Best Regards,
Grace

Comment from Mirko
Posted: March 21, 2012 at 16:29

Hi Eric and thank you for the great job you perform on line. I’m a proud Slackware user and I just compiled KDE 4.8.1 with your script…

Comment from John
Posted: April 2, 2012 at 21:19

Hi.
I appreciate the work you do. It benifits me greatly.
I have a question. When I installed slackware 13.37, I did not install any of the kde stuff. My version is now operating at greater speed than before and I also have no issues with installing programs.

Why is that I wonder?
John.

Comment from Oleg Murawicki
Posted: April 18, 2012 at 20:54

Please give me a link to latest libreoffice-3.4 for x86_64 (after upgrade to 3.5.2 I cant use “search” in Base; the same problem – in AgiliaLinux, PCLinuxOS, Sabayon & Window$)

Comment from Makkuro Kishin
Posted: April 21, 2012 at 07:57

Well guys, I guess we finally have a Troll in a blog ))

Comment from alienbob
Posted: April 21, 2012 at 11:03

Troll posts as well as spam posts get removed. Some spam posts are almost indistinguishable from troll posts.

Eric

Comment from Isaque
Posted: June 18, 2012 at 19:17

Hi Eric, have you tried Slackware on Raspberry Pi yet?

Comment from alienbob
Posted: June 19, 2012 at 13:10

I still do not own a Raspberry-Pi…

Eric

Comment from aiden
Posted: June 22, 2012 at 23:15

Eric,
I want to start by thanking you for all your contributions to the slackware community. I am using unRAID for my fileserver, which is basically slackware-lite, and have found many of your builds to be extremely helpful when trying to add functionality to my NAS. Recently I downloaded and began using your latest Handbrake build 0.9.6 from http://connie.slackware.com/~alien/slackbuilds/handbrake/ . It works perfectly (after I installed some extra dependencies not native to my particular install). However, since that stable version, the Handbrake team has introduced PGS subtitle support in Blu-Rays that I desperately need. Is there anyway I could get you to grab one of the latest nightly Ubuntu builds from https://launchpad.net/~stebbins/+archive/handbrake-snapshots/+packages and make it into a Slackware package? I just don’t have the skills necessary to cross the Debian barrier. Or, if there’s a specific method I should follow to try and build my own package, that would be terrific since these are nightly builds, basically beta code.

Comment from aiden
Posted: July 31, 2012 at 04:46

I’ll update my request to “Could you build a Handbrake 0.9.8 for Slackware”? Handbrake is now on version 0.9.8 as a stable build. Would be awesome to have this for Slackware. Thanks.

Comment from aiden
Posted: July 31, 2012 at 17:28

Bob, I just checked your slackbuilds section on slackware.com… what can I say? Thank you so much! Is there some other communication method you prefer over someone posting to your personal board? Thanks again!

Comment from alienbob
Posted: July 31, 2012 at 18:18

Well, that is why I just opened the http://alien.slackbook.org/blog/your-feedback/ page – it shows up at the top of the blog’s left sidebar. That’s where the feedback/ideas/requests can go in future.

Cheers, Eric

Comment from Lava Infotech
Posted: August 18, 2012 at 11:15

This is really interesting, You’re a very skilled blogger. I have joined your feed and stay up for in the hunt for extra of your fantastic post. Also, I have shared your website in my social networks.

Comment from Rafael
Posted: August 31, 2012 at 00:10

just beginning to use slackware, and I find this site, thanks for all the info, I am on the lookout for your new post, thanks :)

Comment from Jesus Camacho
Posted: October 21, 2012 at 18:43

Are you going to make a Trinity Desktop Environment for slackware 14.0?

Comment from alienbob
Posted: October 21, 2012 at 19:51

Hi Jesus

No sorry, not interested… I always hated the looks of KDE3. KDE4 is so much better, also with regard to functionality.

Cheers, Eric

Comment from fernando
Posted: February 17, 2013 at 17:34

hi allien bobo i need your help on instalation about slackware 14 with usb from windows
i canot please send me images , i dont understand very well your tutorial , excuseme help meeee

Comment from rkelsen
Posted: February 25, 2013 at 12:59

Hi AlienBob,

Sorry for the newbish question: Are your Handbrake and VLC packages stand-alone, or do I need to install the dependancies as well?

Cheers,

Rob

Comment from alienbob
Posted: February 25, 2013 at 14:26

Hi rkelsen

VLC is a standalone package without dependencies. You only need libdvdcss additionally if you want to watch an encrypted DVD disk.

The same is true for Handbrake. It works without the need for additional packages, but if you want it to rip an encrypted DVD you have to install libdvdcss.

Eric

Comment from rkelsen
Posted: February 26, 2013 at 10:02

Thanks Man!

Pingback from Novo slapt-getrc para o Slackware | mundo GNU
Posted: March 24, 2013 at 04:01

[...] um novo /etc/slapt-get/slapt-getrc no qual inclui o mirror dos pacotes de Eric Hameleers, vulgo alienbob, vamos a [...]

Comment from Giovanni
Posted: April 26, 2013 at 04:13

Great site contratulations.

Comment from giorgik
Posted: October 22, 2013 at 17:44

Hi Alien, I’m Giorgio from Italy and great fan of Slackware. Can you explain me step by step how you got the file
libreoffice-4.1.2-i486-1alien.txz etc… ?

Comment from Mike
Posted: November 8, 2013 at 21:18

Hi Eric. I think you may have forgotten the pipelight package. The dependencies appear in your SlackBuilds but not pipleight. Or am I looking in the wrong place:-(

Mike

Comment from alienbob
Posted: November 9, 2013 at 01:01

Hi Mike,

You are right, I wanted to save the pipelight to be released along with the article I just published… the Slackware 14.1 release got in the way. It should not have been mentioned in the ChangeLog.txt yet…
The package will soon appear in the repository.

Eric

Comment from Mike
Posted: November 9, 2013 at 01:43

Beaut. Thanks

Comment from rass
Posted: January 17, 2014 at 11:10

Hi Eric,

I tried install today multilib on 14.1 and I am getting on some packages error for md5.

http://taper.alienbase.nl/mirrors/people/alien/multilib/14.1/gcc-4.8.2_multilib-x86_64-1alien.txz: download error
gcc-4.8.2_multilib-x86_64-1alien.txz: md5sum

I tries calculate md5 also manually it not match.
Seems that you forgot to update md5.

Thanks,
Rasto.

Comment from alienbob
Posted: January 17, 2014 at 12:38

Perhaps you have a bad download? There is nothing wrong on the server:

$ grep 14.1/gcc-4.8.2_multilib-x86_64-1alien.txz CHECKSUMS.md5
aff5fedba07b5b46dd274d9ec4b7e94b ./14.1/gcc-4.8.2_multilib-x86_64-1alien.txz
9334b5fe39ee13075b3fbbde602fd523 ./14.1/gcc-4.8.2_multilib-x86_64-1alien.txz.asc
3033cb13740f1dd7b235c131c3973f29 ./14.1/gcc-4.8.2_multilib-x86_64-1alien.txz.md5
$ md5sum 14.1/gcc-4.8.2_multilib-x86_64-1alien.txz
aff5fedba07b5b46dd274d9ec4b7e94b 14.1/gcc-4.8.2_multilib-x86_64-1alien.txz

Eric

Comment from rass
Posted: January 17, 2014 at 13:12

hmmm … seems that slackpkg+ not checking md5 in CHECKSUMS.md5, because thare is correct checksum, but compare checksum with gcc-4.8.2_multilib-x86_64-1alien.txz.md5, and that’s the reason. So what is wrong, slackpkg+ or gcc-4.8.2_multilib-x86_64-1alien.txz.md5 ?

S rass@rass-work:~/Downloads$ md5sum glibc-zoneinfo-2013d_multilib-noarch-7alien.txz
7c0e80111ac8ffe73cbdfa73e3ec36a9 glibc-zoneinfo-2013d_multilib-noarch-7alien.txz
S rass@rass-work:~/Downloads$ cat glibc-zoneinfo-2013d_multilib-noarch-7alien.txz.md5
7c0e80111ac8ffe73cbdfa73e3ec36a9 glibc-zoneinfo-2013d_multilib-noarch-7alien.txz
S rass@rass-work:~/Downloads$ md5sum gcc-4.8.2_multilib-x86_64-1alien.txz
d41d8cd98f00b204e9800998ecf8427e gcc-4.8.2_multilib-x86_64-1alien.txz
S rass@rass-work:~/Downloads$ cat gcc-4.8.2_multilib-x86_64-1alien.txz.md5
aff5fedba07b5b46dd274d9ec4b7e94b gcc-4.8.2_multilib-x86_64-1alien.txz

Comment from rass
Posted: January 17, 2014 at 13:19

aha last post was wrong …my md5 not much … hmm strange … maybe bad package here http://taper.alienbase.nl/mirrors/people/alien/multilib/14.1/

Comment from rass
Posted: January 17, 2014 at 13:23

so last post .,.. sorry … everything is okej … we have here some troubles with downloads …

Comment from rass
Posted: January 17, 2014 at 14:01

please delete last two posts … seems something is wrong with slackpkg+, because md5 is ok on your side … I am trying to debug slackpkg+,

Comment from Fred Lima
Posted: April 13, 2014 at 00:42

Hi AlienBob
thanks for the support of slackware.
grettings from Brazil

Comment from Ferrari Renato Maria
Posted: April 22, 2014 at 19:09

I very very very thank you for your work with slackware.
Thank you

Comment from Michelino
Posted: May 6, 2014 at 23:04

Hallo Eric,
maybe this is the wrong place, but I don’t know which is the good one :-)
I want just to point you out that there’s a new minor mirall release that seems quite important, ‘couse avoid that the user password is stored in clear in the configuration file.
http://owncloud.org/sync-clients/releases/
Thanks

Comment from alienbob
Posted: May 7, 2014 at 09:49

Hi Michelino

There is a nice link at the top left of my blog, called “Your Feedback” which is meant for feedback like yours… but most people seem to overlook it.

Anyway, the bug you are talking about (credentials are stored in clear text in the mirall config file) has another bug-number than the one mentioned in the miral changelog… they made a typo there.
The actual bug report is https://github.com/owncloud/mirall/issues/1458

The issue is, that mirall now depends on a package “qtkeychain” which is used to store your credentials in the KDE Wallet (if you are running KDE) or Gnome Keyring (if you are running any other Desktop Environment). If you fail to install the qtkeychain package, then mirall will store your credentials in its own configiration file instead… in clear text. This potential security issue was fixed in 1.5.2 but that had side effects which were then fixed in 1.5.3.

I noticed that my repository ChangeLog.txt properly mentions (Fri Feb 14 22:27:55 UTC 2014) that qtkeychain is now required for mirall 1.5.x, but that the package’s “slack-required” and .dep files do not mention it yet.

If you have qtkeychain installed, then the clear text password issue does not apply to you.

I will nevertheless update my mirall package and also update the dependency list to include qtkeychain.

Cheers, Eric

Comment from Michelino
Posted: May 7, 2014 at 11:16

Hallo,
sorry for the bad place for feedback, I’ll definitely use the right one in the future, I promise!!! :-)

Anyway, notwithstanding the lack of qtkeychain in your “slack-required”, I’ve installed it, but I’ve nevertheless had the problem, probabily due to the fact that my kwallet is disabled (if I’ve understood your explanation).
I’ve ri-compiled the new release with your slackbuild and the problem disappeared, also with kwallet disabled.

I hope that my thought is clear notwithstanding my bad english.

Thanks for all, obviously!

Comment from Jupiter Broadcasting
Posted: May 14, 2014 at 13:17

Was wondering if you’d be willing to do an interview about slackware with us at some point. As a long time slackware user myself, id love for it to get some fresh attention. Ive tried to contact Pat, but have been unable to connect with him, and imho you’re the next in line as far as Slackware royality, lol.
If this is something you’d be interested in doing, or if you’d rather defer to Pat and could put us in touch with him that’d be awesome.
I really appreciate your longstanding support and work with Slackware, guys like you are why i just can never leave the slackware side of things.
-Jt

Write a comment