On Sun, Dec 15, 2002 at 06:39:52PM -0800, Doug Barton wrote:
> On Mon, 16 Dec 2002, Harald Hanche-Olsen wrote:
>
> > The main reason I decided to try 5.0-RC1 on my brand new Dell Inspiron
> > 4150 is a minor problem with suspending the machine under 4.7: After
> > wakeup, the fan runs full speed a
On Sun, Dec 15, 2002 at 02:47:51PM -0800, Matthew Dillon wrote:
> :
> :How about renaming swapon(8) into swapctl(8) after this function enhancemen=
> :t?
> :This name reflects it's purpose much better and would be consistent with the
> :other BSDs.
> :
> :- Christian
>
> I think that's an exce
From: Giorgos Keramidas <[EMAIL PROTECTED]>
Subject: Re: recent openssh problem
Date: Fri, 13 Dec 2002 20:18:51 +0200
> On 2002-12-13 08:34, Terry Lambert <[EMAIL PROTECTED]> wrote:
> > Daniel O'Connor wrote:
> > > On Fri, 2002-12-13 at 15:53, CHOI Junho wrote:
> > > > % ssh -2 -N -f -L 9595:rem
Greg 'groggy' Lehey wrote:
> > Add to this that Bosko's workaround for the CPU bug with PSE/PGE
> > includes loading the kernel at 4M rather than 1M.
>
> I'm not sure I understand you. i386's have a 32 bit address space,
> and long ago we loaded at 0xf000 (3.75M). Then we dropped it to
> 0xc
I used a laptop(IBM ThinkPad A21m,ATI Mobile p video
card),with the FreeBSD 5.0-current installed.
I added the follow line to the kernel config file:
options VESA
options SC_PIXEL_MODE
After rebooting the laptop with the new kernel, to
alter the revolution, I tried to use the follow
command : vid
At 08:31 PM 12/15/2002 -0800, David Yeske wrote:
Anyone else having issues with sshd on current?
Dec 15 23:23:24 stuff sshd[843]: fatal: ssh_msg_send: write
Yup, on a userland I built today. I see a few sshd commits
yesterday, relating to pam. Probably broke thereabouts... ?
--
Christophe
Anyone else having issues with sshd on current?
Dec 15 23:23:24 stuff sshd[843]: fatal: ssh_msg_send: write
debug1: next auth method to try is keyboard-interactive
Connection closed by 192.168.1.66
debug1: Calling cleanup 0x804bed0(0x0)
__
Do you
On Mon, Dec 16, 2002 at 03:37:58AM +0100, Harald Hanche-Olsen wrote:
> Shouldn't libposix1e.so.2 have been part of the compat4x package?
> I came across at least one program that uses it.
>
There are numerous libraries missing from compat4x.
A worse problem is that several 4.x shared libs
have th
I plan to deploy GBDE in an environment in which the absolute maximum of
the system that can reasonably be kept encrypted on disk will be kept
in an encrypted format.
The system has the following requirements:
1) It must remain possible to administer the host over ssh. This
includes rebooting the
(This is the last of my current batch of 5.0-RC1 problems.)
Yeah, I know, X server problems ought to be reported to the XFree
maintainers. Is there any interest for details of it here?
The synopsis: The X server crashes under 5.0-RC1 where it runs fine
with the exact same configuration under 4.
Despite the following lines in dmesg...
cbb0: at device 1.0 on pci2
cardbus0: on cbb0
pccard0: <16-bit PCCard bus> on cbb0
cbb1: at device 1.1 on pci2
cardbus1: on cbb1
pccard1: <16-bit PCCard bus> on cbb1
...no /dev/card0 (or /dev/card1) appears, and so pccardc and pccardd
fail. Shouldn't t
On Mon, 16 Dec 2002, Harald Hanche-Olsen wrote:
> The main reason I decided to try 5.0-RC1 on my brand new Dell Inspiron
> 4150 is a minor problem with suspending the machine under 4.7: After
> wakeup, the fan runs full speed and will not settle until I reboot.
>
> However, with 5.0-RC1 the machin
Shouldn't libposix1e.so.2 have been part of the compat4x package?
I came across at least one program that uses it.
- Harald
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
The main reason I decided to try 5.0-RC1 on my brand new Dell Inspiron
4150 is a minor problem with suspending the machine under 4.7: After
wakeup, the fan runs full speed and will not settle until I reboot.
However, with 5.0-RC1 the machine just freezes if I try suspending it.
Theres is no reacti
For some reason, I can't find a way to create a swap partition using
the disklabel editor - other than by using Auto Defaults - and then I
can't see any way to adjust the size of the resulting swap partition.
This never was a problem with 4.x as far as I can remember...?
(After first discovering
On Sat, 14 Dec 2002, [EMAIL PROTECTED] wrote:
> >> FreeBSD still runs on all 386 family CPUs, the only difference is that
> >> if you want to run it on a 80386 you need to enable an option in
> >> your kernel config file.
> >> It will out of the box run on 486 and anything later.
> >
> >It means t
:
:How about renaming swapon(8) into swapctl(8) after this function enhancemen=
:t?
:This name reflects it's purpose much better and would be consistent with the
:other BSDs.
:
:- Christian
I think that's an excellent idea. We would have to do some
rewriting to add the expected options bu
I ran truss on both cvs and ssh and they stop at the following points:
cvs:
open("/home/avatar/.cvsignore",0x0,0666) ERR#2 'No such file or
directory'
access("/home/avatar/.cvswrappers",0)ERR#2 'No such file or
directory'
pipe() = 3 (0
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
On Sun, Dec 15, 2002 at 11:46:55AM -0800, Matthew Dillon wrote:
> David Schultz's swapoff code has been comitted. It should be regarded
> as being highly experimental (and it still needs to be vetted for
> VM locking changes and other recent changes in -current). A considerable
>
On Saturday, 14 December 2002 at 20:53:05 -0800, Terry Lambert wrote:
> Alex wrote:
>> It means that you can not install FreeBSD on a 386 unless you have a
>> 486+ machine that can compile a new FreeBSD system and have a way to
>> get that version to the 386.
>
> Yes, this is true. Several of us w
On Saturday, 14 December 2002 at 20:55:05 -0800, Terry Lambert wrote:
> "M. Warner Losh" wrote:
>> One problem with most 386 boxes is that they have very little memory.
>> sysinstall is a big, bloated pig dog these days that takes more RAM
>> than most 386 boxes have. This is true also for many 48
At 9:23 PM +0100 2002/12/15, Claudio Nieder wrote:
> Problem: After that question the install programm immediatly tries to
> contact the DHCP server, which cannot work, as informations like the WEP
> key to use etc. were asked for/supplied so that the wireless card could
> be properly set up
At 9:23 PM +0100 2002/12/15, Claudio Nieder wrote:
Problem: After that question the install programm immediatly tries to
contact the DHCP server, which cannot work, as informations like the WEP
key to use etc. were asked for/supplied so that the wireless card could
be properly set up to commu
Hi,
after updating my -CURRENT today (sun dec 15) I can no longer connect to my
local cvs and sshd.
cvs returns:
Connection closed by 217.208.105.23
cvs [commit aborted]: end of file from server (consult above messages if any)
and ssh returns:
Connection closed by 217.208.105.23
Both these wor
walt wrote:
>
> [EMAIL PROTECTED] wrote:
>
> > Because few if any 80386 computers have the ram it takes to run sysinstall.
>
> Was sysinstall around when 386 was new? Just curious what's changed since
> then to make it bigger.
The sheer number of new drivers, for one thing.
--
Daniel C. Sobr
On Sun, Dec 15, 2002 at 11:08:01AM -0800, Matthew Dillon wrote:
>
> :
> ::This is complete BULLSHIT, Warner.
> :
> :Your attitude it totally unacceptible. Learn to play well with
> :others, or get the fuck out of the project.
>
> Really? You think I should learn to play well with oth
Ok. so
On Fri, 13 Dec 2002, Julian Elischer wrote:
>
>
> On Fri, 13 Dec 2002, Nate Lawson wrote:
>
> > On Fri, 13 Dec 2002, Julian Elischer wrote:
> > > On Fri, 13 Dec 2002, Peter Wemm wrote:
> > > > Julian Elischer wrote:
> > > > > looking at the code in src/sys/i386/i386/dump_machdep.c,
>
What it comes down to is what developers are willing to do. My
contribution is 'ipfw unbreak'. If someone else has a solution that
they are willing to work on and commit in the next four weeks, then
fine. But if nobody is willing to work on and commit another solution
in the next
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
whe I posted this problem to comp.unix.bsd.freebsd.misc it was suggested
to me I should report it to this e-mail addres. I can't yet use send-pr,
which was suggtested too, as my FreeBSD installation is not finished yet.
This is the "oddity" I not
On Sun, Dec 15, 2002 at 08:00:55PM +, Gavin Atkinson wrote:
> Confirmed. in su.c it seems that pam_authenticate is returning
> PAM_AUTH_ERR, when it presumably should not be doing so.
Try getting rid of the auth_as_self in /etc/pam.d/su for the
pam_wheel module.
David.
To Unsubscribe
On Sun, 15 Dec 2002, Matthew Dillon wrote:
> Here's a new patch. But there isn't much of a point if we do not
> also disallow ipfw DELETE and FLUSH. And the pipe config commands
> as well as anything else that changes the firewall state. Firewalls
> are there to protect the syste
On Sun, 15 Dec 2002, Craig Boston wrote:
> On a laptop running current, I have a problem using the su program
> multiple times (nested).
>
> (log in as auser)
> $ id
> uid=1002(auser) gid=1002(auser) groups=1002(auser)
> $ su - buser
> Password:
> $ id
> uid=1001(buser) gid=1001(buser) groups=1001
< said:
> Was sysinstall around when 386 was new? Just curious what's changed since
> then to make it bigger.
The 80386 came out in 1986. FreeBSD 1.0 came out in 1994, and I don't
think we even had sysinstall then.
I did a lot of 386BSD work on a 386SX/16, which was already old by the
time I g
< said:
> If people are reasonable with me, I am reasonable right back. If
> people are unreasonable, they shouldn't expect me to be reasonable
> in response. It's really that simple.
As a FreeBSD developer, you are expected to be civil to your fellow
developers at all times, as sta
David Schultz's swapoff code has been comitted. It should be regarded
as being highly experimental (and it still needs to be vetted for
VM locking changes and other recent changes in -current). A considerable
amount of testing has been done already but -current is a moving target.
:
:< said:
:
:> Now you are forcing me to go to core. It's absolutely ridiculous and
:> you know it. Goddamn it, next time I won't even bother posting if all
:> I get is this sort of crap.
:
:All the better, if you refuse to be civil to your fellow developers.
:
:-GAWollman
If p
:I've answered this in other email, but you need to expand the check at
:the top of ipfw_ctl to include this new message as one of the ones
:that is disallowed at high security levels.
:
:Warner
Here's a new patch. But there isn't much of a point if we do not
also disallow ipfw DELETE and
< said:
> Now you are forcing me to go to core. It's absolutely ridiculous and
> you know it. Goddamn it, next time I won't even bother posting if all
> I get is this sort of crap.
All the better, if you refuse to be civil to your fellow developers.
-GAWollman
To Unsubscribe: sen
There was a problem with snapshots that lead to incomplete checking
by background fsck which in turn could lead to the problem that you
were seeing (i.e., repeated failures until fsck was run manually).
This problem was fixed with version 1.54 of ufs/ffs/ffs_snapshot.c
which was checked in on Dec 1
:Also, fixing the ipfw2 abi is probably a good item to put on the list
:for getting 5.x to 5-STABLE. Please don't waste time with band-aids
:that will make people forget that ipfw2 needs attention.
:
:Scott
This is a reasonable line of argument but my opinion is that it
hasn't been fix
Matthew Dillon wrote:
> [ useless drivel removed ]
There's still a TODO list for 5.0. It was even mailed out to
developers@ this morning. If you have time to spare in your day, please
focus your attention to that right now.
Also, fixing the ipfw2 abi is probably a good item to put on the lis
In message: <[EMAIL PROTECTED]>
Matthew Dillon <[EMAIL PROTECTED]> writes:
: When people say and do reasonable things I am a reasonable guy. When
: people say and do unreasonable things then I fight tooth and nail.
: It's that simple. If you don't like it, then tough.
In message: <[EMAIL PROTECTED]>
Matthew Dillon <[EMAIL PROTECTED]> writes:
:
: :
: ::This is complete BULLSHIT, Warner.
: :
: :Your attitude it totally unacceptible. Learn to play well with
: :others, or get the fuck out of the project.
: :
: :I am *NOT* blocking you. I'm telli
:
::This is complete BULLSHIT, Warner.
:
:Your attitude it totally unacceptible. Learn to play well with
:others, or get the fuck out of the project.
Really? You think I should learn to play well with others? You
think it's appropriate to request that I spend a man week rewriti
:
::This is complete BULLSHIT, Warner.
:
:Your attitude it totally unacceptible. Learn to play well with
:others, or get the fuck out of the project.
:
:I am *NOT* blocking you. I'm telling you you need to get the SO's
:sign off to make sure that there isn't a security issue because the
:c
:
:In message: <[EMAIL PROTECTED]>
:Matthew Dillon <[EMAIL PROTECTED]> writes:
:: :
:: :The real fix is to fix the abi problems.
:: :
:: :Warner
::
:: Doh!!Thanks for volunteering to fix the ABI problems. No? You
:: don't want to do it? Gee, I saw that one coming a mile
In message: <[EMAIL PROTECTED]>
Matthew Dillon <[EMAIL PROTECTED]> writes:
: :
: :The real fix is to fix the abi problems.
: :
: :Warner
:
: Doh!!Thanks for volunteering to fix the ABI problems. No? You
: don't want to do it? Gee, I saw that one coming a mile away!
:
:This is complete BULLSHIT, Warner.
Your attitude it totally unacceptible. Learn to play well with
others, or get the fuck out of the project.
I am *NOT* blocking you. I'm telling you you need to get the SO's
sign off to make sure that there isn't a security issue because the
current defa
On Sun, 15 Dec 2002 10:26:22 -0800 (PST)
Matthew Dillon <[EMAIL PROTECTED]> wrote:
Hi,
must...resist...
> So don't give me this bullshit about the patch being a security
> issue. YOU KNOW IT ISN'T.
No, Warner has a point, that patch is simply bandaid (albeit a good
one).
> Now you
:How about sending the patch to the Technical Review Board, trb@ instead.
:
:Thanks.
:
:Cheers,
:
:--
:Anders.
Getting bored sitting on your buns? It's already gone to core and,
frankly, I think core is the proper forum now that Warner has declared
it a security issue (when it obvio
Hi,
On Sun, Dec 15, 2002 at 10:26:22AM -0800, Matthew Dillon wrote:
> This is complete BULLSHIT, Warner. This patch exists precisely so
> the firewall can be turned on in secure mode. It does not make it
> any easier to turn off then adding a rule:
>
> ipfw add 2 allow all from
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
:
:The real fix is to fix the abi problems.
:
:Warner
Doh!!Thanks for volunteering to fix the ABI problems. No? You
don't want to do it? Gee, I saw that one coming a mile away!
THEN DON'T COMPLAIN.
This is not a fucking security issue. This is a patch that solves
a ma
:I don't like the patch from a security standpoint. It makes it to
:easy to turn off a firewall. If you want to be that stupid about
:security, you should just make the default be 'accept all' and be done
:with it. I'm opposed to this patch unless you can get the security
:officer to sign off on
In message: <[EMAIL PROTECTED]>
Matthew Dillon <[EMAIL PROTECTED]> writes:
: :I disagree with committing this hack; keep it as a local mod if you must.
: :
: :As to the problem; don't wait for Luigi to "fix the ABI problems", do it
: :yourself. Good things happen when folks are PO'd a
On a laptop running current, I have a problem using the su program
multiple times (nested).
I have two accounts, I'll call them "auser" and "buser". I use auser
for my everyday activities; it has no special privileges. buser is a
member of the wheel group. I don't make auser a member of wheel b
In message <[EMAIL PROTECTED]>, walt writes:
>[EMAIL PROTECTED] wrote:
>
>> Because few if any 80386 computers have the ram it takes to run sysinstall.
>
>Was sysinstall around when 386 was new? Just curious what's changed since
>then to make it bigger.
sysinstall arrived in the 486 days.
Lots o
Hi,
I've got a problem with jail(2), that affects both -STABLE and
-CURRENT (Tested on a 4.7-RELEASE and on a CURRENT updated the 12/14/2002,
both on i386)
I've found a reference to this problem in PR kern/26506, but it's 1,5years
old and it's still not fixed, and I think I've also found a proble
>Was sysinstall around when 386 was new?
No, and neither was FreeBSD.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
[EMAIL PROTECTED] wrote:
Because few if any 80386 computers have the ram it takes to run sysinstall.
Was sysinstall around when 386 was new? Just curious what's changed since
then to make it bigger.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the bod
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
subscribe freebsd-current
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Hi,
I tried to compile arla 0.35.11 on FreeBSD 5.0-RC1. Fisrt I got
following error:
checking for udev2dev in kernel... yes
checking for snprintf in kernel... yes
checking for nosys in kernel... yes
checking for sys_nosys in kernel... no
checking for sys_lkmnosys in kernel... no
checking for cach
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
In message <[EMAIL PROTECTED]>, Nate Lawson wri
tes:
>On Sun, 15 Dec 2002, Erik Trulsson wrote:
>> The only remotely good reason I have heard for removing support for 386
>> in the default configuration is that having it in would pessimize
>> performance too much for more modern CPUs. How valid th
On Sun, 15 Dec 2002, Erik Trulsson wrote:
> The only remotely good reason I have heard for removing support for 386
> in the default configuration is that having it in would pessimize
> performance too much for more modern CPUs. How valid that reason is I
> cannot judge, but I guess it is possible
On Sun, Dec 15, 2002 at 12:18:21AM -0500, Craig Reyenga wrote:
> Sorry for butting in, but my $.02 is that 386's are old enough that
> FreeBSD, or any other OS for that matter, shouldn't wait up for them.
Why not? An OS in itself should not require a lot of CPU power.
> They've gotten to the poi
[ ok, really cc him this time]
On Sun, Dec 15, 2002 at 01:02:51AM -0800, Mike Makonnen wrote:
>
> [ cc'ed imp@ since the second one concerns changes he recently made ]
>
> On Sat, Dec 14, 2002 at 02:24:12PM -0800, Galen Sampson wrote:
> >
> > 17c17
> > < pidfile="/var/run/${name}.pid"
> > ---
>
[ cc'ed imp@ since the second one concerns changes he recently made ]
On Sat, Dec 14, 2002 at 02:24:12PM -0800, Galen Sampson wrote:
>
> 17c17
> < pidfile="/var/run/${name}.pid"
> ---
> > pidfile="/var/run/${name}/pid"
>
> in order to match the default named.conf file.
Yes, definitely a bug. I
From: KT Sin <[EMAIL PROTECTED]>
Subject: Re: cbb attach failed
Date: Sun, 15 Dec 2002 13:29:42 +0800
Message-ID: <[EMAIL PROTECTED]>
> If your CURRENT is pretty recent, please add into your /boot/loader.conf
>
> hw.pci.allow_unsupported_io_range="1"
>
> and then reboot.
it works file.
th
72 matches
Mail list logo
