Google This Site]Well how 'bout that? After seeing Doomworld's 10-year anniversary coverage of DOOM, it remembered myself "damn, that Linux port of ZDoom I wanted to work on, I forgot all about it!" (Link) so first thing I did was going back to the ZDoom page (been a while) and first thing I see is that Randy's got a Linux install going! Good to know! If you need any help with the Linux port (or, hell, with Linux in general) let me know!
BTW Randy, if you like Linux From Scratch, I can guarantee you'll love Gentoo Linux. Think LFS, only with actual package management, Debian-style. I was a LFS user once, and I can tell you, manually hunting for dependencies and patches for stuff becomes annoying pretty fast. And let's face it, it really is a waste of time. All those problems go away with Gentoo, and you still have all the absolute power on everything, being a source-based system and all. It's been one year this month that I'm a Gentoo user, and I certainly wouldn't go back to LFS.
Linux!
Moderator: GZDoom Developers
-
IntergalacticWalrus
- Posts: 31
- Joined: Mon Sep 01, 2003 2:02 pm
- Location: E2M2, among the many UAC boxes
-
IntergalacticWalrus
- Posts: 31
- Joined: Mon Sep 01, 2003 2:02 pm
- Location: E2M2, among the many UAC boxes
-
Traumgeber
blank message
(this message can be deleted)
Last edited by Traumgeber on Wed Dec 17, 2003 7:31 pm, edited 1 time in total.
Oh yeah, that's a good experience. Pegging your CPU usage at 100% for a solid week compiling kernel, X, KDE or Gnome, and then, say, OpenOffice, all the GNU tools, and on and on and on ... makes for a pleasurable computing experience.IntergalacticWalrus wrote:Well it's not like you can't continue using your computer while compiling...
Yessiree.
-
Anonymous
Get a kernel with pre-empt and low-latency patches and you can compile to your heart's extent and still watch movies, play games or do anything you can normally do when there's no heavy-load process running.arioch wrote:Oh yeah, that's a good experience. Pegging your CPU usage at 100% for a solid week compiling kernel, X, KDE or Gnome, and then, say, OpenOffice, all the GNU tools, and on and on and on ... makes for a pleasurable computing experience.
Yessiree.
2.6.0 which includes them was apparently released yesterday. Hooray! Optionally you can just patch 2.4.x.
Randy, you probably already solved your problem with GNOME, but here's what someone posted on http://www.linuxgames.com:
Once you get into "Theme Preferences", click on the "Theme Details" button and you should be able to go over to "Window Border", and change it -- at least in GNOME 2.2 and above.
The only thing I've noticed pre-empt and low-latency patches ever doing for me is locking up the entire userspace whenever anything in the background pegs the cpu usage to 100%.warlock wrote:Get a kernel with pre-empt and low-latency patches and you can compile to your heart's extent and still watch movies, play games or do anything you can normally do when there's no heavy-load process running.
2.6.0 which includes them was apparently released yesterday. Hooray! Optionally you can just patch 2.4.x.
In other words: worse than useless.
And besides, the days of compiling shit for yourself quickly negate any single-percentage gains you might actually see, if any, for "optimizing" those programs for your system.
-
Hirogen2
- Posts: 2033
- Joined: Sat Jul 19, 2003 6:15 am
- Operating System Version (Optional): Tumbleweed x64
- Graphics Processor: Intel with Vulkan/Metal Support
- Location: Central Germany
- Contact:
I am not seeing any difference between a i586-precompiled versions of the kernel and glibc and self-compiled (-march=i686/athlon) one, but I guess that is just due to my 1666MHz, and I think there is of course a performance improvement.
You can still use self-compiled packages (appearing in the rpm db), even whilst using rpm. That's sweet.
You can still use self-compiled packages (appearing in the rpm db), even whilst using rpm. That's sweet.
-
Anonymous
You might want to check that you've 1. reniced X from -10 to 0 as distros typically do that and it's not a good idea with preemption, and 2. try the latest with 2.6.0 as it should've ironed out some preemption related bugs.arioch wrote: The only thing I've noticed pre-empt and low-latency patches ever doing for me is locking up the entire userspace whenever anything in the background pegs the cpu usage to 100%.
And besides, the days of compiling shit for yourself quickly negate any single-percentage gains you might actually see, if any, for "optimizing" those programs for your system.
The preemption and low-latency features should really be noticeable for the desktop user, if you need to get yourself motivated to try 2.6, read this article.
As for compiling for optimization - most of the time it will probably be completely useless. The kernel is one rare exception where it *might* make a little more of a difference but probably that is unnoticeable too. Especially if your distribution already compiles for i586 you're most likely not going to see any measurable benefit. Any benefit you can gain from self-compiling is likely to be around 5% at the absolute max and you're not going to see that kind of performance benefits with most of your apps. You can even slow your system down if you don't know what optimization features to use. And one has to ask, does 'ls' really have to be those microseconds faster? I think compiling everything from scratch is only useful as a learning experience (LFS), you can compile your own from src rpms or debs for the rare applications that really benefit from it anyway.
-
IntergalacticWalrus
- Posts: 31
- Joined: Mon Sep 01, 2003 2:02 pm
- Location: E2M2, among the many UAC boxes
I never had a problem with that. I guess sucky Open Sound System sound drivers are the cause, and the recent kernel desktop enhancements kind of work around those bad apples. Hopefully the much superior ALSA driver system is becoming the new sound standard, especially with the fact that it is now included with the 2.6 kernel.randy wrote:Yes, being able to drag a window around without sound breaking up is nice. But why did it take around ten years for this to become a standard part of the Linux kernel?
Most of the people working on the kernel do get paid for their work, actually. Open source is not all hobby projects, you know. Linux may have started as Linus' play toy, but these days many companies (IBM, HP, Novell, commercial distros) are willing to hire programmers to work on the kernel so they can have whatever they need implemented.HotWax wrote:Progress is slow when the programmers aren't getting paid?