Slackadelic.com

Yeah, we all know by now that the http://rafb.net paste site is going off-line. Seven years of dedication to a free pastebin for the world.

Well, after a few talks with some folks and after being pressed in to doing (hehe) this, I’ve switched http://pastebin.slackadelic.com to use the code from rafb.net.

Thanks go out to edman007 from ##slackware on freenode for his help in tracking down and fixing a few odd issues with the code. It even works with paste scripts! Right now the official script is Pastelling. The script was originally written by Steven Robson Pastelling, aka rafb.pl, was written by _pragma, but is being hosted on github by Michiel van Wessem.

I’ve had a few issues getting my mouse working properly with evdev in the latest updates to Slackware64-current. Today, it appears, that other users are experiencing some other issues outside of a mouse not mapping buttons properly. Most of those users report black screens when trying to restart or quit an X session.

If you are one of us having such issues and are stumped, try the below in your xorg.conf before you go googling around for 3 hours like I did


Section "ServerFlags"
Option "AutoAddDevices" "False"
Option "AllowEmptyInput" "False"
EndSection


I hope this helps!
As always you can catch me in ##slackware on freenode if you have any questions/suggestions/comments.

People have asked, “Is that even possible?” Yes, it is.

I did this remotely from work via ssh on my home box, worked fine, except for a speed bump here and there. Issues that were caused mainly by me not paying attention.

First off, make sure you upgradepkg pkgtools, gzip, and tar. Then install the xz package if its not already installed. If it is, then upgradepkg xz as well.

After that, you should be able to upgradepkg */*.tgz and then upgradepkg */*.txz to make sure everything gets added.

Now, the other issue is the 32bit compat libs that come with Slamd64. You will want to remove these.

You can get the latest release of the 32bit compat libs that Fred is working on here

Now, this is the process that worked for me and your mileage may vary. My upgrade path went a little differently than this and luckily I had a Slamd64 chroot available to symlink missing commands against or I would’ve been hosed.

Comments/suggestions, as always, are welcome.

There have been quite a few questions posed since the official announcement by Patrick Volkerding that Slackware is now releasing an official x86_64 port.

These questions normally stem about 32bit compatibility etc.

Here are a few answers that I hope will resolve any doubts/questions/concerns you may have, at least for now. These are of my own opinion and may not be completely factual.

1) Is Slackware64 multilib? (support both 64bit and 32bit programs)
A: Yes. It is multilib.

2) Does Slackware64 include the needed 32bit compatibility libraries necessary to run 32bit applications?
A: No, it does not include any 32bit compatibility libraries at this time.

3) Can I build 32bit applications on Slackware64?
A: From research and talking with other Slackware64 testers, it appears that gcc/glibc does NOT support building with -m32 flag for 32bit binary output. I have no idea if this is going to change in the future or not.

4) Is there any easy way to include the 32bit compatibility libraries?
A: The short answer is, possibly. Its been debated that you can use the c/ series from Slamd64-current in Slackware64 and gain the ability to run 32bit applications “out of the box.” However, I have not tested this and right now is more of a theory.

One other note, if you want to RUN 32bit applications without the compatibility libraries you will need to get a static built binary that includes those libraries. This in itself isn’t a bad solution per se, but it also means that you will be looking at VERY large binaries.

I hope this helps to answer some questions. If any of this is inaccurate or could use some clarification, please don’t hesitate to drop me a line and let me know.

If you happen to be one of the leechers that has recently gotten pwn3d by my little change in how I publish my images.

Drop me a line! dominian@slackadelic.com

I know a few of you have been searching.. I can see you in mah logs!

In the process of securing my blog, I just so happened to be looking through the logs and found a few leechers for images on my site.  Unfortunately for them the power of Apache and htaccess files makes it possible for me to “serve” up a different image than requested.

This, is what I did.  Was it funny? Oh you bet it was.  Do I get satisfaction from their hardship?  You bet I do.

Yeah, they may have hated it, but I hate it more when someone leeches MY bandwidth and MY resources for their own benefit.  Or was it the fact they were just too ignorant to do it correctly; too lazy to do it correctly.   The reason matters not.. I really don’t care.  They… got….pwn3d!

One site, at this point, has already pulled the image I put in its place. The other sites, lets just say, one is a tiled background, the others are smack dab in the middle of popular articles. Ooops!

That’s right, Fred has released 12.2 of Slamd64!

Get it at your favorite mirror!

Fred has pushed another round of updates to Slamd64. However, he’s still not calling this “stable” due to lack of testing at this time. Its only a few packages at this time and I’d say we are getting close!

Download, upgrade, and test! I’d like to see 12.2 FINAL before the end of the week!

I just found out about this add-on for Firefox called ScribeFire which allows you to post to your blog from within Firefox.. like.. with this post!

Just thought I would let ya know