similar to: phy nics when will they be supported in 4.8

Hello, Is this possible to install drivers for this hardware under FreeBSD, and begginig from which version? Motherboard Epox 8RDA3+ (NForce2) none0@pci0:0:1: class=0x050000 card=0x10001695 chip=0x01eb10de rev=0xc1 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'nForce2 Memory Controller 1' class = memory subclass = RAM none1@pci0:0:2: class=0x050000

I'm building another server and must decide on scsi card the tekram looks very promising to me but need to know if it will be supported or not in 4.8 or 5.1. server will be used of mysql / apache. any info or suggestions as to scsi cards would be great. thx in advance. Sign, Eriq

Can anyone with Heimdal KrbV verify this? -------------- next part -------------- An embedded message was scrubbed... From: Dag-Erling Smorgrav <des at ofug.org> Subject: Kerberos buglet in OpenSSH-3.3p1 Date: 25 Jun 2002 14:52:10 +0200 Size: 1291 Url: http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20020626/347e123e/attachment.mht

While burning in a new desktop Epox KT-880 workstation, I'm running on my old K6-III at 360MHz. Before new X updates (put everything in today, kernel, elfutils, ntpd - Selinux issues? - xorg, ...) with my PCI ATI 7000 (Radeon) on a 19" Samsung 950b @ 1024x768 (one of 5 different resolutions I commonly use), I could scroll smoothly at reasonable rates. With the new stuff I get severe

when will they add the driver to this nic card? I have an nforce2 mb by epox that has this nic and I can't use it at all :(

http://bugzilla.mindrot.org/show_bug.cgi?id=315 Summary: add miissing includes and defines for FREEBSD Product: Portable OpenSSH Version: -current Platform: Other OS/Version: FreeBSD Status: NEW Severity: normal Priority: P2 Component: Build system AssignedTo: openssh-unix-dev at mindrot.org

Hi. It would be of utmost utility if there were a way to cause the sshd "banner" configuration setting to only print the banner in certain circumstances. What I'm actually after is avoiding printing out the banner for non-interactive sessions, so that if I run "ssh somehost ls" I don't get the login banner, but if I just type "ssh somehost" I do (at

A STABLE (not updated since 12/13/02) system shows very strange behavior for devices with a minor mode greater than 256. tcpdump does not work reliably and ls is, uh, "strange", using hex for the minor mode. crw------- 1 root wheel 23, 252 Apr 11 14:29 bpf252 crw------- 1 root wheel 23, 253 Apr 11 14:29 bpf253 crw------- 1 root wheel 23, 254 Apr 11 14:29 bpf254

I am having problem with getting the src from the cvs server for a specific date I read the the man page and it said the date format is : "date=[cc]yy.mm.dd.hh.mm.ss This specifies a date that should be used to select the revi- sions that are checked out from the CVS repository. The client will receive the revisions that were in effect at the specified date and time. At present, the date

HELO, My old CRT is a bit broken so I decided to buy new screen. I d like to get an LCD monitor. I also use FreeBSD , X ver.4.2 server and GNOME 2.2. And now my question: Do I have to setup my X for that monitor, or maybe just change name, vendor, refresh modes in my XF86Config ? I am not going to use DVI.... thanks for help MArek

hail, I have an old AthlonXP 1700+ running 7-STABLE: FreeBSD xxx 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #1: Thu Nov 13 23:54:59 BRT 2008 root@xxx:/usr/obj/usr/src/sys/xxx i386 where I have two 750GB Seagate SATA Disks. They are divided as two slices, around the first 120GB are gathered in gmirror, and what left is in gstripe. so that's whats going on. if the machine locks, and fsck comes to

Hi all. I just upgraded my server from 4.7-Stable to 5.0-Release by a full install. Now I hit a problem with the date.. the time goes much faster than normal.. maybe twice as normal... this morning I found the following kernel log in /var/log/messages May 26 17:23:58 jupiter kernel: Timecounter "i8254" frequency 1193182 Hz May 26 17:23:58 jupiter kernel: Timecounter "TSC"

I have a Lite-On 24102B burner on an Epox 7KXA (VIA 686A southbridge) together with a few SCSI disks. I recently upgraded from FreeBSD 4.5 to 4.7 then almost immediately to 4.8. I've had trouble with the burner since. With FreeBSD 4.5, I used "sysctl hw.atamodes=---,---,dma,---" to set the burner to DMA. Everything then worked fine. As far as I know it was using UDMA33.

Hi all! I need your help. My server doesn't respond any more. Everything crashed. How can I find out if this is a bug or it is simply overloaded? I don't have much running, just KDE with about 10 programs on each of the 16 desktops, and a few background processes. This seems much, but I often have much more stuff running, and it is not even slow. It does respond when I ping it, but

Hello all, The long-mooted PAM merge from FreeBSD is starting _now_. This replaces the PAM password auth kludge that we have used until now with a discrete challenge-response module. This module is invoked via keyboard-interactive for protocol 2 or TIS auth for protocol 1. Warning: this is a large change and will probably break things. It has only been tested with basic password auth modules and

[bcc: to re@] Considering the amount of changes between 4.x and 5.x, and the performance issues of the latter, I think I can safely predict that RELENG_4 will be around for a long time after the RELENG_5 branch. While I understand that some will resist making RELENG_4 any more useful than it currently is (to encourage users to move to 5.x), I think there is one issue that should be addressed: the

Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: This is a digitally signed message part. Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20080617/73afe727/attachment.pgp

We have been having a problem with sshd on our shell server. This has been happening since March 4, 2003 or before IIRC. Initially I thought the next OS upgrade, to 4.8 would fix this. I am accustomed to haveing little things go away in a month or two. I think we jumped to 4.7-STABLE on Feb 28, 2003. Some exploit fix wasn't being MFSd to RELENG_4_7 fast enough for my nerves (cvsd?). It

Below is a new PAM kbd-int diff based on FreeBSD's code. This code makes PAM kbd-int work with privilege separation. Contrary to what I have previously stated - it *does* handle multiple prompts. What it does not handle is multiple passes through the PAM conversation function, which would be required for expired password changing. I would really appreciate some additional eyes over the

Check out http://nondot.org/sabre/LLVMNotes -Chris http://nondot.org/sabre http://llvm.org On Jul 27, 2007, at 12:00 PM, Sarah Thompson <thompson at email.arc.nasa.gov > wrote: > Hi folks, > > Assuming that I'm writing a pass and that for bizarre reasons I need > to > programmatically do the equivalent of a C/C++ sizeof on a Value (or a > Type, it doesn't