In <[EMAIL PROTECTED]>, Jean-Marc Zucconi wrote:
> > Jean-Marc Zucconi writes:
>
> > Try this in -current
> > $ cat some_file | head
>
> > I have to use ^C to regain control.
>
> ... and reverting to rev. 1.22 of eval.c fixes the problem.
Steve Price fixed my 1.23 mistake in 1.24.
Mar
For the last week and a half or so I've been trying to track this down
assuming it was a configuration error on my part or a problem with my
ISP's DHCP configuration. After switching from a DEC 20141 chipset card
to a 3com 3c905, I found I was still having problems although the error
message had
On Sun, 7 Nov 1999, Jeroen Ruigrok/Asmodai wrote:
> libggi has more support for FreeBSD than svgalib has and it also seems
> to be preferred over svgalib due to security hassles and all that.
>
> So you might want to try that route.
I saw where libvgl is now new and improved, and is called "lib
It seems Donn Miller wrote:
> On Sun, 7 Nov 1999, Jeroen Ruigrok/Asmodai wrote:
>
> > libggi has more support for FreeBSD than svgalib has and it also seems
> > to be preferred over svgalib due to security hassles and all that.
> >
> > So you might want to try that route.
>
> I saw where libvgl
On Mon, 8 Nov 1999, Kazutaka YOKOTA wrote:
>
> >Today I noticed accidentally that either libvgl is broken, or the demo
> >program does something wrong - the mouse cursor doesn't move.
>
> Oops, sos and I have developed a new version of libsvgl which can
> handle VESA modes in addition to the st
It seems Andrzej Bialecki wrote:
> >
> > Oops, sos and I have developed a new version of libsvgl which can
> > handle VESA modes in addition to the standard VGA graphics modes.
> > But I haven't committed it to the source tree yet (yes, I should have
> > done so weeks ago ;-(
> >
> > Anyway, if
On Sun, 7 Nov 1999, John Hay wrote:
> Ok, with these patches doscmd is working for me again. I can boot dos and
> run the topspeed C compiler like I used to a few months ago.
>
> If nobody has any complaints I'll commit it. I'm just not 100% sure about
> the patch to doscmd.c and would like if s
Hello Eivind Eklund!
Sun, Nov 07, 1999 at 14:25:22, eivind wrote about "Re: cvs commit: src/libexec/uucpd
uucpd.c"
in cvs-commiters@, cvs-all@:
> > Just for the record, this is considered a really bad thing, because
> > one common error is typing the password when the username is being
> > ex
On Mon, Nov 08, 1999 at 01:04:29PM +0200, Valentin Nechayev wrote:
[Regarding a change to UUCP to have it log the username when the
password entry fails]
> > I don't have any religious feeling about this change, and I'm willing
> > to back it out and keep it as a local change again (the way it has
I just cvsupped this morning, and noticed that now whenever I reboot (I do
this to make sure everything works right with the new kernel) the machine
does this:
syncing disks 15 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12
giving up..
Rebooting...
Then fsck has to fix a whole lot of stuf
Update, that is caused by a leak from my experimental branch into -current.
In message <[EMAIL PROTECTED]>, Kenneth Wayn
e Culver writes:
>I just cvsupped this morning, and noticed that now whenever I reboot (I do
>this to make sure everything works right with the new kernel) the machine
>does t
On Mon, 8 Nov 1999, Jean-Marc Zucconi wrote:
# > Jean-Marc Zucconi writes:
#
# > Try this in -current
# > $ cat some_file | head
#
# > I have to use ^C to regain control.
#
# ... and reverting to rev. 1.22 of eval.c fixes the problem.
Does revision 1.24 work?
# Jean-Marc
#
# --
# J
On Mon, 8 Nov 1999, Hellmuth Michaelis wrote:
> Check the reality. Have a look at the PnP documentation available for
> the old PnP architecture at
> http://www.freebsd.org/~luigi/pnp971020.tgz and then tell me where i
> find "as much or more" than this for the new one.
PnP devices are handled no
On Saturday, 6 November 1999 at 10:49:26 -0700, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Greg Lehey writes:
> : Nov 5 17:15:19 mojave /kernel: sio1: configured irq 3 not in bitmap of probed
>irqs 0
>
> Unless you are running pccardd, you won't see the pccard devices show
> up. The p
Alright I did what PHK told me to, and updated, but now for some reason
when I reboot, I can't get the root directory to keep the new kernel. this
is what happens before I reboot:
culverk:~> ls -l /kernel*
-r-xr-xr-x 1 root wheel 1551621 Nov 8 08:18 /kernel*
-r-xr-xr-x 1 root wheel 1551621
> Steve Price writes:
> On Mon, 8 Nov 1999, Jean-Marc Zucconi wrote:
> # > Jean-Marc Zucconi writes:
> #
> # > Try this in -current
> # > $ cat some_file | head
> #
> # > I have to use ^C to regain control.
> #
> # ... and reverting to rev. 1.22 of eval.c fixes the problem.
In message <[EMAIL PROTECTED]>, Kenneth Wayne
Culver writes:
>Alright I did what PHK told me to, and updated, but now for some reason
>when I reboot, I can't get the root directory to keep the new kernel. this
>is what happens before I reboot:
>
>culverk:~> ls -l /kernel*
>-r-xr-xr-x 1 root whe
We're building a few new systems. I wondered what the status
was of the 4.0 project (stability and release date estimate).
Thanks.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
In message <[EMAIL PROTECTED]>, Forrest Aldrich writes:
>We're building a few new systems. I wondered what the status
>was of the 4.0 project (stability and release date estimate).
We expect release Q1/2000 some time.
Feature freeze will probably happen this year.
--
Poul-Henning Kamp
In message <[EMAIL PROTECTED]> Greg Lehey writes:
: I need to check why I'm not getting irq 3 for the port, but everything
: else looks OK.
Likely because you don't have irq 3 listed in the line of available
irqs for pccardd
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscri
On Monday, 8 November 1999 at 10:05:54 -0700, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Greg Lehey writes:
> : I need to check why I'm not getting irq 3 for the port, but everything
> : else looks OK.
>
> Likely because you don't have irq 3 listed in the line of available
> irqs for pcc
> Here is the patch I've been working on (before I 1st got BDE's reply).
> The changes are mostly from OpenBSD + style changes for the way we do
> things. Can you also test this one?
>
>
> Index: bus.h
> ===
> RCS file: /home/ncvs/
On Sunday, 7 November 1999 at 16:52:12 +0100, Poul-Henning Kamp wrote:
>
> The main thing in this patch is to make bdevs use the same (ie: normal)
> vnode locking as character devices.
>
> Secondary effects are general cleanup in spec_vnops.c
>
> You should see no operational changes by applying
In message <[EMAIL PROTECTED]>, Greg Lehey writes:
>On Sunday, 7 November 1999 at 16:52:12 +0100, Poul-Henning Kamp wrote:
>>
>> The main thing in this patch is to make bdevs use the same (ie: normal)
>> vnode locking as character devices.
>>
>> Secondary effects are general cleanup in spec_vnops
Steve Price wrote:
> Just curious as to what the motivation for re-ordering the
> sa_flags and sa_mask members in sigaction were? The manpage
> still describes the old order BTW.
If sigset_t is to be changed again, then having it the last field in the
structure leaves us some room to avoid intr
Hi all,
just a very basic question that would resolve a dispute between colleagues.
When one talks about Fbsd3.3-STABLE my impression is that such version is a
stage before the Fbsd3.3-RELEASE. In other words the -RELEASE is for the
final version and the -STABLE is the version that is s
On Mon, Nov 08, 1999 at 07:47:23PM +, Theo PAGTZIS wrote:
> just a very basic question that would resolve a dispute between colleagues.
>
> When one talks about Fbsd3.3-STABLE my impression is that such version is a
> stage before the Fbsd3.3-RELEASE. In other words the -RELEASE is for t
On Mon, Nov 08, 1999 at 07:47:23PM +, Theo PAGTZIS wrote:
> just a very basic question that would resolve a dispute between colleagues.
>
> When one talks about Fbsd3.3-STABLE my impression is that such version is a
> stage before the Fbsd3.3-RELEASE. In other words the -RELEASE is for th
>
> just a very basic question that would resolve a dispute between colleagues.
>
> When one talks about Fbsd3.3-STABLE my impression is that such version is a
> stage before the Fbsd3.3-RELEASE. In other words the -RELEASE is for the
> final version and the -STABLE is the version that is s
On Mon, 8 Nov 1999, Jonathan M. Bresler wrote:
> ps. note this explaination is somewaht simplified, but it accurate in
> all its major points.
It's also explained quite clearly in the FAQ, for people who care to read
it.
Kris
Cthulhu for President! For when you're tired of choosing
On 1999-Nov-09 05:01:43 +1100, Luoqi Chen wrote:
>> + "=D" (addr), "=c" (count) :
>> + "r" (bsh + offset), "0" (addr), "1" (count) :
>> + "%eax", "memory");
>You may use "+D" and "+c" for the in-out operands,
> "
A hint for laptop users:
Change the ATTR for the normal case if you have a weak display:
options SC_NORM_ATTR="(FG_WHITE|BG_BLACK)"
options SC_NORM_REV_ATTR="(FG_BLACK|BG_WHITE)"
options SC_KERNEL_CONS_ATTR="(FG_YELLOW|BG_BLACK)"
options SC_KERNEL_CONS_REV_ATTR="(
Jonathan Lemon wrote...
> On Nov 11, 1999 at 01:41:48PM +0100, Dag-Erling Smorgrav wrote:
> > Note that the state transition diagram in RFC793 does not specify a
> > timeout for the CLOSING -> TIME_WAIT transition, so any faithful
> > implementation of RFC793 has this bug (but why doesn't this hap
Guys,
many thanks for the response. It seems to me though, that there is a vicious
circle that the user is locked in. If there are bugs that are resolved in
3.3-STABLE then the 3.4-RC should entail NO new functionality even if this is
supplemental. What I mean is that as a user you, (I feel)
On Mon, 8 Nov 1999, Theo PAGTZIS wrote:
> What are your views?
I think it's fine the way it is. It took me a few minutes to wrap my
mind around the FreeBSD release and patching schemata, but ever since
then, they've treated me pretty well.
--
Ben Rosengart
UNIX Systems Engineer, Skunk Group
On 1999-Nov-09 09:53:44 +1100, Theo PAGTZIS wrote:
> If there are bugs that are resolved in
>3.3-STABLE then the 3.4-RC should entail NO new functionality even if this is
>supplemental.
This (presumably) means that new functionality should only be
introduced at major releases (eg 3.0, 4.0 etc).
On Mon, 8 Nov 1999, Soren Schmidt wrote:
> It seems Andrzej Bialecki wrote:
> > >
> > > Oops, sos and I have developed a new version of libsvgl which can
> > > handle VESA modes in addition to the standard VGA graphics modes.
> > > But I haven't committed it to the source tree yet (yes, I should
Bruce Evans wrote:
> On Mon, 8 Nov 1999, Maxim Sobolev wrote:
>
> > Does anybody can explain why two absolutely identical attempts to remove
> > unexistent files on UFS and FAT32 yields different error codes ("No such
> > file or directory" and "Invalid argument" respectively)? This breaks "rm
>
On Tue, Nov 09, 1999 at 02:18:44AM +0200, a little birdie told me
that Maxim Sobolev remarked
>
> If your logic is right, then attempt to remove existent files from FAT using
> '*' should yield absolutely the same result (i.e. EINVAL). But in fact files
> being removed from FAT w/o any problems (
Why is the /dev names ida0?? for the disk when the kernel are trying to
mount rootdev to id0??? (Guess what... It is'nt compatibel ;)
What is the right thing ? And were should it be fixed ???
---
Nicolai Petri
WM-data Bfc
Denmark
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubsc
I'm currently programming a screensaver the shows statistics (cpu load and
stuff) but the interface for doing it in kernel mode sucks.. What is the
right way to do it ?
And would the screensaver be subject for entering the main source tree ?
---
Nicolai Petri
WM-data Bfc
To Unsubscribe: send
"Matthew D. Fuller" wrote:
> On Tue, Nov 09, 1999 at 02:18:44AM +0200, a little birdie told me
> that Maxim Sobolev remarked
> >
> > If your logic is right, then attempt to remove existent files from FAT using
> > '*' should yield absolutely the same result (i.e. EINVAL). But in fact files
> > be
In article
[EMAIL PROTECTED]>
you write:
>
>Why is the /dev names ida0?? for the disk when the kernel are trying to
>mount rootdev to id0??? (Guess what... It is'nt compatibel ;)
``ida'' is the name of the controller. ``id'' is the name of the disk.
--
Jonathan
To Unsubscribe: send mail to [
In message <001801bf175d$1a9a9940$05012ccf@bopper> "Bill A. K." writes:
: I've got a Rockwell PCI Modem thats full hardware, and I was wondering
: if anybody has written a driver for this kind yet.
I have written a driver for the pci hardware modems in -stable under
contract. I plan to port
44 matches
Mail list logo
