On Fri, 5 Mar 2004, Michael Bushkov wrote:
Some time ago there was a discussion concerning in-process vs. IPC
nsswitch implementation. We agreed that we should develop an example of
IPC implementation and ask for a discussion. We are glad to present you
sample implementation of the IPC
On Wed, May 12, 2004 at 02:08:05PM +0100, Mike Bristow wrote:
+ Hi,
+
+ I am trying to access some ancient 5 1/4 floppies, with 256 byte
+ sectors. Leaving aside the interesting hardware problems, the
+ filesystem on these disks is (surprisingly enough) not supported on
+ -CURRENT. While
, 13.05.2004, 15:29, Pawel Jakub Dawidek :
On Wed, May 12, 2004 at 02:08:05PM +0100, Mike Bristow wrote:
+ Hi,
+
+ I am trying to access some ancient 5 1/4 floppies, with 256 byte
+ sectors. Leaving aside the interesting hardware problems, the
+ filesystem on these disks is (surprisingly
On Thu, May 13, 2004 at 03:58:02PM +0300, Alex Lyashkov wrote:
+ This sector size is valid and shouldn't be rejected.
+ This patch works for me:
+
+ http://people.freebsd.org/~pjd/patches/md.c.3.patch
+ in patch
+ +sc-nsect = (mdio-md_size * DEV_BSIZE) / sc-secsize;
+ why not
+ +
The situation:
Dell PowerEdge 1750, Dual 3.2 GHz, 1 GB RAM.
Sources compiled from CVS on 4 May 2004, RELENG_5_2 branch.
# uname -a
FreeBSD hr-stc-file2.smartrafficenter.net 5.2.1-RELEASE-p5 FreeBSD 5.2.1-RELEASE-p5
#0: Tue May 4 11:02:47 EDT 2004 [EMAIL
On Thu, May 13, 2004 at 01:16:59PM -0400, Kevin A. Pieckiel wrote:
One filesystem NFS mounted from another FBSD 4.9 box.
Samba 3.0.4 is installed and running (AD member server).
Samba is mapping home directories to the NFS-mounted files.
When accessing a home directory from a Windows
I'm posting to freebsd-hardware@ but this list seems to be a little dead.
:-( so the posting follows to freebsd-hackers@
Hi all,
I have a problem with Hewlett Packard scanner from subject. I tried to get
it working on trough FreeBSD 4.8REL , 4.9 REL , 4.9 STABLE and
now 4.10 PREREL cvsuped
I'm looking for a work around to this usb ethernet problem.
With FreeBSD-5.2.1-p5, device ehci added to the default GENERIC kernel,
the axe device works fine in USB 2.0 mode, when plugged in after boot
(AFTER ehci driver is loaded)B.
However, without ehci, uhci tries to attach the device
On Thu, May 13, 2004 at 05:19:39PM -0600, Shawn Webb wrote:
I can't tell exactly what's going on, but from that output, it seems as
though it's smbd's fault, not NFS's
How can I dive deeper? Or _CAN_ I dive deeper? Can I identify the
faulting instruction and determine why it's faulting? At
9 matches
Mail list logo