martouf

first off, you should read this document written by an admin of a site getting about 45 million hits a day. next, read this document written by an admin who has set up a multi-system-one-logfile configuration. Note the use of a pipe as the log destination. The general Apache documentation section on logs will round out your knowledge. Basically, you'll need to have Apache pipe all of the logging to the syslog daemon. With the logging all going to syslog, you set each system in the farm to send logging to the one log host you designate, whose own syslog receives the log data via a LAN.

sorry, a download connection can't be helped by using bittorrent. the bandwidth is too small to see any improvement from bittorrent. Words of Wisdom: Never underestimate the bandwidth of an envelope full of CDROMs sure, the latency is a beatch, but the bandwidth is tremendous! 8)

before googling, you should read up on the documentation provided by the Samba project ( samba.org ). It is possible to set up an network where Samba is the PDC but at present this would require your BDCs also to be running Samba. The reason is the domain database is maintained by a backend LDAP server, which is not what Windows does. If you install Cygwin on your Win2k system, you can then install Samba on it, too. A future version of Samba is expected to provide full Active Directory services.

'apt' is a Debian distro thing. 'up2date' is a Red Hat _less than or equal_ 9.0 thing. (it's 'yum' and 'apt' for Fedora, right?) which distro are you installing?

Hold, please! Now back up a step... Linuxant has a driver wrapper you buy so you can use WiFi equipment which have only Windows drivers. It's their WLAN Driverloader product. Conexant/Rockwell is the maker of HSF modem chipsets. HSF modems have free drivers available from Linuxant, limiting them to 14.4kbps. You pay Linuxant US$15 for full 56k and FAX. It doesn't look like Conexant has cooperated with anyone to make a fully featured free driver available. So it's not available. Winmodem makers want to be certain you don't configure their universal chipset in a way which violates the phone system rules and regulations in your country. If you must have a winmodem using a free driver, then you must choose one of the linmodems listed here. Either that, or use an external "real" modem like this external serial modem (US$18).

w00t! So many people have been struggling with this. Hooray for ALSA!

there are md5sum checkers available for Windows. read all about it here, then get your own copy. ps: found it by doing a google search of "md5sum windows"

it seems to me you've done all of the right things.. when you say you see the "Grub inscription", do you mean the Grub boot menu appears but is blank? Or do you mean the Grub boot menu appears and lists the two OSes, but just sits there waiting? Grub does provide a command line interface you can use to specify which disk partition it should try to boot from. can you boot from your Fedora disk, mount /dev/hda6 and post the contents of your /boot/grub/menu.lst and /boot/grub/device.map files?

ok, the distro is Red Hat based "pinktie". good. ulikeit: so now run 'sndconfig' as root and tell it to use the "Crystal CS423x" driver. That should get your sound card ready. Be sure to say 'yes' when it asks if it should test the sound system. If you don't want to run sndconfig, then just use the GUI Control Panel and go to the Hardware section to configure your soundcard. Use the "Crystal CS423x" driver. Later you can run aumix (if available), kmix (if KDE), or gmix (if Gnome) and set your sound levels.

oldspice: run "ls -l /dev/ptmx" and "id -a" logged in as the regular user account with which you've been having trouble. I realize you may need to login to vty2 (CTRL-ALT-F2) and copy down the output. Is the Yoper distro RPM based? running "rpm -ql devs | tail -10" ought to show a few documentation files/scripts included with the 'devs' package. (and probably in the /usr/share/doc/packages/devs directory) cibi3d: interesting. on my (working) system, my regular user account is not a member of the tty group, and yet /dev/ptmx and all /dev/pts/* are group owned by tty. In fact, all /dev/pts/* are user owned by my regular account in addition to group owned by tty.

good, that's "R" for recursive. plus one for remembering. the recursive directive is a command line switch, sooo... yup, it needs a hyphen char. try "chmod -R 777 topdirname" ciao!

consider this: if you run RH6 under VMware, you won't need to scrounge up and dust off a bunch of old hardware just to match RH6's native capabilities. As best I recall, there really wasn't any direct hardware support for things like DSL modems at the time. It was expected the DSL modem be an external box with an ethernet port.

uhh, Dan, where's the smiley? You know this Inter-web thing is just a fad, right? Dedicated 56kbps lines (56kbps data plus 8kbps signalling) are the way to go. None of this newfangled packet switching network stuff. Circuit switched ATM. Over fiber. p.s.

1. yes, it looks like you don't have minicom installed. you probably want to find the package and install it. 2. the account you're using belongs to the dialout group. That's good. No need to change anything there. 3. what happens if you modprobe ltmodem first, then ltserial second? 4. you obviously have a different LT modem driver than the one I found documentation about.. seems I found docs on the one for the 2.4 kernel (or earlier).

CNN.com - Technology - did a "preview" of RH6 in April 2000. what do you mean "high speed internet"? You mean faster than 56kbps? Oh! You mean hook up to a LAN. A LAN that's connected to the Internet. 8) Sure. if you've got a NIC it recognizes, you can set up your 10Mbps ethernet interface.. or would you prefer token ring (16Mbps)?

I'm pretty sure the Windows boot loader will automagically set itself up to give you a choice of WinXP or WinServer2003. If you install RHEL3 next, then GRUB can be set up to give you a choice of Windows or RHEL3. So, sure, you can do this.. install the Windows stuff first and RHEL3 last. Make GRUB the master bootloader by telling it to be installed in the MBR. Let the Windows bootloader worry about the Windows OSes.

according to this site, the Lucent LT modem drivers are initiated with 'modprobe lt_serial' so both lt_modem and lt_serial are loaded. do both of these kernel modules appear when you check using 'lsmod' ? the device initiated by lt_serial is /dev/tts/LT0 not /dev/ttyLT0 the way to do a quick troubleshoot is to run 'minicom' and send some basic AT commands to the modem - like, "AT<CR>" and "ATI4<CR>" where <CR> is the enter key. you'll have to tell minicom which device name to use to connect to your modem. try '/dev/ttyLT0' and '/dev/tts/LT0' before you try '/dev/modem'. additionally, when you are starting up pppd or wvdial, are you doing so logged in as an account belonging to the 'dialout' account group?

it would help to know what you've done so far, step-by-step. when you say "got the rpm" - what do you mean, exactly ?

Red Hat (RH) 8 or 9 provides RPMs for openssl, mysql, etc. Why are you compiling them when you can install the precompiled RPMs ? Are you confusing package installation with application compilation? How much disk space is available on your workstation? (do 'df' and 'free' and 'uname -a' and post the output, please)

do "ls -lL /dev/modem" or "ls -l /dev/ttyLT0" and post the output, please. Note by adding the 'L' in the first command, you dereference the symbolic link to show the (file)list ('ls') of the underlying device. The second command is equivalent to the first, so just pick one and run it.

I'm certain RH6 can ignore the ext3 partitions as long as you don't ask it to mount them... hang on - memory flash - RH6 will mount the ext3 filesystems as ext2 but won't (of course) update the fs journal. I think your best bet is to provide ext2 fs'es for RH6 otherwise FC1 is going to report fs errors. Now that I see your disk layout, I suspect the problem is the whole RH6 'world' does not live below the 4GB mark on your disk. 3GB for RH6 should be plenty, and try putting it immediately following your boot partition. Hint: what's 2^32 - 1 ? BTW, why such a gigantic boot partition? 30MB for one kernel or 120MB for four kernels ought to be plenty enough.

cibi3d: you're saying you can type something in the 'Run Command' textbox? and you can start up an app or a shell from there, right? oldspiceap: can you confirm the same symptom as cibi3d ? If you can type just fine in a KDE app or applet or textbox but not in a shell, then the problem is caused by a lack of pseudoterminals. One or all of the following questions may apply: Are you missing /dev/ptmx ? Are there never any entries in /dev/pts/ ? Do you not have the 'devs' package installed ? Have you missed/skipped running the 'makedevs' script ?

well, let's see... a google search on "irda usb linux" provides this Infrared-HOWTO document. It's the section on IrDA-USB dongles. According to the HOW-TO and the Linux USB Project page, if your dongle is made by SigmaTel or uses the SigmaTel chipset the answer to your question is: you can't get there from here. sorry. However, if the dongle is an Actisys or Extended System then MDK10 should already have the FIR-USB driver you need.

I'm thinking the placement of ks.cfg matters a great deal if isolinux is being used in one of its emulation modes. When isolinux emulates a floppy disk, all of the data must fit contiguously into a floppy-sized region of the CD. If your vendor's disc uses an emulation mode and then puts ks.cfg outside of the isolinux-emulated floppy disk, then there's no way for the booting kernel to 'see' the ks.cfg file. You'd know this is happening if the boot behavior is just like the disc not having a ks.cfg file at all.

wait.. do you mean you're only installing the kernel in /boot but you're intending to use an already set-up filesystem elsewhere on the disk? If you're using a journaled filesystem, I believe RH6.2 pre-dates many of the current journaled filesystem options. Any hints on the other vtys as you attempt the disk partitioning part of the install? The 1024 cyl "barrier" isn't so much a barrier as it is/was a limitation of using AT BIOS compatible CylHdsSec (CHS) addressing. The Cyl number used 10 bits, hence the 1024 "barrier".