Ask a LinuxWorld Exhibitor

Most Slashdot readers aren't coming to the LinuxWorld Conference and Expo in New York this week. If you're not coming, but you have a question you'd like to ask one of the exhibitors, please post it here. I promise to ask 10 of the highest-moderated exhibitor questions on your behalf, and I'll do my best to ask more than 10, time permitting. If you have a question for anyone who is holding a conference session or tutorial Thursday or Friday, please feel free to post it, too. I will try to ask speakers at least a few questions, but that's chancier than getting hold of exhibitors (who are in booths where they're easy to find), so no promises. One question per post, please. Hopefully, I'll have time to type up the answers over the weekend and post them Monday or Tuesday.

Comments

To the KDE team

[secondsun]

Which will come first, Duke Nukem Forever or KDE 3.1?

You knew it was coming

[Anonymous Coward]

Vi or Emacs?

Re:Ask a Linux Administrator? Is this, TheOnion?

[vaxer]

Dear Linux Administrator,

I'm a divorced mother of seven trying to put my life put back together after the death of my fourth husband. My kids still blame me for his death (it wasn't my fault, honest!), and I'm having a tough time meeting new people. What should I do?

-Sleepless in Sarasota

Dear Sleepless in Sarasota,

Since uugetty is part of getty_ps you'll first have to install getty_ps. If you don't have it, get the latest version from metalab.unc.edu:/pub/Linux/system/serial. In particular, if you want to use high speeds (57600 and 115200 bps), you must get version 2.0.7j or later. You must also have libc 5.x or greater.

By default, getty_ps will be configured to be Linux FSSTND (File System Standard) compliant, which means that the binaries will be in /sbin, and the config files will be named /etc/conf.{uu}getty.ttySN. This is not apparent from the documentation! It will also expect lock files to go in /var/lock. Make sure you have the /var/lock directory.

If you don't want FSSTND compliance, binaries will go in /etc, config files will go in /etc/default/{uu}getty.ttySN, and lock files will go in /usr/spool/uucp. I recommend doing things this way if you are using UUCP, because UUCP will have problems if you move the lock files to where it isn't looking for them.

getty_ps can also use syslogd to log messages. See the man pages for syslogd(1) and syslog.conf(5) for setting up syslogd, if you don't have it running already. Messages are logged with priority LOG_AUTH, errors use LOG_ERR, and debugging uses LOG_DEBUG. If you don't want to use syslogd you can edit tune.h in the getty_ps source files to use a log file for messages instead, namely /var/adm/getty.log by default.

Decide on if you want FSSTND compliance and syslog capability. You can also choose a combination of the two. Edit the Makefile, tune.h and config.h to reflect your decisions. Then compile and install according to the instructions included with the package.

Let's have some fun with this

[fobbman]

Okay, we've got Rob promising to ask the ten highest-moderated questions. Why don't we have him look for booth babes and ask if he can get the source to their hearts or maybe even walk up to various vendors and ask if his butt would look good in pleather?

Can I have a t-shirt?

[stecker]

No, I don't want the crappy "relaxing ball". I want the t-shirts that i KNOW you have under the counter. No, I don't want to have a discussion with you about my enterprise needs. I just need a t-shirt. Don't make me come back there and get it.