I believe udev does the hotplugging duties now, but don't quote me on that.Bulkley wrote:So does mine, now. Thanks. I find this interesting. Does the 2.6 kernels do the hardware detection? Discover1 seems to have become redundant.
Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
HOWTO: Speeding up Debian
- chrismortimore
- Posts: 849
- Joined: 2007-04-24 06:34
- Location: Edinburgh, UK
Desktop: AMD Athlon64 3800+ Venice Core, 2GB PC3200, 5x320GB WD 7200rpm Caviar RE2 (RAID5), Nvidia 6600GT 256MB
Laptop: Intel Pentium M 1.5GHz, 512MB PC2700, 60GB 5400rpm IBM TravelStar, Nvidia 5200Go 64MB
Laptop: Intel Pentium M 1.5GHz, 512MB PC2700, 60GB 5400rpm IBM TravelStar, Nvidia 5200Go 64MB
-
- Posts: 17
- Joined: 2007-02-09 11:24
- Contact:
".....I believe udev does the hotplugging duties now, but don't quote me on that...."
That is correct sir Although the kernels have came along way to help this process
discover1 (or discover2) is really just needed to discover non-hotplug stuff at boot-time and load the needed modules.... discover is really just simple program that parses the data in /proc/ and compares it to a XML database found in /lib/discover/
If your hardware doesnt change alot or you are comfortable editing /etc/modules then its not needed.
In other words: If the module for your hardware is already in /etc/modules.... its already been detected no reason to discover1
BTW chris:
Our conversation the other day on parameter passing finially intrigued me into whipping up a test version.. Alot of rewritting but I think I'll have a working version soon.
Take Care,
-Justin
One Mynds Eye
That is correct sir Although the kernels have came along way to help this process
discover1 (or discover2) is really just needed to discover non-hotplug stuff at boot-time and load the needed modules.... discover is really just simple program that parses the data in /proc/ and compares it to a XML database found in /lib/discover/
If your hardware doesnt change alot or you are comfortable editing /etc/modules then its not needed.
In other words: If the module for your hardware is already in /etc/modules.... its already been detected no reason to discover1
BTW chris:
Our conversation the other day on parameter passing finially intrigued me into whipping up a test version.. Alot of rewritting but I think I'll have a working version soon.
Take Care,
-Justin
One Mynds Eye
- chrismortimore
- Posts: 849
- Joined: 2007-04-24 06:34
- Location: Edinburgh, UK
Huzzah Chalk one up for Chrisonemyndseye wrote:That is correct sir Although the kernels have came along way to help this process
Yeah, it's a real pest tweaking stuff to "clean up" code. Just now I'm writing a 3D engine (that I'm hoping to turn into a racing game eventually), and I'm tweaking it all to work with classes. Probably going to start again and import code as I need it, might be easieronemyndseye wrote:Our conversation the other day on parameter passing finially intrigued me into whipping up a test version.. Alot of rewritting but I think I'll have a working version soon.
Desktop: AMD Athlon64 3800+ Venice Core, 2GB PC3200, 5x320GB WD 7200rpm Caviar RE2 (RAID5), Nvidia 6600GT 256MB
Laptop: Intel Pentium M 1.5GHz, 512MB PC2700, 60GB 5400rpm IBM TravelStar, Nvidia 5200Go 64MB
Laptop: Intel Pentium M 1.5GHz, 512MB PC2700, 60GB 5400rpm IBM TravelStar, Nvidia 5200Go 64MB
tips galore
Thanks for the tips, everyone. I tried out a few, and so far so good.
Cheers.
Cheers.
Don't Panic!
Re: HOWTO: Speeding up Debian
Brah!, I'm right there with you, and I hate that pesky mouse in my way. Didn't know of 'unclutter'. Kudos for mentioning it!Lou wrote:<snip>
ENTERING THE X SYSTEM
$ nano .xinitrc
and i added the following lines:
unclutter &
<snip>
I did find a small problem using 'unclutter'; console games. I loaded Q3A and kept getting turned around, literally, in the game while mousing and keyboarding. Turned off unclutter and the game play was normal. So I wrote a little script to handle it. It goes like this (any corrections accepted if I goofed anywhere):Lou wrote:Hehe!
He who reads, finds out! - chinese storekeeper by my house
#!/bin/bash
killall unclutter &&
/usr/local/games/ioquake3/ioquake3.i386
unclutter&
I found I needed to leave off the '&' at the end of line three as the console hung awaiting the next command. Maybe ioquake3.i386 closes and releases without need of the '&' or '&&'.
This has been a most informative thread. I was wondering, if anyone can add tips on speeding up Debian response over the Internet. Are there firewall settings that can be adjusted? (I use Firestarter) Any tuning that might help video cards respond faster? (generic adjustments; not specific to make or model) Tuning network cards? Anything else?
Speed up ? I dunno, but this should help on the matter in general:Bulkley wrote:This has been a most informative thread. I was wondering, if anyone can add tips on speeding up Debian response over the Internet. Are there firewall settings that can be adjusted? (I use Firestarter) Any tuning that might help video cards respond faster? (generic adjustments; not specific to make or model) Tuning network cards? Anything else?
http://www.aboutdebian.com/network.htm
http://tinyurl.com/6rk4a
Try turning off the firewall and see if there's improvements - the kernel does nearly all firewalling by default any way - except for, I think, indent and port 113 which are "closed".
-
- Posts: 42
- Joined: 2005-06-24 18:54
in laymans termsHevoos wrote:What does these things do:
openbsd-inetd
rc.local ?
How do I install and use localpurge? Apt-get clean is also a great thing to do.
inetd is basically a superserver. some net services(read ftp, ssh, et al) can be set to rely on this to run. not necessarily necessary on any system.
rc.local is basically a startup script. The only thing I have in rc.local is esd for my sound.
- chrismortimore
- Posts: 849
- Joined: 2007-04-24 06:34
- Location: Edinburgh, UK
inetd is hardly used these days, as most of these services are now started by their own init.d scripts anyway (because you get greater control over them when you don't use inetd). The only thing I have that uses inetd is vmware.jombeewoof wrote:inetd is basically a superserver. some net services(read ftp, ssh, et al) can be set to rely on this to run. not necessarily necessary on any system.
Desktop: AMD Athlon64 3800+ Venice Core, 2GB PC3200, 5x320GB WD 7200rpm Caviar RE2 (RAID5), Nvidia 6600GT 256MB
Laptop: Intel Pentium M 1.5GHz, 512MB PC2700, 60GB 5400rpm IBM TravelStar, Nvidia 5200Go 64MB
Laptop: Intel Pentium M 1.5GHz, 512MB PC2700, 60GB 5400rpm IBM TravelStar, Nvidia 5200Go 64MB
- chrismortimore
- Posts: 849
- Joined: 2007-04-24 06:34
- Location: Edinburgh, UK
I think some things require it to be installed. But you don't have to run it. The only package I have installed that needs it is "netbase" though.Bulkley wrote:Can I safely remove inetd?
Desktop: AMD Athlon64 3800+ Venice Core, 2GB PC3200, 5x320GB WD 7200rpm Caviar RE2 (RAID5), Nvidia 6600GT 256MB
Laptop: Intel Pentium M 1.5GHz, 512MB PC2700, 60GB 5400rpm IBM TravelStar, Nvidia 5200Go 64MB
Laptop: Intel Pentium M 1.5GHz, 512MB PC2700, 60GB 5400rpm IBM TravelStar, Nvidia 5200Go 64MB
I discovered that inetd has been replaced by xinetd.
Swappiness is a new term for me. It refers to the choice the computer makes between using memory or harddrive swap partition. The swappiness is usually set to 60, but we can change it. Some experts set it to 100; others to 0. If you have a lot of memory, you can speed your machine behavior by lowering its swappiness. I set mine to 10 but everyone has to make his own decission on this. Check this article http://www.linuxjournal.com/article/8308 for instructions.
Swappiness is one of those issues that needs some benchmarking tools. Any suggestions?
Swappiness is a new term for me. It refers to the choice the computer makes between using memory or harddrive swap partition. The swappiness is usually set to 60, but we can change it. Some experts set it to 100; others to 0. If you have a lot of memory, you can speed your machine behavior by lowering its swappiness. I set mine to 10 but everyone has to make his own decission on this. Check this article http://www.linuxjournal.com/article/8308 for instructions.
Swappiness is one of those issues that needs some benchmarking tools. Any suggestions?
-
- Posts: 1
- Joined: 2007-06-03 21:25
- Location: Zurich, Switzerland
omitted stuff
Hi all
I've found this thread by chance when searching for the relevant info. It was a good read. Many tips have been discussed. Yet a few have been forgotten. Therefore I have registered myself and here are some more:
- first of all, before messing around in your system, make some investigations what really eats up processor cycles and/or memory. Useful candidates are top, xrestop, dpigs and du -S.
- concerning the discussion about display managers:
I agree that wdm is the best one on small systems, but why use a dm at all? If you don't like logging in on a text console, try Qingy. I love it.
- nobody mentioned hdparm. When it comes to speeding up disk access there's no way around hdparm.
- if you're on a particularly small system (like me on my old laptop with a 300MHz processor and 32MBy of RAM), you might get even a shorter bootup when changing getty for fgetty, a very small and fast getty clone.
- in terms of window managers, my personal favorite on small systems is evilwm. It's very lightweight and fast. No bells and whistles, but a set of very good keyboard shortcuts. And it's easily customizable.
- network speed: you might get some speed improvement by issuing
# echo "0" > /proc/sys/net/ipv4/tcp_sack
# echo "0" > /proc/sys/net/ipv4/tcp_timestamps
- it happens that you are connected to a router which does not understand ipv6. You can see that if your browser always waits before transmitting data. In that case disable ipv6 entirely.
- have a look at the powertweak package
- concerning the bootup process there are interesting reads here and here.
- if you're looking for speeding up iceweasel (former firefox) you might be interested in this.
- for speeding up the desktop experience there were two articles in Linux Journal two years ago. Some stuff is certainly still useful.
And then we could join forces and update the wiki article to the same topic at http://wiki.debian.org/?LinuxSpeedup .
Cheers
I've found this thread by chance when searching for the relevant info. It was a good read. Many tips have been discussed. Yet a few have been forgotten. Therefore I have registered myself and here are some more:
- first of all, before messing around in your system, make some investigations what really eats up processor cycles and/or memory. Useful candidates are top, xrestop, dpigs and du -S.
- concerning the discussion about display managers:
I agree that wdm is the best one on small systems, but why use a dm at all? If you don't like logging in on a text console, try Qingy. I love it.
- nobody mentioned hdparm. When it comes to speeding up disk access there's no way around hdparm.
- if you're on a particularly small system (like me on my old laptop with a 300MHz processor and 32MBy of RAM), you might get even a shorter bootup when changing getty for fgetty, a very small and fast getty clone.
- in terms of window managers, my personal favorite on small systems is evilwm. It's very lightweight and fast. No bells and whistles, but a set of very good keyboard shortcuts. And it's easily customizable.
- network speed: you might get some speed improvement by issuing
# echo "0" > /proc/sys/net/ipv4/tcp_sack
# echo "0" > /proc/sys/net/ipv4/tcp_timestamps
- it happens that you are connected to a router which does not understand ipv6. You can see that if your browser always waits before transmitting data. In that case disable ipv6 entirely.
- have a look at the powertweak package
- concerning the bootup process there are interesting reads here and here.
- if you're looking for speeding up iceweasel (former firefox) you might be interested in this.
- for speeding up the desktop experience there were two articles in Linux Journal two years ago. Some stuff is certainly still useful.
And then we could join forces and update the wiki article to the same topic at http://wiki.debian.org/?LinuxSpeedup .
Cheers
Just off the top of my head, you need cron to:
- rotate logs
- update the find database
- update man database
- take care of lost+found
- take care of exim (default MTA - required for error messages, etc.)
I am sure there are plenty of others. Disabling cron is just asking for trouble in the long run. Cron jobs are an essential part of Linux systems. Essential programs assume that it is up and running. Do NOT turn crond off.
- rotate logs
- update the find database
- update man database
- take care of lost+found
- take care of exim (default MTA - required for error messages, etc.)
I am sure there are plenty of others. Disabling cron is just asking for trouble in the long run. Cron jobs are an essential part of Linux systems. Essential programs assume that it is up and running. Do NOT turn crond off.