really into answering questions these days.
Anyway, WinXP was sucking pretty bad on it, but Linux Mint Debian Edition is somewhat more responsive (and much more capable). I will see if I can scare up some more RAM.
I am, incidentally, thoroughly pissed at the computer shop that sold my grandmother an under-memoried machine with an IDE hard drive, but then put in a fairly nice (for the time) motherboard with SATA controller. All of it in a fancy-looking case
(window, LEDs, fan w/LED) for a little old lady to do her family tree software on. I don't know what they spent, but it was way more than they should have.
Sorry to hear that about your granny. My mum got similarly ripped off when she bought a computer at some store once. They sold her some freaky micro-atx mainboard with an amd cpu soldered onto the board. Total utter crap. Too few ram and crappy hd, too. I am currently building a new machine to replace the old machine she uses now, which is the computer my step brother gave her. DDR1 ram and AGP gpu. This new one is a c2d, 4gb ddr2 ram and a SSHD sata. Should be enough for her surfing needs.
Pentium 4 machines are only good as heating devices. If you are lucky, the socket can hold some c2d.
Pentium 4 machines are only good as heating devices. If you are
lucky, the socket can hold some c2d.
Hmmm... my guess is a pentium 4 will run a reasonable linux distro just fine.
Worst case, it should play DVDs and maybe handle some amateur radio stuff in my work room; that's where it is now.
I don't have the real hardware any more, but thought it would be fun to torture myself with this:
Think 8086 or 8088.
Semi active. They seem to loose the repo now and then. Someone makes floppy images every now and then.
Today, I learned the difference between sed and ed.
Use ed for in-place edit of files.
Use sed for streaming edits across pipes.
It's entertaining to use ed for scripting edits of files.
(e.g. echo ',s/foo/bar/g;w;q' | tr \; '\012' | ed -e $file )
Next you can learn "ex", which is basically vi without the fullscreen. Sounds silly, but if you need to pipeline a bunch of commands you already know them.
sed and awk together are powerful shell scripting tools. Perl is for weenies.
I'm fortunate that I have been using vi(m) for a long time now, so a lot of those commands are actually fairly well ingrained in me. That, I've noticed, has helped me get through some of the complicated commands pretty well. They are relatively intuitive to me.
This said, I still have to look up a lot of stuff. I was originally trying to do all of this with sed instead of ed, but found that ed did the job I wanted far better.
I'd probably feel similarly about emacs. I used to love emacs, though, but vi really grew on me.
I still prefer nano. I can use (and most important: exit!) vi, but I never ever cared to learn any of its alledgedly beneficial features. I'd rather describe it as "I can defend myself against *nixes which lack nano and fore me to use vi". Heck, I even do not know how to do a search in it (probably involves the /). I like how vi highlites brackets, and some things about rows it does better than nano. It is also smarter when it comes to charset conversion.
I did all my work on this current layout of citadel and all my hacking and slashing in the source in nano. In fact, I edit most html in nano, there is syntax highlighting and it is enough most of the time. Still, I am willing to give Aptana Studio a try for the next layout rework.
I use nano also but only because my old boss used it and it was default. When I ssh to godaddy I have to use