Joerg Sonnenberger | 1 Feb 2004 20:23
Picon

Re: New Here

On Sat, Jan 31, 2004 at 10:03:43PM -0000, dboling02 wrote:
> Hi All,
> 
> I have recently installed OBSD 4.3, and have been looking for the
> "Gnome Desktop Manager" for OBSD. Does it exsist? Is there any
> advantage to it over XDM?

This question belongs not on tech <at> , but on ports <at>  or even misc <at> .
GDM has both advantages and disadvantages. The greatest disadvantage
and one reason to avoid it is his history. GDM have had much more
security problems than both XDM and KDM. The former is proven and
light, you may want to stick to it if there are no good reasons
to use something else.

> I have Gnome running on XDM but some things seem to work not quite
> right with it.

Post a mail with this problems to ports <at>  or misc <at> , you might get help
there. But of course RTFM first ;-)

Joerg

> TIA,
> 
> Don

slick | 2 Feb 2004 04:14
Picon

My new fdisk(8) program.

Hi,
	I decided to write a new fdisk(8) program for unix. The main goal was to be
able to do all the MBR manipulation from the command line, to be portable
across all unix platform using libc, to work alone, to be as small and
simple as possible and to be easy to maintain and extend.

	I did it.

	Program:
		- do anything the exiting fdisk(8) do and even more(also more to come).
		- compiles, run and work on any sane unix platform with standard libc.
		- has no need for anything else than "/bin/sh" and "/usr/lib/libc*".
		- is 10 times smaller.
		- in pure C.
		- has no struct.

	I tested it, but you know I might have forget some details or even do
things better.

	Please review the code, the structure, the functionality and the error
possibility.

	I accept any (good and/or bad) feedback if its constructive.

	Thanks for taking the time to do so and if you don't thanks anyway...

	Slick
	Plan B
	Plan_b <at> videotron.ca

(Continue reading)

slick | 2 Feb 2004 05:11
Picon

My new fdisk(8) program.

Hi,
	I decided to write a new fdisk(8) program for unix. The main goal was to be
able to do all the MBR manipulation from the command line, to be portable
across all unix platform using libc, to work alone, to be as small and
simple as possible and to be easy to maintain and extend.

	I did it.

	Program:
		- do anything the exiting fdisk(8) do and even more(also more to come).
		- compiles, run and work on any sane unix platform with standard libc.
		- has no need for anything else than "/bin/sh" and "/usr/lib/libc*".
		- is 10 times smaller.
		- in pure C.
		- has no struct.

	I tested it, but you know I might have forget some details or even do
things better.

	Please review the code, the structure, the functionality and the error
possibility.

	 http://paste.msunix.org/index.php?view=4963

	I accept any (good and/or bad) feedback if its constructive.

	Thanks for taking the time to do so and if you don't thanks anyway...

	Slick
	Plan B
(Continue reading)

Maciej Nadolski | 2 Feb 2004 09:33
Picon
Favicon

3.4-current PF bug?

Hi !

 Currently I`m using 3.4-current and I think I`ve found a problem with
 it. It is not a bug so I haven`t sent this post to bug list.
 The problem:
 If I want to use limiting of created states in my internal lan which
 is behing nat it is imposible, beacouse pf goeas mad.
 My thoughts:
 Limiting of states need keep state directive in the rule. nat crates
 it`s own state and thats why there is a problem.
 This is the easiest way to describe it. Limiting might sometimes work
 but in random.. I tried to use this great feature together with altq
 enabled and the result of that was stop of working few queues. I
 think that it isn`t problem beacouse it is still -current. I wanted
 inform about my discover. Maybye someone successfully done this so I
 should go to misc?

--

-- 
Regards,
 Maciej Nadolski                          mailto:krecik-usenet <at> go2.pl

Thierry Deval | 2 Feb 2004 11:06
Picon

Re: My new fdisk(8) program.

Hi,

By curiosity, I glanced over the code and...
- No interactive mode ?
- Why not use getopt(3) for the arguments parsing ?
- Your usage formatting is, hmm, non-intuitive...

And what's this license ?  Is it supposed to be BSD-like ?
/*
  *
  * Copyright (c) 2004 Plan B
  * All Rights Reserved.
  *
  * Permission to use, copy, modify and distribute this software and its
  * documentation is hereby granted, provided that both the copyright
  * notice and this permission notice appear in all copies of the
  * software, derivative works or modified versions, and any portions
  * thereof, and that both notices appear in supporting documentation.
  *
  * Plan B ALLOWS FREE USE OF THIS SOFTWARE IN ITS "AS IS"
  * CONDITION. PLAN B DISCLAIMS ANY LIABILITY OF ANY KIND FOR
  * ANY DAMAGES WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE.
  *
  * PLAN B requests users of this software to return to
  *
  *   Slick
  *   Plan B
  *   Montreal, Quebec
  *   plan_b <at> videotron.ca
  *
(Continue reading)

Steve Vitale | 2 Feb 2004 17:22

ssh timeouts

I'm running 3.2 Generic with OpenSSH 3.5 and authpf to authorize
wireless users.

Until a few months ago, this worked flawlessly.  Since then, apparently a
patch to newer Windows XP Pro clients causes them to timeout on the
inactive ssh sessions.  Any hints on what I can do either on the client or
server sides to fix this problem?  I'm pretty sure this is an OS problem,
not a client software problem because it happens with any ssh software I
use.

The log I see in the firewall when the disconnect occurs looks like this:

"Jan 30 13:24:38 knight sshd[23215]: Disconnecting: Timeout, your session
not responding."

Mac OS X clients still work fine.

Thanks so much for any help you can give:)

Steve Vitale
http://www.gcrc.upenn.edu/~steve

Pierre-Yves Ritschard | 2 Feb 2004 17:45

Re: My new fdisk(8) program.

slick wrote:

>	Please review the code, the structure, the functionality and the error
>possibility.
>
>	 http://paste.msunix.org/index.php?view=4963
>
>	I accept any (good and/or bad) feedback if its constructive.
>  
>

you might want to prepare a port for it and submit it to the ports <at>  
mailing-list for inclusion in the ports tree, that way you'll be
able to gather more input from users.

Pierre-Yves

Anthony Roberts | 2 Feb 2004 19:27
Picon
Favicon

Re: ssh timeouts

>"Jan 30 13:24:38 knight sshd[23215]: Disconnecting:
>Timeout, your sessionnot responding."

I get this all the time when I log in to home from work, and some friends 
have this problem logging in to my computer from behind the university's 
firewall. It happens because their firewall/nat drops the connection after 
the connection has been idle for a given period. I don't know why that would 
happen on a Windows machine on the physical network. Something is making 
idle connections time out on Windows computers, and I don't think it's your 
client software. It's probably either firewall software or Windows itself. 
It occurs to me that the Windows network stack might actually have been 
altered to time out idle connections all by itself, so they don't have to 
fix other parts of the OS that are being sloppy. I don't know, but I 
wouldn't be surprised either way.

In either case, something is timing out the connection. The workaround is to 
enable client side keepalive signals. This can be done in Putty in the 
connection properties. I don't know about other software, but it can 
probably do it too.

_________________________________________________________________
MSN 8 with e-mail virus protection service: 2 months FREE*  
http://join.msn.com/?page=features/virus&pgmarket=en-ca&RU=http%3a%2f%2fjoin.msn.com%2f%3fpage%3dmisc%2fspecialoffers%26pgmarket%3den-ca

Curtis H. Wilbar Jr. | 3 Feb 2004 03:32

Re: ssh timeouts

This doesn't belong on tech <at> ... so this is cc'd to misc <at>  where it
should be moved to...

I've solved the problem with firewalls timing out the state for
ssh connections that are idle longer than the firewall keeps
states by adding the following to /etc/ssh/sshd_config on boxes
you ssh into:

ClientAliveInterval     60

If you don't control the box you ssh into, then all you can do is
contact whomever runs the system and see if they will be kind enough
to add this.

-- Curt

On Mon, 2004-02-02 at 13:27, Anthony Roberts wrote:
> >"Jan 30 13:24:38 knight sshd[23215]: Disconnecting:
> >Timeout, your sessionnot responding."
> 
> I get this all the time when I log in to home from work, and some friends 
> have this problem logging in to my computer from behind the university's 
> firewall. It happens because their firewall/nat drops the connection after 
> the connection has been idle for a given period. I don't know why that would 
> happen on a Windows machine on the physical network. Something is making 
> idle connections time out on Windows computers, and I don't think it's your 
> client software. It's probably either firewall software or Windows itself. 
> It occurs to me that the Windows network stack might actually have been 
> altered to time out idle connections all by itself, so they don't have to 
> fix other parts of the OS that are being sloppy. I don't know, but I 
(Continue reading)

PecheninAV | 4 Feb 2004 07:42
Picon
Favicon

Fw: ega.c; callout.h

----- Original Message -----
From: PecheninAV
To: misc <at> openbsd.org
Sent: Wednesday, February 04, 2004 1:23 PM
Subject: ega.c; callout.h

      do you happen to have callout.h ?


Gmane