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.
Distribution: Debian, edition depends on what i run it, wheezy on main box.
Posts: 91
Rep:
Quote:
Originally posted by piete Just to set a record or two straight, it seems like Andronik is confused (forgive me if I've misinterpreted):
With the full 10.1 release now done, I imagine you will be pleased with the "Slackware Experience" Fred and Slamd64 provide for you, because for all intents and purposes it is exactly the same, but using 64-bit binaries. If you're anything like me and compile a lot of your programs from source, you'll find most of the newer stuff compiles fine, and the stuff that doesn't (mplayer & wmv playback) gives you instructions on how to get it to work.
yeah, i am something like you
i do my hands not a little dirty, but mostly very unclean.
my amd64 box is just my main work computer.so it must be in shape all time.
Quote:
[i]
In short:
* If you like Slackware's way of doing things and don't mind getting your hands a bit dirty in your quest to keep Slack, then Slamd64 is definitly for you.
* If you don't have the handful of hours needed to fix up some of those little niggles, but still want a 64-bit platform, try SuSE.
* If you don't have the time to reinstall a new distro, then stick with 32-bit Slackware current. You'll find a speedup improvement in compile times and boot loading times by using full 64-bit binaries. I don't do video editting or heavy raw computation (RSA Challenge Keys, anyone?), but I expect that they'd be faster under 64-bit, too.
[/B]
SuSe is like red flag for cow.
It is perfect os besides the fact it have yast.
because i like to configure things myself, i do not need Yast, at least in way he does confs.
Suse is for money, money is time, and i said i have no time.
Quote:
[i]
As a final note to acidjuice:
it's only the Java web-plugin that doesn't exist for x86_64 - they've released the RTE (which works very nicely ... mmm Azureus!) for x86_64. I recompiled Firefox for x86_64, but actually, the dev team's standard x86 downloadable binary runs faster than my custom compiled! Anyway, the point I was making: you can use the Java RTE/SDK (to run/compile java apps) in native x86_64, but the 64 bit RTE has no web plugin.
So, whatever happens, enjoy your distro!
- Piete. [/B]
thx for thorough information.
information about java as rte/sdk was needed.
i always do enjoy slack.
just don't know who is Fred. is he as stable as Pat?
i think there is time for some more people as slack developers (not me, not script guy enough), also as ports. 64 bit official port is must have in one distro.
maybe CELL port too?
those factors rise sometimes question for me about longevity of sackware in future.
just don't know who is Fred. is he as stable as Pat?
Fred Emmott is the man behind Slamd64 ( www.slamd64.com ). He's more interested in getting decent x86_64 support under Slackware than absolute stability (which is fair). Considering the x86_64 platform is still quite new for desktop machines (and thus the programs and toolchains are still immature), I'd be suprised if you would seriously consider trying to pit your 64-bit box's uptime with that of a stable Slackware and i486 combo.
Quote:
i think there is time for some more people as slack developers (not me, not script guy enough), also as ports. 64 bit official port is must have in one distro.
Slamd64 isn't an official port, because it is not a duplicate of Slackware. For technical and compatibility reasons, Fred has used newer toolchain components (gcc, glibc) and seems happy to put newer programs into it, too, for similar compatibility (x86_64) reasons. In all, it's a power user's dream, but a server admin's nightmare =)
I've always wanted to build PS2-Slackware (I have the PS2Linux kit), but at this rate PS3-Slackware will be ready way before I get around to it!
Quote:
those factors rise sometimes question for me about longevity of sackware in future.
An interesting point, but one that's been made and countered often enough without me adding more fuel to the fire. In short: Pat has other people around him to (excuse the pun), take up the Slack. Rummage around the other posts for more information on this. I know I won't be stopping any time soon.
Originally posted by piete
it's only the Java web-plugin that doesn't exist for x86_64 - they've released the RTE (which works very nicely ... mmm Azureus!) for x86_64. I recompiled Firefox for x86_64, but actually, the dev team's standard x86 downloadable binary runs faster than my custom compiled! Anyway, the point I was making: you can use the Java RTE/SDK (to run/compile java apps) in native x86_64, but the 64 bit RTE has no web plugin.
yep, that's what i meant when i explained why i still use 32-bit firefox.
Originally posted by acidjuice I'm starting to question WHY should i build it. it will still be in 32 bits anyway, why not take patrick's .tgz and modify it to point at the /usr/lib64 directory instead of the /usr/lib...
I don't have sgml-common or any other package related installed on my system and Gnome works just fine. Like I said, it's a backwater dependency for something extra in Gnome... Or something..... I didn't bother with it... Looking at the official Gnome build order list, there are alot of packages in there that I don't bother with. Of course, I think they have introduced quite a few more things in Gnome 2.10 that wasn't required in 2.8.3..... You'll have to do some research into sgml-tools and find out exactally what needs them...
i guess i might as well not compile it and see what happens :P less proper but definitely less time consuming seen what kind of a poor documentation of dependencies there's on gnome (almost unbelieveable, but that's the way it is).
Originally posted by acidjuice yep, that's what i meant when i explained why i still use 32-bit firefox.
No need to. The Blackdown x86_64 JRE DOES have a plugin ! Just link it to your 64bit firefox plugins dir (don't copy !) and you're good to go.
Flash though IS a problem with 64bit firefox (not with 64bit konqueror though, that one can be made to use the 32bit plugin... don't ask me how, I don't use it).
Distribution: Debian, edition depends on what i run it, wheezy on main box.
Posts: 91
Rep:
slamd64 in next year maybe...
Ok
Took my time yesterday and wiped off one 20 gig partition for slamd64 trial.
Good news is, i got it installed -at least almost.
Bad news is, that something is messed up in 64amd kernel.
result is working system without sound and network.(if you don't mind use firewire as network device.)
reason is'nt missing driver for marvell-yukon gigab adapter phy with 88E8001-lkj chip.
nor is'nt reason that alsa is unable to play this alc850 codec on my MB A8V deluxe wifi wersion i have.
nope, something makes it behave in way it does not route irq-s on slamd64, and kernel and drivers fail to see some pci devices after boot.
pci=routeirq and disable ACPI workarounds do not help.
and there is no difference, built in kernel or module loading.
just device is absent and that's it.
quick google-moogle resolved other people have similar problems with usb devices.and they had to hack drivers source to force em show devices again.
i am freak, but not to that degree.
so, what to say? nice desktop, pretty fast, but just take additional soundcard and lan adapter?
nope.
part2 > as i already had googled 2 additional hours for nothing, was showtime for debian.
amd64 netinstall cd (90 mb smth), boot from it and voilaa'! i had network.
now half of hour googling working 64-bit debian mirrors and editing apt sources.
>desktop install> synaptics and can choose between xfce4, flux, kde and gnome.
all working, sound is playing.
didn't compile ntfs write support yet nor new kernel.
BUT THIS IS FAST.Never handled something as fast my desktop is now.
XP on my second partition have a lot to learn to get even close to this performance i am getting from debian with generic 64 kernel.
uname -a: Linux (myboxname) 2.6.8-11-amd64-generic #1 Wed May 4 20:03:43 UTC 2005 x86_64 GNU/Linux
little spam from console:
0000:00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 0282
0000:00:00.1 Host bridge: VIA Technologies, Inc.: Unknown device 1282
0000:00:00.2 Host bridge: VIA Technologies, Inc.: Unknown device 2282
0000:00:00.3 Host bridge: VIA Technologies, Inc.: Unknown device 3282
0000:00:00.4 Host bridge: VIA Technologies, Inc.: Unknown device 4282
0000:00:00.7 Host bridge: VIA Technologies, Inc.: Unknown device 7282
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800 South]
0000:00:07.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80)
0000:00:08.0 RAID bus controller: Promise Technology, Inc. PDC20378 (FastTrak 378/SATA 378) (rev 02)
0000:00:0a.0 Ethernet controller: Marvell Technology Group Ltd. Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (rev 13)
0000:00:0e.0 Network controller: RaLink Ralink RT2500 802.11 Cardbus Reference Card (rev 01)
0000:00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80)
0000:00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
0000:00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
0000:00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
0000:00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
0000:00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
0000:00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
0000:00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [K8T800 South]
0000:00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
0000:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
0000:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
0000:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
0000:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
0000:01:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 MX 440] (rev a3)
video is as is, not gaming box.
am still missing Xorg and kde latest eyecandy....
and not installed java jet.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
I didn't bother with it... Looking at the official Gnome build order list, there are alot of packages in there that I don't bother with. Of course, I think they have introduced quite a few more things in Gnome 2.10 that wasn't required in 2.8.3..... You'll have to do some research into sgml-tools and find out exactally what needs them...
