Language Selection

English French German Italian Portuguese Spanish

Slax-5.1.7 md5sum

Filed under
WebSite

I recently d'loaded slax-5.1.7 and checked the md5sum that was listed at Distrowatch and found it to be incorrect. I checked at the Slax site to verify the error and found the correct one:

a716b9bc1a47c8afb4b25d40e77d2660 *slax-5.1.7.iso

Here's a excerpt from the Slax forum:

"Distrowatch does (again) link to an older version of md5.txt file (hosted on some non-updated mirror). The bad file is my fault but I can't do anything with it now. This confuses people a lot.

Would somebody be so kind and report the problem to Ladislav? (distrowatch owner).
100% correct md5.txt file is here: http ://ftp.linux.cz/pub/linux/slax/SLAX-5.x/md5.txt

Moreover distrowatch is using older logo for SLAX, I hope it will switch to new one sometime.

http ://www.slax.org/dl/newslax/dwicon.png
_________________
Tomas
The Project Manager"

I hope this is the proper place to post this to get in touch with the temp host of Distrowatch-Susan Linton who is sitting in for Ladislav.

Phil

Thanks for the quick

Thanks for the quick response I will pass it on to Tomas.

Phil

re: slax md5sum

He said he fixed it earlier this morning. The logo will have to wait for Ladislav to return. You're welcome. Smile

----
You talk the talk, but do you waddle the waddle?

re: Slax-5.1.7 md5sum

Sure. Ladislav is on vacation, but Dr. Zhu is available, and he's usually the one who takes care of the release postings. I sent him an email on the subject. I'll update you as soon as I hear anything. He's on Shanghai time tho.

The logo might have to wait. I'm not sure I should take it upon myself to replace that file even if I have the correct file permissions to do so. Worst case scenario, I'll write Ladislav and he'll fix it when he gets back.

Thanks,
Susan

----
You talk the talk, but do you waddle the waddle?

More in Tux Machines

Black Hat 2014: Open Source Could Solve Medical Device Security

On the topic of source code liability, Greer suggests that eventually software developers, including medical device development companies, will be responsible for the trouble their software causes (or fails to prevent). I think it’s fair to say that it is impossible to guarantee a totally secure system. You cannot prove a negative statement after all. Given enough time, most systems can be breached. So where does this potential liability end? What if my company has sloppy coding standards, no code reviews, or I use a third-party software library that has a vulnerability? Should hacking be considered foreseeable misuse? Read more

Does government finally grok open source?

Yes, the government -- one U.S. federal government employee told me that government IT tends to be "stove-piped," with people "even working within the same building" not having much of a clue what their peers are doing, which is not exactly the open source way. That's changing. One way to see this shift is in government policies. For the U.S. federal government, there is now a "default to open," a dramatic reversal on long-standing practices of spending heavily with a core of proprietary technology vendors. Read more

The OS LinuX Desktop

Reader Oliver wanted to make his Linux Mint desktop look as much like a Mac as possible so others would find it easy to use. Given some of our previous Linux featured desktops, we know it wasn't tough, but the end-result still looks great. Here's how it's all set up. Read more

A Linux Desktop Designed for You

Desktop environments for Linux are not released ready-made. Behind each is a set of assumptions about what a desktop should be, and how users should interact with them. Increasingly, too, each environment has a history -- some of which are many years old. As you shop around for a desktop, these assumptions are worth taking note of. Often, they can reveal tendencies that you might not discover without several days of probing and working with the desktop. Read more