SlackwareThis Forum is for the discussion of Slackware Linux.
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 keep track of the SlackBuilds or Changelog in current, you will get some clues. There are "x86_64" flags in SlackBuilds.(some even have "arm" flag, see source/x/scim/scim.SlackBuild) Sometime ago, grub patched for boot 64bit kernel. So...
Sorry I had to make sure of a few things, that I wasn't dreaming, and that I was not drunk. I am sober, though I guess the shock of the news has not quite hit yet. This is incredible news, and the fact that 32-bit Slackware will be maintained alongside the official 64 bit... Wow.
64-bit slackware?! NO WAY!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! I can't believe it!!!!!!!!!!
This is very good news indeed. I'm anxious to read more details as they become available. I'm long overdue for a new computer, and it makes sense to get a 64-bit system these days. I'm glad my favorite operating system will soon be available in a 64-bit flavor.
Not without a 32-bit mplayer unfortunately. But it probably won't affect you unless you get a very odd video encoded with a proprietary codec that very few ever use. I've had this happen a single time so far. I solved it by compiling myself a 32-bit mplayer and pointing it to the 32-bit codecs. However, again, it's very rare. The 64-bit codecs available in the package you pointed to is enough to run about 90-95 % of all videos on the net.
Last edited by H_TeXMeX_H; 05-20-2009 at 01:11 PM.
Slackware64-current installed and working, just a small problem with dialog not displaying properly on the keyboard selection stage of the install and whilst installing nvidia64 drivers.
The keyboard selection dialog actually looks exactly as intended...
The keyboard input for the old version of this dialog made the setup crash if you would type a # or $ character, so this new dialog no longer uses an input box. That makes it look a bit weird (monochrome stretching all across the screen) and I warned Pat V. that people (just like me when I first saw it) would think it was a graphical display bug.
About the NVIDIA installer... yes this has baffled me ever since I got to the point where I had a working X.Org. The curses interface of that installer is all messed up and I have not found the reason why, nor have any of the team found a fix.
The most agreeable way to install the NVIDIA driver is by running it as
sh NVIDIA-installer-blabla.run --ui=none
and answering the questions on the prompt instead of using curses dialogs.
Slack64 up and running and WOW!!
I haven't built any pkgs for it yet but was able to use some stuff I built for Slamd64.
Nice to be able to install Smplayer and Pokerth without deps.
Nice partitioner in /extra works great!
Installed kdelibs3-3.5.10-x86_64_slamd64-opt2.tgz trying to get GooglEarth & Kaffeine to work but no dice. But that ok because Smplayer is my favorite and I can live without GoogleEarth.
I had some difficulty installing the Nvidia driver but got past it. On my system the installer was not very legible with "accept" and "do not accept" buttons scattered all over the place but I was able to get through it from memory. I should mention the this is a dual monitor setup and maybe that has something to do with it.
So far the system seems to be bullet proof, or at least "slackass" proof.
I remember, that Slackware was looked at being archaic, outdated, user hostile and so on. It had no LVM and initrd support, playing multimedia files was a nighmare to set up, and support for removable devices, such as USB harddiscs, was very basic. But those who used would not change it, because it was so Unix'ish, so stable and so mature.
Then installer support for LVM, LUKS, software RAID and initrd was added, finally. And the udev, HAL and D-BUS implementation of Slackware came late, but was the cleanest and most mature implementation of these, I have seen on any distro. Then, Unicode (UTF-8) support went into liloconfig.
Finally, Slackware is now always one of the first distros for which you can get the latest incarnation of KDE.
Slackware is no longer archaic. It's no longer technologically trailing the market. It is now the most modern distro I know, with the highest user comfort. It has passed by so many contenders in such a short time --- incredible.
Thinking back, I actually avoided trying Slackware, until I bought an old, used laptop with very limited hardware, such as only 40 MB of RAM. The so-called "modern" distros wouldn't install on hardware with less than 64 MB, then. Slackware was my last option, and it worked quite well on that laptop, for a long time. I slowly learned what it was, that Slackwers made stick with this "oldie".
Now, Slackware is up to the competition and in some ways leading it, but it is still Slackware: Unix'ish, stable, cryptic, but most efficient in some areas. Slackware64 finally is going to replace my last installation of some other distro. I do like the chameleon, I have to say, too, but I set it free now.
I don't think Fred will be at all displeased, why should he be ? This is what he wanted, a 64-bit slackware which he implemented at first, and now it's official.
Maybe, he finds, it is a relief, actually, as his new job seems to absorb him. Patches that appear for Slackware are usually avaiable after a short delay for Slamd64, too, but currently the delay is bigger than usual.
All depends on the question, if Fred intends to continue maintaining Slamd64.com. Mabe, he already stopped it, stuck in the middle, just having relaunched the web site.
So he will probably not be pissed off by the fact, that there is now an officiel Slackware64, but maybe by the fact, that he wasn't involved or informed earlier (*if* he was or wasn't, I really don't know).
BTW, the official announcement reads a bit offensive. Although the team thanks the non-official ports, it has done it right, now. This implies that the other haven't done it right, and that, in turn, has a potential to make a couple of guys feel pissed off...