search for: mahabharata

Today I install FreeBSD release 4.8 on a machine for the first time. This is on a new machine so it could easily have as yet undetected hardware faults. I observe the 'dmesg' gives startup information not only for the latest boot but also information generated in a number of previous boots. I've not seen this with earlier FreeBSD realeases including 4.7. Is it normal for FreeBSD

...iber could have confirmed this mail, which never should have been send in the first friggin' place. -- "Well," Brahma said, "even after ten thousand explanations, a fool is no wiser, but an intelligent man requires only two thousand five hundred." - The Mahabharata -------------- next part -------------- An embedded message was scrubbed... From: Gerald Combs <gerald+confirm+1061610246.19853.1dcb62@zing.org> Subject: Confirmation accepted Date: Fri, 22 Aug 2003 22:47:25 -0500 (CDT) Size: 2839 Url: http://lists.freebsd.org/pipermail/freebsd-stable/attachm...

Hi. I have a question related to freebsd opie implementation. I am running 4.9-RELEASE and I've tried to setup opie. *** 1 *** opiepasswd/opiekey I've added user using `opiepasswd -c "ssa"` mx2# opiepasswd -c "ssa" Adding ssa: Only use this method from the console; NEVER from remote. If you are using telnet, xterm, or a dial-in, type ^C now or exit with

Hello all, I have problems with enabling support for SMBus on STABLE. My motherboard is ICH3 (82801CA). As suggested in LINT I added 3 lines to my kernel config: device smbus device ichsmb device smb But after compiling, installing and rebooting /dev/smb[01] are not available and no changes in kernel startup messages either. So I

so i just found that one of my hosts is GENERATING these probe pairs, maybe every minute or two (note the sequence numbers): seq my host victim(s) --- ---------------- --------------- 24) 192.168.0.2:1121 <--> 216.52.3.2:2703 25) 192.168.0.2:1122 <--> 216.52.3.4:2703 39) 192.168.0.2:1124 <-->

I'm working with a FreeBSD user -- a teacher -- who's running KDE on a system on which she neither has nor wants root privileges. She wants to be able to mount and unmount floppies and ZIP cartridges from within KDE, using the standard KwikDisk utility (which, by the way, generates mount and unmount command that don't conform to FreeBSD syntax; however, it appears possible to fix this

I'm not sure where else to ask about this, so please excuse me if this is the wrong forum. In trying to remove a 'nodump' flag on a directory with the 'chflags' command I have noticed that the 'nonodump' flag does not function. I see an open PR for the problem: o [2003/01/09] i386/46912 johan chflags nonodump fails I was wondering when this might be dealt with? Else is