-On [19991201 20:01], Russell Cattelan ([EMAIL PROTECTED]) wrote:
>Dag-Erling Smorgrav wrote:
>> I have a Soundblaster 128 PCI (labeled "MODEL:CT4810") which I can't
>> get to work with newpcm.
>What mother board are you using?
>There have been some report
I recently noticed that ^v (the scroll down a page command in ee) must be
entered twice to scroll down once (i.e. if you hit ^v once it won't do
anything, you must hit it again) on a 4.0-CURRENT system. As far as I can
recall, this has been happening for as long as I've been tracking -CURRENT
(~1
I've updated to the latest -current, and things have gone awry. At boot,
the console freezes
at the end of the dmesg. The startup process continues, tho, and I can
telnet into the box. Then madness ensues. The contents of some files I
create disappears, top freezes after listing the process
On Tue, 30 Nov 1999, Brian Fundakowski Feldman wrote:
> kind of thing I'd rather have. I like the precomputed one (add all
> argv[] strlen's and malloc that) better, anyway.
..and as soon as warner reviews my revised patch, it will be committed :-)
Kris
To Unsubscribe: send mail to [EMAIL P
Has anyone been able to do a make release recently? It seems
to break when trying to build jade from the ports, which I
think is due to the new compiler import. I saw that there
are recent snapshots on current.freebsd.org, which is confusing
because I can't get jade to build:
../include/StringO
On Wed, 1 Dec 1999, Matthew D. Fuller wrote:
> On Wed, Dec 01, 1999 at 04:36:12PM -0500, a little birdie told me
> that James Howard remarked
> > On Wed, 1 Dec 1999, Matthew D. Fuller wrote:
> > >
> > > [15:25:53] mortis:~
> > > (ttyp9):{838}% ll -i `which crypt` `which enigma`
> > > 23155 -r-x
On Wed, Dec 01, 1999 at 04:36:12PM -0500, James Howard wrote:
> > Renaming?
> > [15:25:53] mortis:~
> > (ttyp9):{838}% ll -i `which crypt` `which enigma`
> > 23155 -r-xr-xr-x 2 root wheel 4980 Oct 29 13:47 /usr/bin/crypt*
> > 23155 -r-xr-xr-x 2 root wheel 4980 Oct 29 13:47 /usr/bin/eni
I am getting the folowing error messages for each mounted directory every time
rpc.umntall is being run:
Bad MNT RPC: RPC: Remote system error
The following is fragment of my /etc/fstab file:
# DeviceMountpoint FStype Options DumpPass#
kan:/home/ak03 /
> : Hey, we're getting somewhere. It works, in that it stops the panic.
> : I get the "ed0: unloaded" message, and the machine doesn't panic, but
> : there are still some problems. It seems that device_delete_child
> : is failing (I forgot to print the return code, but it is not zero),
> : and r
On Wednesday, 1 December 1999 at 16:40:33 -0600, tonymb wrote:
> HELLO MY NAME IS TONY. I HAVE BEEN DOING RESEARCH ON FREEBSD. I'M PLANNING TO SETUP
>A SYSTEM WITH THIS OS. I WOULD THANK YOU FOR PLACING ME ON YOUR MAILING LIST TO
>BENEFIT FROM THE EXPERIENCE OTHERS AND EXPERTISE TO MAKE MY TR
On Wed, Dec 01, 1999, tonymb wrote:
> HELLO MY NAME IS TONY. I HAVE BEEN DOING RESEARCH ON FREEBSD. I'M PLANNING TO SETUP
>A SYSTEM WITH THIS OS. I WOULD THANK YOU FOR PLACING ME ON YOUR MAILING LIST TO
>BENEFIT FROM THE EXPERIENCE OTHERS AND EXPERTISE TO MAKE MY TRANSITION SMOOTH.PLEASE
>USE
HELLO MY NAME IS TONY. I
HAVE BEEN DOING RESEARCH ON FREEBSD. I'M PLANNING TO SETUP A SYSTEM WITH THIS
OS. I WOULD THANK YOU FOR PLACING ME ON YOUR MAILING LIST TO BENEFIT FROM THE
EXPERIENCE OTHERS AND EXPERTISE TO MAKE MY TRANSITION SMOOTH.PLEASE USE
THIS E-MAIL ADDRESS [EMAIL PROTECTED]
[ I've cc'd FreeBSD-doc on this, in case there's someone there who's solved
the problem you're having ]
On Sun, Nov 28, 1999 at 05:38:57PM +0100, F. Heinrichmeyer wrote:
> i tried to make me a new handbook, so i needed jade.
>
> But the newest C++ fashion (g++ under current) has changed to fas
Nevermind, I had nosuid in fstab, totally forgot
about it.
- Original Message -
From:
David W.
Chapman Jr.
To: [EMAIL PROTECTED]
Sent: Wednesday, December 01, 1999 3:54
PM
Subject: su and traceroute
I just cvsuped to -current right after bind-8.2.2
was mer
On Wed, Dec 01, 1999 at 04:36:12PM -0500, a little birdie told me
that James Howard remarked
> On Wed, 1 Dec 1999, Matthew D. Fuller wrote:
> >
> > [15:25:53] mortis:~
> > (ttyp9):{838}% ll -i `which crypt` `which enigma`
> > 23155 -r-xr-xr-x 2 root wheel 4980 Oct 29 13:47 /usr/bin/crypt*
> > 2
I just cvsuped to -current right after bind-8.2.2
was merged into the source tree. I noticed two problems. Su won't
work and traceroute gives me the following
traceroute: icmp socket: Operation not
permitted
here are its permissions
-r-sr-xr-x 1 root wheel 12076
Dec 1 14:15 /usr/
On Wed, 1 Dec 1999, Matthew D. Fuller wrote:
> On Wed, Dec 01, 1999 at 04:09:11PM -0500, a little birdie told me
> that Bakul Shah remarked
> >
> > Enigma is just a format converter at this point and should be
> > left around (after renaming it crypt -- which is how it is
> > known on all Unix v
On Wed, Dec 01, 1999 at 03:26:34PM -0600, Matthew D. Fuller wrote:
> On Wed, Dec 01, 1999 at 04:09:11PM -0500, a little birdie told me
> that Bakul Shah remarked
> > Enigma is just a format converter at this point and should be
> > left around (after renaming it crypt -- which is how it is
On Wed, Dec 01, 1999 at 04:09:11PM -0500, a little birdie told me
that Bakul Shah remarked
>
> Enigma is just a format converter at this point and should be
> left around (after renaming it crypt -- which is how it is
> known on all Unix versions older than 10 years). Some of us
Renaming?
[15:2
On Tue, Nov 30, 1999 at 10:34:56AM -0700, Davec wrote:
>
> Yup tried it, didn't work. Got the same error messages (refer to the [LONG]
> email I sent a few days past. Thanks for the suggestion though.
>
I missed that one apparently. Send it to me in private and I'll see what I
can do.
> Dave
> With the FreeBSD 4.0 code freeze fast approaching, are there any
> compelling reasons to keep enigma (src/usr.bin/enigma) in the
> source tree?
How dare you be so anti-bloat, living so close to Redmond?:-)
[But otherwise a nice place, Seattle. I used to live there]
Enigma is just a format co
>From: Steve Kargl <[EMAIL PROTECTED]>
>Date: Wed, 1 Dec 1999 12:20:19 -0800 (PST)
>With the FreeBSD 4.0 code freeze fast approaching, are there any
>compelling reasons to keep enigma (src/usr.bin/enigma) in the
>source tree? Yes, I know it is a *small* utility, but
>1. it provides rather weak
[Donning asbestos underwear]
With the FreeBSD 4.0 code freeze fast approaching, are there any
compelling reasons to keep enigma (src/usr.bin/enigma) in the
source tree? Yes, I know it is a *small* utility, but
1. it provides rather weak encryption,
2. the crypto-distribution is available with s
On Wed, Dec 01, 1999 at 12:02:54PM -0800, Mike Smith wrote:
> > On Wed, Dec 01, 1999 at 09:05:38AM -0700, Warner Losh wrote:
> > > In message <[EMAIL PROTECTED]> Mike Smith writes:
> > > : The only "right" solution is for us to mandate that people down cards
> > > : before ejecting them.
> ...
>
On Tue, 30 Nov 1999, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Christopher Masto writes:
> : Hey, we're getting somewhere. It works, in that it stops the panic.
> : I get the "ed0: unloaded" message, and the machine doesn't panic, but
> : there are still some problems. It seems that d
On Tue, 30 Nov 1999, Mike Smith wrote:
> > Hmmm... That's something... How do you know that the delete_child is
> > failing? An if printing that it failed or conjecture based on the
> > insertion results?
>
> You should definitely check the delete result, yes.
>
> Also, are you calling bus_g
> On Wed, Dec 01, 1999 at 09:05:38AM -0700, Warner Losh wrote:
> > In message <[EMAIL PROTECTED]> Mike Smith writes:
> > : The only "right" solution is for us to mandate that people down cards
> > : before ejecting them.
...
> I would like to see that something along the lines of a method to shut
On Wed, 1 Dec 1999, David O'Brien wrote:
> On Wed, Dec 01, 1999 at 07:49:19AM -0500, Chris D. Faulhaber wrote:
> > That's kinda hefty for a small port :) I have it marked as broken for
> > -current until the lib is in compat3x.
>
> Why? Many of us still have libc*.so.3 from when that was the v
--- Blind-Carbon-Copy
To: Christopher Masto <[EMAIL PROTECTED]>
Subject: Re: PCCARD eject freeze (was Re: your mail)
Cc: [EMAIL PROTECTED]
In-reply-to: Your message of "Wed, 01 Dec 1999 12:36:29 EST."
<[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
On Wed, Dec 01, 1999 at 09:05:38AM -0700, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Mike Smith writes:
> : The only "right" solution is for us to mandate that people down cards
> : before ejecting them. The physical design of pccards basically gives us
> : no other option. No matter
Dag-Erling Smorgrav wrote:
> I have a Soundblaster 128 PCI (labeled "MODEL:CT4810") which I can't
> get to work with newpcm. It shows up like this in dmesg:
>
> pci0: unknown card (vendor=0x3274, dev=0x1371) at 10.0 irq 5
>
> and in 'pciconf -l':
>
> none0@pci0:10:0:class=0x040100 card=0x
I've made one more round of fixes to the if_dc driver, which I hope
will be the last before I import it into -current this coming weekend
so that I can get it in before the feature freeze. The changes are:
- Modified the behavior of dc_mii_tick() so that the DC_REDUCED_MII_POLL
flag works for n
On Wed, Dec 01, 1999 at 07:49:19AM -0500, Chris D. Faulhaber wrote:
> That's kinda hefty for a small port :) I have it marked as broken for
> -current until the lib is in compat3x.
Why? Many of us still have libc*.so.3 from when that was the version in
-CURRENT until a month ago.
--
-- David
I have a Soundblaster 128 PCI (labeled "MODEL:CT4810") which I can't
get to work with newpcm. It shows up like this in dmesg:
pci0: unknown card (vendor=0x3274, dev=0x1371) at 10.0 irq 5
and in 'pciconf -l':
none0@pci0:10:0:class=0x040100 card=0x13711274 chip=0x13713274 rev=0x06
hdr=0x
In message <[EMAIL PROTECTED]> Mike Smith writes:
: The only "right" solution is for us to mandate that people down cards
: before ejecting them. The physical design of pccards basically gives us
: no other option. No matter how hard we try to get it "right" for
: spontaneous removal, we can'
Você ainda não faz parte da maior vitrine de profissionais do Brasil?
Deixe www.curriculum.com.br trabalhar por você!
Cadastre-se gratuitamente e faça como inúmeros outros profissionais.
Independente se está ou não empregado, coloque-se a disposição do mercado de trabalho.
Este é o futuro. Dei
Hi,
Doug Rabson wrote:
> > Please see
> > http://www.jp.freebsd.org/cgi/cvsweb.cgi/ACPI/util/acpiconf?cvsroot=freebsd-jp
>
> This sounds very promising. I will check out the code soon and try to give
> feedback. Creating the ACPI namespace is a necessary first step before its
> possible to do fu
On 1 Dec, F. Heinrichmeyer wrote:
> On a freebsd-current box there is a second scsi-cdrom (a cd-writer
> working fine with cdrecord). I remade the devices with MAKEDEV,
> everything is new, but there is nothing new like cd1c ... Looking at the
> source the minor number of cd0c has to be increased
I have been contemplating replacing our
/usr/src/share/termcap/termcap.src with the latest termcap file
maintained by Eric Raymond. His latest version seems 10.2.7 dated 10
March 1999.
While our termcap.src has been maintained well by ache and other
committers, Eric's version appears more compre
Bruce Evans <[EMAIL PROTECTED]> writes:
> If the caller has passed a double, then the stack alignment can be determined
> at compile time and the current subl-type adjustment can be used.
Doubles are not aligned when passed as parameters and passing a double
doesn't guarantee that there are loc
> The stack must be aligned before the return address is pushed:
>
> The following C fragment
> f(1);
> f(2);
>
> Translates to
>
> addl $-12,%esp
> pushl $1
> call f
> addl $16,%esp
> addl $-12,%esp
> pushl $2
> call f
>
On Tue, 30 Nov 1999, David O'Brien wrote:
> > > that it requires libc_r.so.3; unfortunately, compat3x does not contain
> > > this lib. Any chance of having it added to compat3x?
> >
> > Yes. The PR is assigned to me, but David already has it on his TODO
> > list. Compat3x is updated late to mak
Ville-Pertti Keinonen wrote:
> Perhaps crt1.c should call main like this (I can't immediately figure
> out whether the stack pointer should be correctly aligned before the
> return address is pushed or after the previous stack frame is pushed,
> this is assuming the former, s/subl/addl/ would cha
> It would be better for GCC to force alignment only within those
> procedures that need it rather then force all procedures to guarentee
> alignment. Then we could have the best of both worlds.
Determining whether it is necessary is non-trivial, you would have to
go through all lo
For those who are keeping track of this, just a quick update. The 'amr'
driver for AMI MegaRAID controllers in -current and available for -stable
at http://www.freebsd.org/~msmith/RAID/ami has now been tested with the
following AMI MegaRAID controllers:
Enterprise 1500 aka 467 (new)
Ente
>
> With freeze I meant, freeze. Rock solid. Nothing to be done. Stepping
> through the code the laptop freezes in the second putb in pcic_disable.
> As in stepping the assembler to that outb does never return the prompt.
Actually, I don't think so. I'm not 100% sure, but I think that you end
> In message <[EMAIL PROTECTED]> Christopher Masto writes:
> : On Tue, Nov 30, 1999 at 04:52:33PM -0700, Warner Losh wrote:
> : > It would help me if you could send me your patches...
> :
> : Well, here's all I've got. It's basically just a sloppy version of
> : what you suggested.
>
> OK. Thi
47 matches
Mail list logo
