SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
So I would like to hear all of the futile arguements for why RAID1 shouldn't be considered as a standard feature at installation. And then you can tell us how Slackware isn't closed (and unduly regressive).
Hey Shingoshi,
It is a breeze setting up a RAID for Slackware. You've got the EXCELLENT mdadm tools with the 12.x series and the "old-school" raidtools for Slackware 11.
I've been running more or less all my Slackware machines (both servers and desktops) with RAID for a looong time, and it works very well.
Yes, it's not available as a ncurses option, but it's just as much there as the trusty fdisk is. And it's not that hard doing:
The reason it looks out of place on the Slackware website is because the site layout is so square, which fit with the old logo. The new logo is all curvy so it looks a bit out of place. But the logo itself is great in my opinion.
Next step: it's time to change the website design to a more "curvy" one to fit with the new logo. OMG, I'm out :-(
Next step: it's time to change the website design to a more "curvy" one to fit with the new logo. OMG, I'm out :-(
I don't think it'll be possible to rewrite entire website in the way that everything will look the same (while remaining readable) upside-down (including text, links, etc. ).
I keep looking at that new logo, thinking it might grow on me. So far...no chance. It's like a naturally pretty girl plastering her face with cheap make-up, unnecessary and unfitting.
Hmmm, it's not bad, but the perspective seems a bit off and so the text looks a little lopsided. Other than that a less photographic digital art box would probably be beneficial, because it would allow you to maintain the colour palette and look-n-feel/textures of the box when you shrunk it down to a favicon size. Logos are difficult, I've never been able to make anything good myself, I reserve mystified awe for people who consistently throw out good work like say: http://logoholik.com/.
Before this gets out of hand, I must say that post of mine
was just a joke. The logo on that website is just plain text
thrown on the first Google image hit for box, and put beside
one of the logos from the Slackware site around 2:00 a.m.
My plan for that site is to learn XHTML, and CSS, and then put
something up that looks a bit more ... serious. In the meantime,
it's just a sandbox to save a few items. Who knows, I may never
stop my real work and learn HTML enough to do anything.
Well in that case, might I suggest learning HTML4.01 strict instead of XHTML trans or XHTML strict? In a fully compliant browser (like the one w3c are building themselves) serving XHTML as text/html can cause unexpected problems due to the differences between it and HTML (more details here) and if you serve it under the correct mimetype application/xhtml+xml, then IE will not render the page.
Basically, if you make it viewable in most browsers then you lose all the advantages XHTML would have given you (XML parsing, etc - not that most browsers do that even under the correct mime, tag-soup engines are just much more forgiving of coding errors) and it can actually cause unforeseen issues not present in HTML4.01 strict (which when written correctly is just as neat and elegant as XHTML).
EDIT: Uh... this is off-topic isn't it, should stop doing that.
Before this gets out of hand, I must say that post of mine
was just a joke.
It wasn't hard to tell, at least for me. I got a good laugh out of it. Had you really been serious then I wouldn't have said anything for fear of hurting your feelings... It literally looks like it took you 10 seconds to do. At least no one can say that about the new logo...
It's been more than two weeks. I really don't think new logo deserves that much attention, no matter how ugly (or wonderful, or whatever) it is. It's just a logo.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.