Out of curiosity, what kind of tweaks did you give KDE to get it so responsive? I keep reading about how fast kde3 is, and I run it at home, and don't seem to notice the difference from kde2-kde3. In my opionion, kde1 was fast. I'm running the default RH 7.3 install on my AMD 700MHz, 768MB RAM.
The one thing I find real annoying, is clicking on any folder. It seems to take a while to load, since I'm guessing it's loading part of konqueror. Why not cache this in memory when kde loads, so when you click on a folder it pops open. If there is a way to do this, or a website with kde performance tweaks, please point me in the right direction:-)
well, it does have the source rpm, so I guess you could audit it. It would be nice to have the md5sums, though. I'm guessing the author is trying to be nice in building an rpm.spec from the source, and also including some binary builds for RH 7.3
I have had bad luck with linuxconf messing up settings, and then having to go in with vi to fix the config files. It would be great if linuxconf was bug free, since I would prefer to use it.
but that's still a far cry from scoadmin. Maybe I'll stick too vi, and editing files, and restarting services. At least with that method, if you break something, it's your fault, and not the admin tools fault (or bug, like a lot of the linuxconf modules)
I agree. I would love to see something as complete as scoadmin on linux (redhat). You could configure just about everything from the command line, now all the RH utils are GUI based, requiring X11. It was nice to be able to ssh into a SCO box, and configure a printer. linuxconf had a text based interface, but it is no longer present in RH 7.3. What happened? What is a good text based config utility for RH (besides vi)?
I have one IDE HD, and 2 SCSI HD's in my desktop machine, and if I really crank on the IDE, you can see the slow down, where the SCSI HD's keep pace. I also have a CDRW, DVD, Scanner, Zip drive, and a CDROM on my SCSI chain - burning, ripping, and doing normal tasks does not slow my system down. Trying that on a system with IDE, tends to slow it down a bit. With my 29160 controller, I also have plenty of room for more HD's if I want.
I recently helped a friend install a CDRW (IDE) in his machine, and the first thing I tried was burning on the fly. Nope. Sorry. Need another IDE bus for that, so that the CDROM and CDRW are on seperate buses. Not true with SCSI. I burn on the fly all the time.
I guess I just like the overall flexibility with SCSI.
Why such the large difference between binary sizes? The Linux version weighs in at ~ 66.6MB, wheras the win32 comes in around 48.9MB. I usually find the oposite to be true with linux v. win32 binaries.
Sure, but the proof part is tough. Heck, any system that is not managed properly, could have any jr. admin be able to get in with a local root exploit. Unless you have a camera, and keystroke recorder, how do you prove it? With cron jobs, and log cleaners, you would never know the time it happened either. I guess we will have to wait for retinal scans, before we can take that out of the equation. For now, the reality is that somebody could be root, and not need the password.
Like I said in my original post, I realize it's not a moral thing, and I would never do such a thing. All I'm saying, is that it's a possibility, and someone who knows what they are doing could really cover their tracks, and I know of two cases where it's happened, and management was left scratching their heads! (as far as I know, they still have not been caught to this day)
I work as an admin for a family business (so I would never attempt such a task), and have two people working under me. For one, they don't know enough about *nix (yet) to do any harm to our systems, and with tools like sudo, and heavily patched systems, I don't have to worry about root being comprimised. I just hope other companies take similar precautions.
Take the code red worm (my IDS is still logging attempts!!) Since worms like code red can happen, I feel that something like the above could easily happen, due to admin ignorance, and un-patched systems.
I'm sure the two companies that this happened to thought the same thing you did (and for obvious reasons, I will not release the company names)
I'm not sure if they realize how much power IT workers yield. I've heard of terrible stories of disgruntled IT workers writing worms/trojan horses, so that if they are let go, or in this case given a pay decrease, unleash the worm, and *poof* - bye bye system. I have even heard one story of an admin altering a backup script to send out email results that the backup was working fine. Months went bye, and when the worm went into effect, it turned out all the backups were blank tapes.
I realize that this is not the moral thing for an IT worker to do, but it's a possibility none the less.
VOCP is a complete voice messaging solution, featuring voicemail boxes, email pagers and DTMF "command shells". Users can navigate the system using a touch-tone phone, leave and retrieve messages (by phone or through the web interface) and execute programs (optionally feeding the program numeric or even text input) on the host machine using the DTMF command shells.
Since it's mostly perl, I'm sure you could hack up something similar to what you are looking for.
Sheesh! People are computing faster than I am, even at 40k feet. Our neighborhood still has the same copper that was put up in the early 60's. No connections over 31.6:-(
It certainly will be interesting to see who holds the reigns to that machine. I'm sure that the COSI would be more than willing to further the opensource development model, but allowing access to such a machine would require some strict security measures. I can't imagine giving anyone access to such a powerful machine, without some kind of control. This should certainly bring opensource development to another level.
Regardless, I can't say enough about how happy I am with the COSI, and all their work. I'm looking forward to looking more in depth at their projects, and their implications.
That's great news about the Clarkson students. I'm glad to see that students at my old college are involved with Linux. I only wish I could be there participating.
Good job.
Bruce Garlock
Clarkson U. class of '95
Let's go tech!
i should have mentioned, that's what i was talking about:-) dreaming up the perfect level, one that involved the perfect timing, or you couldn't complete the board, and had to commit suicide!
2.2.19 for servers @ Work, which all have uptimes aproaching 1 year.
At home I use RH 7.2, with 2.4.17 vanilla. Can't seem to figure out what uses so much memory, because I have 768MB of RAM, and after a few days, it starts to swap. The 2.2.19 machines @ work, have never dipped into swap, and most of them are 256MB or lower.
I think 2.4.17 needs to iron out VM issues, before it will start being loaded on production machines.
Slashdot Mirror
I'm guessing this is because of build time optimizations? Maybe I'll grab the source RPM's, and see what can be done with them.
Out of curiosity, what kind of tweaks did you give KDE to get it so responsive? I keep reading about how fast kde3 is, and I run it at home, and don't seem to notice the difference from kde2-kde3. In my opionion, kde1 was fast. I'm running the default RH 7.3 install on my AMD 700MHz, 768MB RAM.
:-)
The one thing I find real annoying, is clicking on any folder. It seems to take a while to load, since I'm guessing it's loading part of konqueror. Why not cache this in memory when kde loads, so when you click on a folder it pops open. If there is a way to do this, or a website with kde performance tweaks, please point me in the right direction
well, it does have the source rpm, so I guess you could audit it. It would be nice to have the md5sums, though. I'm guessing the author is trying to be nice in building an rpm.spec from the source, and also including some binary builds for RH 7.3
and still riddled with security holes! Check out the latest (just today)
I have had bad luck with linuxconf messing up settings, and then having to go in with vi to fix the config files. It would be great if linuxconf was bug free, since I would prefer to use it.
Well, I did find:
/usr/sbin/setup
but that's still a far cry from scoadmin. Maybe I'll stick too vi, and editing files, and restarting services. At least with that method, if you break something, it's your fault, and not the admin tools fault (or bug, like a lot of the linuxconf modules)
I agree. I would love to see something as complete as scoadmin on linux (redhat). You could configure just about everything from the command line, now all the RH utils are GUI based, requiring X11. It was nice to be able to ssh into a SCO box, and configure a printer. linuxconf had a text based interface, but it is no longer present in RH 7.3. What happened? What is a good text based config utility for RH (besides vi)?
HERE is a link to whats new in this release.
That's interesting, maybe his system can handle it. Thanks for the info!
I have one IDE HD, and 2 SCSI HD's in my desktop machine, and if I really crank on the IDE, you can see the slow down, where the SCSI HD's keep pace. I also have a CDRW, DVD, Scanner, Zip drive, and a CDROM on my SCSI chain - burning, ripping, and doing normal tasks does not slow my system down. Trying that on a system with IDE, tends to slow it down a bit. With my 29160 controller, I also have plenty of room for more HD's if I want.
I recently helped a friend install a CDRW (IDE) in his machine, and the first thing I tried was burning on the fly. Nope. Sorry. Need another IDE bus for that, so that the CDROM and CDRW are on seperate buses. Not true with SCSI. I burn on the fly all the time.
I guess I just like the overall flexibility with SCSI.
Why such the large difference between binary sizes? The Linux version weighs in at ~ 66.6MB, wheras the win32 comes in around 48.9MB. I usually find the oposite to be true with linux v. win32 binaries.
Have a look at this article, which explains that sabotage does happen, and denying it is part of the issue:
http://www.cio.com/archive/010102/security.html
Sure, but the proof part is tough. Heck, any system that is not managed properly, could have any jr. admin be able to get in with a local root exploit. Unless you have a camera, and keystroke recorder, how do you prove it? With cron jobs, and log cleaners, you would never know the time it happened either. I guess we will have to wait for retinal scans, before we can take that out of the equation. For now, the reality is that somebody could be root, and not need the password.
Like I said in my original post, I realize it's not a moral thing, and I would never do such a thing. All I'm saying, is that it's a possibility, and someone who knows what they are doing could really cover their tracks, and I know of two cases where it's happened, and management was left scratching their heads! (as far as I know, they still have not been caught to this day)
I work as an admin for a family business (so I would never attempt such a task), and have two people working under me. For one, they don't know enough about *nix (yet) to do any harm to our systems, and with tools like sudo, and heavily patched systems, I don't have to worry about root being comprimised. I just hope other companies take similar precautions.
Take the code red worm (my IDS is still logging attempts!!) Since worms like code red can happen, I feel that something like the above could easily happen, due to admin ignorance, and un-patched systems.
I'm sure the two companies that this happened to thought the same thing you did (and for obvious reasons, I will not release the company names)
Is that real enough for ya?
Certainly, but I'm just trying to play devils advocate, here.
I'm not sure if they realize how much power IT workers yield. I've heard of terrible stories of disgruntled IT workers writing worms/trojan horses, so that if they are let go, or in this case given a pay decrease, unleash the worm, and *poof* - bye bye system. I have even heard one story of an admin altering a backup script to send out email results that the backup was working fine. Months went bye, and when the worm went into effect, it turned out all the backups were blank tapes.
I realize that this is not the moral thing for an IT worker to do, but it's a possibility none the less.
From the freshmeat "About" section:
VOCP is a complete voice messaging solution, featuring voicemail boxes, email pagers and DTMF "command shells". Users can navigate the system using a touch-tone phone, leave and retrieve messages (by phone or through the web interface) and execute programs (optionally feeding the program numeric or even text input) on the host machine using the DTMF command shells.
Since it's mostly perl, I'm sure you could hack up something similar to what you are looking for.
VOCP Homepage
Sheesh! People are computing faster than I am, even at 40k feet. Our neighborhood still has the same copper that was put up in the early 60's. No connections over 31.6 :-(
Looks like just adding an equal sign:
/cvs/src/usr.bin/ssh/channels.c,v
RCS file:
retrieving revision 1.170
retrieving revision 1.171
diff -u -r1.170 -r1.171
--- channels.c 27 Feb 2002 21:23:13 -0000 1.170
+++ channels.c 4 Mar 2002 19:37:58 -0000 1.171
@@ -146,7 +146,7 @@
{
Channel *c;
- if (id < 0 || id > channels_alloc) {
+ if (id < 0 || id >= channels_alloc) {
log("channel_lookup: %d: bad id", id);
return NULL;
}
Any idea when RH's 2.4.17 will be the "supported" kernel? I am using vanilla 2.4.17 now, since the ieee1324 drivers lockup my RH 2.4.9 kernel.
It certainly will be interesting to see who holds the reigns to that machine. I'm sure that the COSI would be more than willing to further the opensource development model, but allowing access to such a machine would require some strict security measures. I can't imagine giving anyone access to such a powerful machine, without some kind of control. This should certainly bring opensource development to another level.
Regardless, I can't say enough about how happy I am with the COSI, and all their work. I'm looking forward to looking more in depth at their projects, and their implications.
Damn fine job!
That's great news about the Clarkson students. I'm glad to see that students at my old college are involved with Linux. I only wish I could be there participating.
Good job.
Bruce Garlock
Clarkson U. class of '95
Let's go tech!
i should have mentioned, that's what i was talking about :-) dreaming up the perfect level, one that involved the perfect timing, or you couldn't complete the board, and had to commit suicide!
drol, sneakers, choplifter, joust, beyond castle wolfenstein, beagle brothers
:-)
oh, the memories
did anyone else ever dream of the "perfect" lode runner level?
2.2.19 for servers @ Work, which all have uptimes aproaching 1 year.
At home I use RH 7.2, with 2.4.17 vanilla. Can't seem to figure out what uses so much memory, because I have 768MB of RAM, and after a few days, it starts to swap. The 2.2.19 machines @ work, have never dipped into swap, and most of them are 256MB or lower.
I think 2.4.17 needs to iron out VM issues, before it will start being loaded on production machines.