Hi,
Current sshd doesn't handle actual size of struct sockaddr correctly,
and does copy it as long as just size of struct sockaddr. So, sshd
deesn't log hostname into utmp correctly.
Here is a proposed patch to fix this problem. Please review it.
Sincerely,
Index: crypto/openssh/monitor.c
d
I notice reproductible effect on my recent -current remote machine, after
5-7 hours of normal work, I can't connect to this machine via
ssh,telnet,pop3 or ftp, but smtp and http continue to work normally.
When I turn ipfw2 off, this effect is gone. It was never happened for old
ipfw with the same
On Thu, Aug 01, 2002 at 12:11:05PM +0400, Andrey A. Chernov wrote:
> I notice reproductible effect on my recent -current remote machine, after
> 5-7 hours of normal work, I can't connect to this machine via
> ssh,telnet,pop3 or ftp, but smtp and http continue to work normally.
>
> When I turn ipf
Hajimu UMEMOTO <[EMAIL PROTECTED]> writes:
> Current sshd doesn't handle actual size of struct sockaddr correctly,
> and does copy it as long as just size of struct sockaddr. So, sshd
> deesn't log hostname into utmp correctly.
> Here is a proposed patch to fix this problem. Please review it.
C
Should one be able to do a source upgrade from an old -current (March 10)
to the latest? I have been trying, but it breaks in the cross tools
section in gnu/usr.bin/cc/cc_int. mkdep fails. There are a lot of warnings
that looks like this:
#
/home/src/gnu/usr.bin/cc/cc_int/../.
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
I have stumbled to this too, and thought I'm getting crazy. After
some hours of investigation, I have found that O'Brien did some
repo-surgery there, removed some revisions, and later replaced
them with the new stuff (well, new stuff took the same revisions),
and now some of your checked out sour
Revs.1.2-1.3 of tar/src/extract.c break pkg_add (not to mention probably
thousands of user scripts that are no more careful than pkg_add) in
-current and RELENG_4:
% RCS file: /home/ncvs/src/contrib/tar/src/extract.c,v
% Working file: extract.c
% head: 1.4
% branch:
% locks: strict
% access list:
sc0: at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0
Timecounters tick every 10.000 msec
Fatal trap 9: general protection fault while in kernel mode
instruction pointer = 0x8:0xc4109ac1
stack pointer = 0x10
Yup, you are right, thanks. I remember about the problem, but did not
remember the symptoms of it, so didn't put two and two together. :-(
> I have stumbled to this too, and thought I'm getting crazy. After
> some hours of investigation, I have found that O'Brien did some
> repo-surgery there, r
> sc0: at flags 0x100 on isa0
> sc0: VGA <16 virtual consoles, flags=0x300>
> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0
> Timecounters tick every 10.000 msec
>
> Fatal trap 9: general protection fault while in kernel mode
> instruction pointer = 0x8:0xc4109ac1
> stack pointer
Mitsuru IWASAKI wrote:
>>sc0: at flags 0x100 on isa0
>>sc0: VGA <16 virtual consoles, flags=0x300>
>>vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0
>>Timecounters tick every 10.000 msec
>>
>>Fatal trap 9: general protection fault while in kernel mode
>>instruction pointer = 0x8:0xc410
All,
Starting about a week ago, -current started refusing to boot on my TOS 5005-S504.
Depending on the config I use, it hard locks at boot in one of two places: either when
loading the fxp driver, or when probing the pci bus. And I do mean hard. I can't break
to debug, nothing. A power cyc
Hi,
we have a bug in setlocale(), it writes past
static char new_categories[_LC_LAST][ENCODING_LEN + 1];
in the do-while loop around line 159.
I get this backtrace
---snip---
(gdb) bt
#0 0x2816c9bc in kill () from /usr/lib/libc.so.4
#1 0x281af744 in abort () at /usr/src/lib/libc/../libc/stdl
On Thu, Aug 01, 2002 at 03:16:35PM +0300, Ruslan Ermilov wrote:
> I have stumbled to this too, and thought I'm getting crazy. After
> some hours of investigation, I have found that O'Brien did some
> repo-surgery there, removed some revisions, and later replaced
> them with the new stuff (well, n
On Thu, Aug 01, 2002 at 10:14:34PM +0900, Mitsuru IWASAKI wrote:
> Hmmm, I don't think so. How about typing
> unset acpi_load
> in loader prompt, and see if this panic disappear or still happen?
Where is it documented what to do to stop the autoloading of acpi.ko?
To Unsubscribe: send mai
On Thu, Aug 01, 2002 at 01:40:55AM +0900, Hajimu UMEMOTO wrote:
> makonnen> Thanks for spotting this. I think the following patch might be better.
> Thanks! I've just committed your version.
We probably should have decided if setkey should have been moved to
/sbin first. Is it reasonable to run
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
Hi,
> On Thu, 1 Aug 2002 10:45:08 -0700
> "David O'Brien" <[EMAIL PROTECTED]> said:
obrien> On Thu, Aug 01, 2002 at 01:40:55AM +0900, Hajimu UMEMOTO wrote:
> makonnen> Thanks for spotting this. I think the following patch might be better.
> Thanks! I've just committed your version.
obr
Since yesterday I've been getting the following error when running the
command `portsclean -DDi':
Detecting unreferenced distfiles...
(eval):9:in `chdir': No such file or directory -
"\"/usr/ports/Mk/bsd.port.mk\", line 1621: warning: duplicate script for
target \".BEGIN\" ignored\n\"/usr/ports/M
Hajimu UMEMOTO <[EMAIL PROTECTED]> writes:
> des> Could you please submit it to <[EMAIL PROTECTED]>?
> Yes, I'll sent it.
> Can I commit it to FreeBSD repo.?
No, please wait and see what the OpenSSH developers say.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EM
Hi,
> On 01 Aug 2002 11:05:46 +0200
> Dag-Erling Smorgrav <[EMAIL PROTECTED]> said:
des> Hajimu UMEMOTO <[EMAIL PROTECTED]> writes:
> Current sshd doesn't handle actual size of struct sockaddr correctly,
> and does copy it as long as just size of struct sockaddr. So, sshd
> deesn't log
Bruce Evans wrote:
>
> Revs.1.2-1.3 of tar/src/extract.c break pkg_add (not to mention probably
> thousands of user scripts that are no more careful than pkg_add) in
> -current and RELENG_4:
Are you sure? My own investigation at the time of the commit showed
that old tar shipped with FreeBSD, wa
Maxim Sobolev wrote:
>
> Bruce Evans wrote:
> >
> > Revs.1.2-1.3 of tar/src/extract.c break pkg_add (not to mention probably
> > thousands of user scripts that are no more careful than pkg_add) in
> > -current and RELENG_4:
>
> Are you sure? My own investigation at the time of the commit showed
Hi,
> On 01 Aug 2002 17:18:23 +0200
> Dag-Erling Smorgrav <[EMAIL PROTECTED]> said:
des> Hajimu UMEMOTO <[EMAIL PROTECTED]> writes:
> des> Could you please submit it to <[EMAIL PROTECTED]>?
> Yes, I'll sent it.
> Can I commit it to FreeBSD repo.?
des> No, please wait and see what the Op
On Wed, 31 Jul 2002, John Baldwin wrote:
> On 31-Jul-2002 Chris Knight wrote:
> > ...
> > the mfsroot floppy contents were too large
> > ...
> > the kern floppy contents were too large
> > ...
> > the fixit floppy contents were too large
> > ...
>
> Oof. It's like our binaries are suddenly very
Maxim Sobolev wrote:
>
> Maxim Sobolev wrote:
> >
> > Bruce Evans wrote:
> > >
> > > Revs.1.2-1.3 of tar/src/extract.c break pkg_add (not to mention probably
> > > thousands of user scripts that are no more careful than pkg_add) in
> > > -current and RELENG_4:
> >
> > Are you sure? My own investi
My recollection matches what Bruce says (and I have been
using unix since when version 7 was the latest and greatest).
At least the SUN OS 5.6 man page I could locate online says
this:
The o function modifier is only valid with the x function. p
Restore the named files to their original modes,
Bakul Shah wrote:
>
> My recollection matches what Bruce says (and I have been
> using unix since when version 7 was the latest and greatest).
> At least the SUN OS 5.6 man page I could locate online says
> this:
>
> The o function modifier is only valid with the x function. p
> Restore the na
On Fri, Aug 02, 2002 at 02:57:44AM +1000, Bruce Evans wrote:
> I'm surprised -Os [-falign...] isn't already the default for crunches.
-Os is -O2 except for those optimizations which bloat. We don't trust
-O2 and thus maybe should not -Os. Hopefully we have found all our bad
in-line ASM and -O2
In the last episode (Aug 01), David O'Brien said:
> On Fri, Aug 02, 2002 at 02:57:44AM +1000, Bruce Evans wrote:
> > I'm surprised -Os [-falign...] isn't already the default for
> > crunches.
>
> -Os is -O2 except for those optimizations which bloat. We don't trust
> -O2 and thus maybe should no
On 01-Aug-2002 Bruce Evans wrote:
> On Wed, 31 Jul 2002, John Baldwin wrote:
>
>> On 31-Jul-2002 Chris Knight wrote:
>> > ...
>> > the mfsroot floppy contents were too large
>> > ...
>> > the kern floppy contents were too large
>> > ...
>> > the fixit floppy contents were too large
>> > ...
>>
>
On Thu, 1 Aug 2002, Maxim Sobolev wrote:
> Maxim Sobolev wrote:
> >
> > Maxim Sobolev wrote:
> > >
> > > Bruce Evans wrote:
> > > >
> > > > Revs.1.2-1.3 of tar/src/extract.c break pkg_add (not to mention probably
> > > > thousands of user scripts that are no more careful than pkg_add) in
> > > >
On Thu, 1 Aug 2002, David O'Brien wrote:
> On Fri, Aug 02, 2002 at 02:57:44AM +1000, Bruce Evans wrote:
> > I'm surprised -Os [-falign...] isn't already the default for crunches.
>
> -Os is -O2 except for those optimizations which bloat. We don't trust
> -O2 and thus maybe should not -Os. Hopef
On Thu, 1 Aug 2002, Maxim Sobolev wrote:
> Bakul Shah wrote:
> >
> > My recollection matches what Bruce says (and I have been
> > using unix since when version 7 was the latest and greatest).
> > At least the SUN OS 5.6 man page I could locate online says
> > this:
> >
> > The o function modifie
> Well, OK, now I am really confused. So what should we be bound to? To
> the POLA (old GNU tar in 4.6-release and downward was not fully
> preserving permissions unless -p is specified, even when invoked by
> root)? Or to what other systems do? Bruce, what do you think?
Okay, I did some more res
< said:
> If it were upto me I'd choose what POSIX says.
POSIX says to use pax(1). There is no `tar' in POSIX. (There is,
unfortunately, a cpio(1) in POSIX.)
-GAWollman
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I am currently running Current on an u60
and it seems to be running quite nicely minus
some gotchas and not yet working ports.
Thanks for the hard work.
I do however have one pretty strange problem.
Some apps cant seem to route properly, aka they
cant reach remote hosts because routing lookups b
Desription:
unauthorized write access to /etc directory using chfn/chsh commands in FreeBSD
5.0-CURRENT.
Contributing factors:
In FreeBSD 5.0, it is possible to fill up the whole partition by using chfn/chsh
commands. Normally, users have quotas set up on directories that are allowed to be
* De: Peter Schultz <[EMAIL PROTECTED]> [ Data: 2002-08-01 ]
[ Subjecte: portupgrade problem ]
> Since yesterday I've been getting the following error when running the
> command `portsclean -DDi':
That's partly my fault, but largely the fault of things getting the output of
make -V in the
David O'Brien writes:
> On Thu, Aug 01, 2002 at 10:14:34PM +0900, Mitsuru IWASAKI wrote:
> > Hmmm, I don't think so. How about typing
> >unset acpi_load
> > in loader prompt, and see if this panic disappear or still happen?
>
> Where is it documented what to do to stop the autoloading
Galen Sampson wrote:
> I started seeing this on a -current machine about 5 months ago. The -current
> was pre gcc3.1 and pre KSE. Samba was 2.2.3. Updating -current solved the
> problem for me.
It has been kinda on and off here. With some -CURRENT builds it would
happen, with some it wouldn't
I've been reading -current for a while and waiting for an island of
relative stability to show up, ideally -DP2, so that I can install it
on my own home systems and start exploring the new release track.
I doubt I'm going to be able to contribute much to the kernel dev,
which is why I'm not a
Michael Nottebrock wrote:
> sc0: at flags 0x100 on isa0
> sc0: VGA <16 virtual consoles, flags=0x300>
> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0
> Timecounters tick every 10.000 msec
>
> Fatal trap 9: general protection fault while in kernel mode
> instruction pointer=
Michael Nottebrock wrote:
> I tweaked my BIOS to assign a different irq (9) to
> the NIC and now the kernel boots and runs my old userland quite nicely.
> The old kernel ran perfectly well with the NIC on irq10 ... strange.
None of your other postings identified the devices also on
IRQ10. If I h
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
Terry Lambert wrote:
> Michael Nottebrock wrote:
>
>>I tweaked my BIOS to assign a different irq (9) to
>>the NIC and now the kernel boots and runs my old userland quite nicely.
>>The old kernel ran perfectly well with the NIC on irq10 ... strange.
>
>
> None of your other postings identified t
Michael Nottebrock wrote:
> >>I tweaked my BIOS to assign a different irq (9) to
> >>the NIC and now the kernel boots and runs my old userland quite nicely.
> >>The old kernel ran perfectly well with the NIC on irq10 ... strange.
> >
> > None of your other postings identified the devices also on
>
Apparently, On Fri, Aug 02, 2002 at 12:02:28AM +0200,
Sten said words to the effect of;
>
> I am currently running Current on an u60
> and it seems to be running quite nicely minus
> some gotchas and not yet working ports.
> Thanks for the hard work.
>
> I do however have one pretty str
On Thu, Aug 01, 2002 at 15:43:56 +0200, Alexander Leidinger wrote:
> Hi,
>
> we have a bug in setlocale(), it writes past
> static char new_categories[_LC_LAST][ENCODING_LEN + 1];
> in the do-while loop around line 159.
Thanx, fixed.
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: s
The 505ES comes with a builtin Orinoco, wi0 recognizes it but
1. under stable continually comes up with wi0 watchdog timer messages,
and won't DHCP handshake (it will connect to the AP).
2. Under current-newcard, boot stops with a panic at the second PCCBB,
saying unable to connect IRQ (offhand i
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
FYIfrom my Linux User Group maillist.
--karl
>X-Authentication-Warning: quince.tricity.wsu.edu: majordomo set sender to
>[EMAIL PROTECTED] using -f
>Date: Thu, 1 Aug 2002 13:20:48 -0700
>From: Ed <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: <3CLUG> [[EMAIL PROTECTED]: openssh-3
53 matches
Mail list logo
