"Brandon D. Valentine" wrote:
>
> On Thu, 27 Sep 2001, Jordan Hubbard wrote:
>
> >Progress in these types of situations nearly always comes from people
> >with enough self-interest in the problem area to actually commit to
> >working on it. Rather than asking for people who have written an
> >a
"Brandon D. Valentine" wrote:
>
> On Fri, 28 Sep 2001, Thyer, Matthew wrote:
> >Combine that with the fact that FreeBSD has no automounter that is
> >compatible with the commercial UNIX systems and you'll see that
> >FreeBSD is missing out in some key markets (being a client in a
> >larger UNIX n
On 28-Sep-01 Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Mike Smith writes:
>: > > > I only found this out today when my Dell inspiron7500
>: > > > refused to boot past the ACPI message..
>: > > > Surprised me a bit as Mike has one of these.
>: > >
>: > > There's a well-documented and
On Thu, 27 Sep 2001, Jordan Hubbard wrote:
>Progress in these types of situations nearly always comes from people
>with enough self-interest in the problem area to actually commit to
>working on it. Rather than asking for people who have written an
>autofsd to step forward, why not instead start
In message <[EMAIL PROTECTED]>, Julian Elischer writes:
>This is a multi-part message in MIME format.
>--5937F02517145C712E28C299
>Content-Type: text/plain; charset=us-ascii
>Content-Transfer-Encoding: 7bit
>
>'du' keeps an array of files it has encountered that have > 1 link.
>Wheneve
Progress in these types of situations nearly always comes from people
with enough self-interest in the problem area to actually commit to
working on it. Rather than asking for people who have written an
autofsd to step forward, why not instead start working on this project
yourselves and ask for
On Fri, 28 Sep 2001, Brandon D. Valentine wrote:
>I have echoed these sentiments many times on this same mailing list. I
>am faced with the same problem. I admin a large, heterogenous
>NIS/NFS/autofs domain and integrating just one FreeBSD box into is so
>hacking it's embarassing.
s/hacking/ha
On Fri, 28 Sep 2001, Thyer, Matthew wrote:
>Now that is something I do care about and FreeBSD's possible poor
>NIS client performance is making it look very bad in a large UNIX
>network such as the one we run here.
>
>Combine that with the fact that FreeBSD has no automounter that is
>compatible
Stephen McKay wrote:
>
> On Monday, 24th September 2001, "Thyer, Matthew" wrote:
>
> > IMPORTANT: This email remains the property of the Australian Defence
> > Organisation and is subject to the jurisdiction of section 70 of the
> > CRIMES ACT 1914. If you have received this email in error, you
In message <[EMAIL PROTECTED]> Mike Smith writes:
: > > > I only found this out today when my Dell inspiron7500
: > > > refused to boot past the ACPI message..
: > > > Surprised me a bit as Mike has one of these.
: > >
: > > There's a well-documented and necessary hack to work on these
: > > ma
In message <[EMAIL PROTECTED]> Alfred Perlstein writes:
: Can someone please share with us the magic to disable acpi and add
: it to src/UPDATING, my sound fell victim to acpi and i think I just
: lost my mouse to it. Now I have a lapbrick that consumes less
: power...
I'll have to add it to UPD
Are you using -DNOCLEAN?
Luigi Rizzo wrote:
> Hi,
> not sure if this is a local problem or a more general one.
> I am trying to build picobsd image using -CURRENT sources on
> a 4.3 box, a process which i successfully managed to complete
> multiple times over the past few weeks with the picobsd s
Hi,
not sure if this is a local problem or a more general one.
I am trying to build picobsd image using -CURRENT sources on
a 4.3 box, a process which i successfully managed to complete
multiple times over the past few weeks with the picobsd script.
With a freshly downloaded source tree, today I
To all our fans!!
Welsh Fantasy Football has paid your entrance fee to the
WELSH FANTASY FOOTBALL GAME 2001
Go to www.welshfantasyfootball.com
you have to be in it to WIN it!!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Wilko Bulte wrote:
>
> On Thu, Sep 27, 2001 at 02:00:26PM -0700, Julian Elischer wrote:
> > 'du' keeps an array of files it has encountered that have > 1 link.
> > Whenever it encounters another, it checks to see if it's one it has
> > already seen
> > and thus can avoid counting its space twice.
On Thu, Sep 27, 2001 at 02:00:26PM -0700, Julian Elischer wrote:
> 'du' keeps an array of files it has encountered that have > 1 link.
> Whenever it encounters another, it checks to see if it's one it has
> already seen
> and thus can avoid counting its space twice..
>
> This is ok for small file
'du' keeps an array of files it has encountered that have > 1 link.
Whenever it encounters another, it checks to see if it's one it has
already seen
and thus can avoid counting its space twice..
This is ok for small filesystems, however VICOR maintains
500GB filesystems on which much of the data
On 27-Sep-01 SXren Schmidt wrote:
> It seems John Baldwin wrote:
>> > I found that I am no longer able to boot -current kernel on my machine.
>> > The
>> > system panices right after initialising ed0 driver:
>> >
>> > [...]
>> > ed0: port 0xe800-0xe81f irq 9 at
>> > device
>> > 9.0 on pci0
>> >
It seems John Baldwin wrote:
> > I found that I am no longer able to boot -current kernel on my machine. The
> > system panices right after initialising ed0 driver:
> >
> > [...]
> > ed0: port 0xe800-0xe81f irq 9 at device
> > 9.0 on pci0
> > panic: inthand_add: can't initialize ICU
> >
> > Att
On 27-Sep-01 Maxim Sobolev wrote:
> Hi,
>
> I found that I am no longer able to boot -current kernel on my machine. The
> system panices right after initialising ed0 driver:
>
> [...]
> ed0: port 0xe800-0xe81f irq 9 at device
> 9.0 on pci0
> panic: inthand_add: can't initialize ICU
>
> Attach
On Thu, 27 Sep 2001, Maxim Sobolev wrote:
> I found that I am no longer able to boot -current kernel on my machine. The
> system panices right after initialising ed0 driver:
>
> [...]
> ed0: port 0xe800-0xe81f irq 9 at device 9.0 on
>pci0
> panic: inthand_add: can't initialize ICU
>
> Attached
I stumbled across this just now. I got the error after usb detection, so
I switched off everything usb in my bios, and amazingly it boots again.
Strange but true :)
On 27 Sep, Maxim Sobolev wrote:
> Hi,
>
> I found that I am no longer able to boot -current kernel on my
> machine. The system pani
Hi,
I found that I am no longer able to boot -current kernel on my machine. The
system panices right after initialising ed0 driver:
[...]
ed0: port 0xe800-0xe81f irq 9 at device 9.0 on
pci0
panic: inthand_add: can't initialize ICU
Attached please find verbose kernel bootup messages obtained f
On Thu, Sep 27, 2001 at 12:57:26AM -0700, Julian Elischer wrote:
>I'd try asking for a service name of "ISP"
THANK YOU!!! :))
/john
Live Free OR Die
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
John Indra wrote:
>
> On Tue, Sep 25, 2001 at 12:42:47PM +0100, Brian Somers wrote:
>
> >You could try running ``tcpdump -i xl0 -e -l not ip'' to see if any
> >of your traffic is being replied to (and to ensure it goes out with
> >the dodgy header numbers).
>
> I have run tcpdump and attached i
25 matches
Mail list logo
