On 25-Dec-01 Eric Melville wrote:
>> However, perhaps sysinstall should tell the user that if they have a USB
>> mouse, they need do nothing, insetad of think 'Uhh, I don't recognise any of
>> these, lets try this one' and getting it wrong.
>
> Before this menu is presented, sysinstall asks
On 24-Dec-01 William Ward wrote:
> Is /dev/ums0 ommitted from sysinstall for any particular reason? This patch
> adds /dev/ums0 to sysinstall::Configure->Mouse->Port.
Yes, usbd already runs moused for you. (Look at usbd.conf), so putting this in
results in 2 moused's trying to work with /dev/u
On Sat, Dec 29, 2001 at 04:03:40PM +1030, Greg Lehey wrote:
> On Saturday, 29 December 2001 at 6:21:29 +0100, Bernd Walter wrote:
> > On Sat, Dec 29, 2001 at 10:09:11AM +1030, Greg Lehey wrote:
> >> This has nothing to do with Vinum. The errors are at the device
> >> driver level, and they appea
hi, there!
On Fri, Dec 28, 2001 at 09:33:08PM +0100, Jan Stocker wrote:
> What is the state of smbfs for current at present?
Boris Popov has updated kernel-side smbfs for KSE.
Sheldon Hearn imported smbfs 1.4.3 userland (to both HEAD and RELENG_4).
smbfs should work out of box.
we still do no
From: Jim Bloom <[EMAIL PROTECTED]>
Subject: PC Card hang
Date: Tue, 27 Nov 2001 19:26:04 -0500
: My laptop is hanging when I boot it after this commit. The system hangs
: when pccardd is started. If no cards are installed, the boot proceeds
: without a problem and the system hangs when the fir
On Saturday, 29 December 2001 at 6:21:29 +0100, Bernd Walter wrote:
> On Sat, Dec 29, 2001 at 10:09:11AM +1030, Greg Lehey wrote:
>> This has nothing to do with Vinum. The errors are at the device
>> driver level, and they appear to relate only to the compact flash
>> adaptor. Does it work when
On Sat, Dec 29, 2001 at 10:09:11AM +1030, Greg Lehey wrote:
> On Friday, 28 December 2001 at 14:48:54 -0600, Jim Bryant wrote:
> > I know this is probably a minor issue, as it is only an annoyance, and
> > doesn't impact operation or performance, but still..
> >
> > Ever since I concatenated some
On Fri, Dec 28, 2001 at 12:30:23PM -0800, Doug White wrote:
> On Fri, 28 Dec 2001, Bernd Walter wrote:
>
> > On a -current from 26th december:
> > [...]
> > ata1 at port 0x250-0x257,0x25e irq 11 slot 1 on pccard1
> > ad2: 7MB [245/2/32] at ata1-master BIOSPIO
> > ticso@cicely30# ls -al /dev/ad2*
In article <[EMAIL PROTECTED]>
Josef Karthauser <[EMAIL PROTECTED]> wrote:
> joe 2001/12/28 12:50:13 PST
>
> Modified files:
>bin/ls Makefile ls.1 ls.c ls.h print.c util.c
> Log:
> Add a new flag, -h which when combined with the -l option causes
> file sizes to be d
[replies sent directly to me may timeout and bounce, since I'm not
online as often as I should be, but I'll check the list archives]
I wrote a while back to freebsd-hackers:
> Is it safe (relatively speaking) to use the null and the union
> filesystems?
Well, so far I have had no serious probl
On Friday, 28 December 2001 at 14:48:54 -0600, Jim Bryant wrote:
> I know this is probably a minor issue, as it is only an annoyance, and
> doesn't impact operation or performance, but still..
>
> Ever since I concatenated some old drives to make a more reasonable capacity
> out of them, I have be
I know this is probably a minor issue, as it is only an annoyance, and doesn't impact
operation or performance, but still..
Ever since I concatenated some old drives to make a more reasonable capacity out of
them, I have been noticing the following
whenever vinum is loaded at startup [Note: Th
What is the state of smbfs for current at present?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Fri, 28 Dec 2001, Bernd Walter wrote:
> On a -current from 26th december:
> [...]
> ata1 at port 0x250-0x257,0x25e irq 11 slot 1 on pccard1
> ad2: 7MB [245/2/32] at ata1-master BIOSPIO
> ticso@cicely30# ls -al /dev/ad2*
> crw-r- 1 root operator 116, 0x00010012 Dec 28 15:29 /dev/ad2
Ar
Hi
My userland and kernel were rebuilt after running cvsup on Christmas day.
Right after that, files created on /tmp which is swap-backed get corrupted
easily.
I was trying to build mozilla and everytime I untarred the source into /tmp,
I would get about 10 random files corrupted. Each of these
The s1 after da0s1 is similar for all disc devices under bsd. It means
the first slice (similar to partition for Wind**s users).
But this is something out of topic here... move to FreeBSD-question or
take a private talk with me...
Jan
On Fri, 2001-12-28 at 17:28, Joe Halpin wrote:
> Jan Stocke
Sigh. Turns out the "unwind" cleanup in ufs_mkdir() and ufs_makeinode()
has changed, but the MAC code was using the old unwinding rather than the
new 'bad' label. The EA code had an error case I forgot about, and so I
bumped into the bad unwinding code, causing the panic. Now fixed in the
trust
Jan Stocker wrote:
>
> Looks quite fine for me...
>
> looks like your cam was connected for about 6 mins...
>
> what does a
>
> $ mount -t msdos /dev/da0s1 /mnt
>
> say?
That works fine. I guess I'm trying to mount the wrong device file.
Sorry, I'm pretty new to usb and haven't caught on
On a -current from 26th december:
[...]
ata1 at port 0x250-0x257,0x25e irq 11 slot 1 on pccard1
ad2: 7MB [245/2/32] at ata1-master BIOSPIO
ticso@cicely30# ls -al /dev/ad2*
crw-r- 1 root operator 116, 0x00010012 Dec 28 15:29 /dev/ad2
ticso@cicely30# fdisk ad2
*** Working on device /dev/
Recently got this:
./account missinmg (directory noto created: Deviced not configured)e
= 040700, inum = 6, fs = /var
panic: ffs_valloc: dup alloc
Debugger("panic")
Stopped at Debugger+0x44: pushl %ebx
db> trace
Debugger(c03a3b9b) at Debugger+0x44
panic(c03bb9e1,c03bb9c0,41c0,6,c22ab0d4
Maksim Yevmenkin <[EMAIL PROTECTED]> wrote:
> it looks like if_ar and if_sr modules will not compile
> unless you have enabled NETGRAPH. patches are simple and
> attached.
Sorry for the breakage, yes.
> #include
> #include
> #else /* NETGRAPH */
> +#include
> +#include
> +#include
> +#i
Looks quite fine for me...
looks like your cam was connected for about 6 mins...
what does a
$ mount -t msdos /dev/da0s1 /mnt
say?
Maybe you should take a look at the partition table with
$ fdisk da0
if it tells you something like
fdisk: invalid fdisk partition table found
Media sector
22 matches
Mail list logo
