Log in

No account? Create an account
Linux Community's Journal
[Most Recent Entries] [Calendar View] [Friends View]

Wednesday, February 25th, 2004

Time Event
Upgrading to the 2.6x kernel
Today slashdot is linking to a white paper the provides instruction on how to upgrade your kernel to version 2.6x. For those who are interested, you can read the actual whitepaper here.

I am pretty much a linux newbie myself, and I was able to upgrade my kernel to 2.61 on Mandrake 9.2 without too many hiccups. I haven't reviewed the white paper, but someone in the linux community helped me to do it. You can read redgreenblue's excellent instructions in this thread.

((thanks again for all of your help on that, mr. redgreenblue))

Neato burrito.

Current Mood: fine
Linuxbeginner has an article about Slackware 9.1. I find it to be rather consistent with my own experience of the distro, and it sums up some of the points of it rather well.

Incidentally, if you want to learn Linux, there are few better ways than a "down to the metal" distro. Slackware is definitely one of those, with almost no added complexity or overhead over a basic BSD init style UNIX.
so, when i install fluxbox, when i get into it, all i get on the menu is xterm, restart, exit.

and the xterm button doesnt work.

i check the menu file, and its got the full menu goodness in there, but for some reason it doesnt look like fluxbox reads it.

any ideas?
My next odd ball question(s)....

The SCSI protocal allows for multiple (at least two) controllers on a chain. Normally you would have a controller on one end and a terminator on the other. In this case you have controllers on both ends, and the drives in the middle.

I've seen a friend do this set up with a keyboard(synthisizer) on one side and a windows box on the other, and it seemed to work well.

I would like to do something like this, but with a couple linux boxes sharing the drives. The idea is to create a pair od redundant servers. To start with I would have two high capacity drives on the chain running raid-1. Both systems would have unique IP's but then one would have an aliased addres. If the first system goes down, the second would sense it (ping test?) and alias the address to it's on network connection. If one linux system goes down, the other can assume the roll of the first and as they would share drives all the data would be up todate.

The selling points are, it would be faster than NFS, and would take less rack space in the colo.

Have any of you tried this under linux? Was it stable? If one system gets turned off, will the SCSI chain still be terminated?

<< Previous Day 2004/02/25
Next Day >>
About LiveJournal.com