Seriously? You believe that the difference between i586 and x64_86 is similar as as MSDOS -> Windows 10, for real? So you accuse PV as spending time maintaining also a today DOS?

Amazing yet, that oldest 32bit flavor is the only one able to run shiny things like Skype, Android Studio and another useful crap, required by almost any Company Management. Personally, I go ARM for fun, and I still run your (abandoned) ARM version, and while can 64 version can be able to works native with some Java! applications, I will consider some experimental thing, good to check around 2050, if I' still alive.

I have two x8 Buldozer, two x4 Phenom and an (reference) Pentium 4. Go compute.

In other hand, around of 300 computers, both servers and desktop, with which I have to deal, are x86 only. Again, go figure.

Nope. No interest to run experimental trees and operating systems. If, you are kind to provide a ISO able to boot into my Pentium4 3GHz, 2G RAM, GeForce 6200 with 256B RAM, I will glad to check it. Where is the link for?

So you decided to ship exactly that experimental 64 version, well know to NOT be able to run even Skype native. You don't believe that you can be accused to make the Slackware be more difficult like it is for real?

The true Slackware, able to run Skype and Android Studio without replacing its GLIBC wih a custom one, even provided by the Slackware's Knight.

Nope. For installation, usually I use a custom version of YaLI, my pwn graphical installer, which get the packages from a local net repository.

Nice information, good to know, even personally I used an Slackware ISO booting around ten years ago. To be fair, still I have a (complete) collection into DVDs. As in Pat's shipped DVDs.

If remembering you that there is Slackware (i586), make me a Moron, well... I'm proud to be a Moron. All the best!

1 members found this post helpful.

...you mean, like slackware64? You don't need to actually _replace_ glibc. My slackware64 installations are perfectly capable of running e.g. Android stuido, by simply populating /lib and /usr/lib with the 32-bit stock libraries, such as glibc-solibs-2.23-i586-1.txz...

Now I am accusing Pat of unspeakable things? You are so funny. Not.

You are not interested in Slackware-current yet you are bugging me to provide a 32bit version of its Live Edition?


Ah yes that graphical installer which you are not sharing. Yet you accuse me of not sharing more.
I could continue answering, but I guess this was my last reply. It is useless to spend more time on you.

4 members found this post helpful.

Sorry, but you claim that x86 arch is similar with Microsoft DOS. Go figure!


You believe that I really need your Live Edition? Come on! Under A.D. 2008 I managed to have a Live DVD Edition of (Slackware?), with all shiny graphical things, including the installer.

Or, using your insider information, you suppose that I'm the only one tard asking and using x86?

Correction: "that graphical installer which you are not sharing" because I'm not willing to even pay 3 (euro)cents for sharing it. Give me some web space and I'll push the latest (public) version on-line. In other hand consider that I ask for so small space compared with you usual friendly hosted crap, like OMG! WTF? 1.7GB MATE ISO?

Let us get back on topic, gentlemen. I am thrilled with Slackware 14.2 RC 2. If you have not purchased a Slackware subscription now is an excellent time to do so. Let us support Slackware.
Accept no substitute. Slackware!!!

4 members found this post helpful.

+1.

1 members found this post helpful.

128-bit or GTFO.... J/K

I would love to see the computational power of a 128-bit CPU though.

I also provide only x86_64 (64) version of MATE packages for next Slackware 14.2 for MATE 1.12 and 1.14 in testing directory where Eric used this binary packages to build the MATE ISO for public testing. The x86 packages will be generated once Slackware 14.2 gets released and it will be placed in the usual place.

I'm grateful that Eric is willing to build the MATE and Cinnamon ISO because many people can try and test it before the final version is shipped, which is the main goal of this project. We all do this in our free time and many others have helped during the development cycle. What we need is a constructive comments, not insulting other's work. If you don't like it, so be it. There are others who gets the benefit from this project.

6 members found this post helpful.

Here you go...

OOPS! I see this one is still installed with 32-bit, I'll boot it with 64-bit shortly in case that makes a difference.

Let me know if you need anything else.

*** Update: Here it is booted to 64-current installer with network configured.

Darth, you have github and bitbucket, of which both are free to upload YaLI and it's source so stop making shit-for-brains level excuses. I'm sorry, but are you that dense, or blind to services that have been available for free for years?

And be damn well thankful Eric and crew are at least putting stuff out. You don't have to like it, but you can at least be respectful to the work done.

I think 64 bit power was introduced somewhere around 1995. 20 years is enough, let's move on to 128. Chip makers have made of ton of money off of existing technology. Think I'll get my drafting machine set up, sharpen the pencils and start designing tonight. I may someday need a computer that can access more than 16 exabytes of memory (2^64=2*10^16 I think). It is amazing though that in 20-30 years the personal computer when from the TRS-80 to a PC to XT...to 64 bit which today is enough for 99% of uses.

Jesus... i still think about restart my old C=64 which is 8Bit only. With the S-CPU module i still have laying around i may get about 16bit... and that did rock 30 years ago! I'm pretty sure i will never get Slackware-current running on this mature hardware, would be nice anyway.

Weird. The e100e driver is contained in the initrd, so why is it not loading that driver during boot? Something might be amiss with UDEV because in case of network boot, it is called to trigger the loading of the driver, but it does this only if the "nfsroot" parameter is present.
Time to do some troubleshooting. My laptop has a wired interface supported by e1000e too.

Just wanted to chime in and mention that all Ludites don't agree on everything. I do prefer 32 bit OpSys for now but that doesn't prevent me from trying 64bit both as a hard install and with each new iteration of Live. It also doesn't (and obviously by my previous posts) prevent me from deep respect and gratefulness for all that Eric has done and continues to do for Slackware. Sometimes I think we just have to look at nicknames to see how a person views themselves. IIRC didn't Darth Vader cut off his own son's hand?

2 members found this post helpful.

I found the cause, the initrd is missing modules that are dependencies for e1000e and therefore 'e1000e' refuses to load.
I will have to improve the routine which adds network support to the initrd. The 'mkinitrd' script has some good code to take care of that, which I might just re-use.

2 members found this post helpful.