Profile cover photo
Profile photo
Thiago Silvino
About
Posts

Post has shared content
#Linux stable kernel 4.13.2 and 4.12.13 as well as the longterm kernels 4.9.50, 4.4.88 and 3.18.71 (which is kind of EOL to be precise) are out now. As usual, they contain fixes throughout the tree and some of them might fix security bugs – users thus should upgrade to one of these versions.

Just this time I'll be more precise. I know there are at least two important fixes in there. But the "at least" is the important part. Read it as: There might be more. And that's why you always should upgrade to new stable and longterm kernels, if your distribution hasn't you covered.
Photo
Add a comment...

Post has shared content
UTF-8 25 years old. Cheers!
UTF-8 turned 20 years old yesterday.

It's been well documented elsewhere (http://www.cl.cam.ac.uk/~mgk25/ucs/utf-8-history.txt) that one Wednesday night, after a phone call from X/Open, Ken Thompson and I were sitting in a New Jersey diner talking about how best to represent Unicode as a byte stream. Given the experience we had accumulated dealing with the original UTF, which had many problems, we knew what we wanted. X/Open had offered us a deal: implement something better than their proposal, called FSS/UTF (File System Safe UTF; the name tells you something on its own), and do so before Monday. In return, they'd push it as existing practice.

UTF was awful. It had modulo-192 arithmetic, if I remember correctly, and was all but impossible to implement efficiently on old SPARCs with no divide hardware. Strings like "/*" could appear in the middle of a Cyrillic character, making your Russian text start a C comment. And more. It simply wasn't practical as an encoding: think what happens to that slash byte inside a Unix file name.

FSS/UTF addressed that problem, which was great. Big improvement though it was, however, FSS/UTF was more intricate than we liked and lacked one property we insisted on: If a byte is corrupted, it should be possible to re-synch the encoded stream without losing more than one character. When we claimed we wanted that property, and sensed we could press for a chance to design something right, X/Open gave us the green light to try.

The diner was the Corner Café in New Providence, New Jersey. We just called it Mom's, to honor the previous proprietor. I don't know if it's still the same, but we went there for dinner often, it being the closest place to the Murray Hill offices. Being a proper diner, it had paper placemats, and it was on one of those placemats that Ken sketched out the bit-packing for UTF-8. It was so easy once we saw it that there was no reason to keep the placemat for notes, and we left it behind. Or maybe we did bring it back to the lab; I'm not sure. But it's gone now.

I'll always regret that.

But that's my only regret in this story. UTF-8 has made the world a better place and I am delighted to have been a facilitator in its creation.

So tonight, please give a toast to a few quickly sketched boxes on a placemat in a New Jersey diner that today define how humans represent their text to be sent across international boundaries (http://googleblog.blogspot.com/2012/02/unicode-over-60-percent-of-web.html), and especially to the X/Open folks for giving us the chance and the Unicode consortium and IETF for pushing it so successfully.

Signed,
-rob
U+263A '☺' white smiling face
Add a comment...

Post has shared content
Add a comment...

This is how I managed to configure PRIME Sync in my Optimus laptop:

Dell Inspiron 14 3443 (distro Slackware64-current)
iGPU Intel 5500 (driver i915)
dGPU Nvidia Geforce 820M (driver NVIDIA-Linux-x86_64-375.26)
Kernel 4.8.14 (CONFIG_HARDENED_USERCOPY is not set) boot option nvidia-drm modeset=1
Xorg 1.19.0

The solution is posted in this link:
https://devtalk.nvidia.com/default/topic/957814/linux/prime-and-prime-synchronization/6/?offset=82#5040106

Post has attachment

Post has shared content
Howto code
How do I learn coding in a single night? #humor   #programming   #geeky  
Photo
Add a comment...

Post has attachment
Thiago Silvino commented on a post on Blogger.
I hope that Pat chooses the kernel 3.14 so we can use the firewall nftables and the stable zram code :)
Add a comment...

Post has attachment
Thiago Silvino commented on a post on Blogger.
Very good work Willy!
Add a comment...

Post has attachment
+Eric Hameleers's blog is back!
Alien Pastures
Alien Pastures
alien.slackbook.org

Anybody using slackpkg+? I just set it up but I can't find any packages from Alienbob repository (I am sure that Alienbob's packages is not in the blacklist file). This is how my slackpkgplus.conf file looks like:
PKGS_PRIORITY=( slackpkgplus:.* restricted:.* multilib:.* ktown:.* alienbob:.* )
REPOPLUS=( slackpkgplus alienbob restricted multilib ktown )
MIRRORPLUS['alienbob']=http://taper.alienbase.nl/mirrors/people/alien/sbrepos/current/x86_64/ MIRRORPLUS['restricted']=http://taper.alienbase.nl/mirrors/people/alien/restricted_sbrepos/current/x86_64/ MIRRORPLUS['multilib']=http://taper.alienbase.nl/mirrors/people/alien/multilib/current/ MIRRORPLUS['ktown']=http://taper.alienbase.nl/mirrors/alien-kde/current/latest/x86_64/ MIRRORPLUS['slackpkgplus']=http://slakfinder.org/slackpkg+/
Wait while more posts are being loaded