Lenz, Is SuSE 6.4 going to have the ability to install the ReiserFS directly from the distribution CDs? Lenz Grimmer wrote:

Hi,

On Thu, 13 Jan 2000, Alexander Daniloff wrote:

...

I got a couple of question regarding new Reiser journaling file system. Is somebody of you actually using it?

Yes, we use it internally on quite a lot of machines. I have a reiserfs partition on my personal workstation:

grimmer@Wiles:~ > mount | grep reiserfs /dev/sda4 on /space type reiserfs (rw) grimmer@Wiles:~ > df -h /dev/sda4 Filesystem Size Used Avail Use% Mounted on /dev/sda4 4.4G 1.2G 3.2G 27% /space

Our main development server also runs on reiserfs:

grimmer@Hilbert:~ > mount | grep reiserfs /dev/sda3 on /work type reiserfs (rw,noatime) grimmer@Hilbert:~ > df -h /dev/sda3 Filesystem Size Used Avail Use% Mounted on /dev/sda3 235G 161G 74G 69% /work

...

Is there any advantages Reiser FS over EXT2 in terms of speed, ability to recover after crash?

Yes, that's its main intension :)

It is significantly faster because it is using a balanced tree algorithm to store the files. And since it is a journaling file system, you do not have hours of filesystem-check after a crash. Pretty neat!

For more info about it, see http://devlinux.com/projects/reiserfs/

...

Can I install reiser fs with my plain kernel 2.2.14?

There is an article in our support database (german only, the translation is in the queue - but Babelfish should give you a clue):

http://sdb.suse.de/sdb/de/html/tw_reiser.html

Bye, LenZ

-- Avi Schwartz Get a Life avi@CFFtechnologies.com Get Linux -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

Has anyone gotten serial consoles to work with SuSE? I am

I have got them to work. It takes a little tweaking. I often get the respawing too fast message. I run it through strace and it connects. I can then see where the trouble lies. I use S0:123:respond:/sbin/agetty -mL 19200,9600,2400 ttyS0 As a test to see if the port is open try echo junk > /dev/ttyS0 or the port of your choice you should see "junk" on the terminal screen if there is nothing then the ports are not connected, if you see stuff but not "junk" then the comm settings are off. Check the baud and parity. ----- Original Message ----- From: Herman Knief <herman@knief.net> To: <suse-linux-e@suse.com> Sent: Tuesday, February 22, 2000 11:33 AM Subject: [SLE] Serial Console... trying to use a

Livingston PM-25 to hook up a bunch of systems, but can't seem to get it to work.

Tried agetty, mgetty, etc. and no luck. I have gotten the box to spew boot messages to the serial port, but the getty doesn't respawn to offer the login when it's done.

Is there something else I need to do, other than setup the inittab? - And yes, serial console support is compiled into the kernel.

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

Sorry it has been so long, but I've only now gotten back to this. So, here's where I'm at. Tried to run the below setup. In fact, also ran the agetty direct from the command line. It seems to keep dying and then being respawn by init, so the inittab option is just broken. When running the command line version, I get a whole lot of garbage... it seems to try many different things, then exits. I know the serial port is connected right, because I see the boot messages during startup, but once the machine is up, I never get a login on the serial port... Any helpful hints or advice would be much appreciated. TIA - Herman # strace /sbin/agetty -L 9600 ttyS0 vt100 ( a whole lot of this, where the "read" line chages to different values <ttyS0, ttyS1, pts 0-6>, but also ends up wit the same result) -------------8<-------------- fcntl(3, F_SETLKW, {type=F_RDLCK, whence=SEEK_SET, start=0, len=0}) = 0 read(3, "\10\0\0\0y\25\0\0pts/2\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 384) = 384 fcntl(3, F_SETLKW, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0}) = 0 rt_sigaction(SIGALRM, {SIG_DFL}, NULL, 8) = 0 alarm(0) = 1 alarm(0) = 0 rt_sigaction(SIGALRM, {0x400fcf80, [], 0x4000000}, {SIG_DFL}, 8) = 0 alarm(1) = 0 fcntl(3, F_SETLKW, {type=F_RDLCK, whence=SEEK_SET, start=0, len=0}) = 0 read(3, "\10\0\0\0\202\25\0\0pts/9\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 384) = 384 fcntl(3, F_SETLKW, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0}) = 0 rt_sigaction(SIGALRM, {SIG_DFL}, NULL, 8) = 0 alarm(0) = 1 alarm(0) = 0 rt_sigaction(SIGALRM, {0x400fcf80, [], 0x4000000}, {SIG_DFL}, 8) = 0 alarm(1) = 0 fcntl(3, F_SETLKW, {type=F_RDLCK, whence=SEEK_SET, start=0, len=0}) = 0 read(3, "\10\0\0\0\343\25\0\0pts/10\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 384) = 384 fcntl(3, F_SETLKW, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0}) = 0 rt_sigaction(SIGALRM, {SIG_DFL}, NULL, 8) = 0 --- SIGALRM (Alarm clock) --- +++ killed by SIGALRM +++ Mike Kenzie wrote:

I have got them to work. It takes a little tweaking. I often get the respawing too fast message.

I run it through strace and it connects.

I can then see where the trouble lies.

I use

S0:123:respond:/sbin/agetty -mL 19200,9600,2400 ttyS0

As a test to see if the port is open try

echo junk > /dev/ttyS0 or the port of your choice

you should see "junk" on the terminal screen if there is nothing then the ports are not connected, if you see stuff but not "junk" then the comm settings are off. Check the baud and parity.

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/