Ed Ahlsen-Girard | 1 Aug 2010 02:03
Picon

Re: X login screen

On Sat, 31 Jul 2010 15:18:03 -0400
RD Thrush <rd <at> thrush.com> wrote:

> On 07/31/10 10:13, Ed Ahlsen-Girard wrote:
> > Dmesg says 4.8-beta.
> > 
> > Login screen says 4.7
> > 
> > Is that how it's supposed to be for the time being?
> 
> /etc/motd is updated via /etc/rc to reflect the booted kernel.
> 
> I'm not sure what you mean by "X login" screen...
> 
> Here's what I see on amd64 -current:
> 
> a8v2:home/rd 3215>grep OpenBSD /var/log/Xorg.0.log | egrep '4\.[78]'
> [490471.594] Build Operating System: OpenBSD 4.8 amd64
> [490471.594] Current Operating System: OpenBSD a8v2.thrush.com 4.8
> GENERIC.MP#240 amd64
> a8v2:home/rd 3216>sysctl kern.version
> kern.version=OpenBSD 4.8-beta (GENERIC.MP) #240: Wed Jul 28 18:21:15
> MDT 2010
> deraadt <at> amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> 
> 
> a8v:snapshots/today 27658#ls -lT amd64/install48.iso
> -r--r--r--  1 rd  wheel  236115968 Jul 28 18:44:00 2010
> amd64/install48.iso a8v:snapshots/today 27659#vnconfig svnd0
> amd64/install48.iso a8v:snapshots/today 27660#mount /dev/svnd0a /mnt
(Continue reading)

Philip Guenther | 1 Aug 2010 05:51
Picon

Re: X login screen

On Sat, Jul 31, 2010 at 7:13 AM, Ed Ahlsen-Girard <eagirard <at> cox.net> wrote:
> Dmesg says 4.8-beta.
>
> Login screen says 4.7
>
> Is that how it's supposed to be for the time being?

Hmm, the summer commit dates for those files have been, in order,
2007/08/03, 2008/07/02, and 2009/06/26.  *Clearly* the trend is to do
it a month earlier each time, so we're now more than 2 months late!

Umm, yeah.  Take a deep breath and calm down.  No, they haven't been
updated for 4.8 yet.  No, that's not the end of the world.  It'll
happen before the xenocara tree is locked for 4.8 and before the final
build and source code cut is made.  The people that handle that have
been doing so for years and many releases.  If you suffer anxiety over
the ability of open source projects to deliver then you should be
talking to your doctor or therapist.

Philip Guenther

Ed Ahlsen-Girard | 1 Aug 2010 14:12
Picon

Re: X login screen

On Sat, 31 Jul 2010 20:51:16 -0700
Philip Guenther <guenther <at> gmail.com> wrote:

> On Sat, Jul 31, 2010 at 7:13 AM, Ed Ahlsen-Girard <eagirard <at> cox.net>
> wrote:
> > Dmesg says 4.8-beta.
> >
> > Login screen says 4.7
> >
> > Is that how it's supposed to be for the time being?
> 
> Hmm, the summer commit dates for those files have been, in order,
> 2007/08/03, 2008/07/02, and 2009/06/26.  *Clearly* the trend is to do
> it a month earlier each time, so we're now more than 2 months late!
> 
> Umm, yeah.  Take a deep breath and calm down.  No, they haven't been
> updated for 4.8 yet.  No, that's not the end of the world.  It'll
> happen before the xenocara tree is locked for 4.8 and before the final
> build and source code cut is made.  The people that handle that have
> been doing so for years and many releases.  If you suffer anxiety over
> the ability of open source projects to deliver then you should be
> talking to your doctor or therapist.
> 
> 
> Philip Guenther

Anxious?  No.  Curious?  Yes.  Thanks for the info.

--

-- 

(Continue reading)

Ryan Flannery | 1 Aug 2010 21:02
Picon
Gravatar

Question about suspend+resume & X11-application buggy-ness

Hello misc,

I have a small X application I use on my laptop that behaves buggy
after some suspend+resumes.  Detailed description below, but first...

HOLY HELL thank you to all the devs who made suspend+resume work!  I
had almost forgotten what it was like to suspend+walk-to-work+resume
and be on my way.  Thank you again.

The application is a small, horizontal stats display-er.   After most
suspend+resume's it continues to work fine.  It always works fine
after the first resume.  After 3-5 resume's, there's a ~50% chance the
display goes "buggy" (details below).  In trying to resolve the
problem, I am curious about the following:

1. Initially, I tried to catch a resume thinking a SIGCONT would be
issued, and manually clear the display and re-draw.  This doesn't
appear to happen.  Out of curiosity, on a resume is any signal issued
to each process?   man'ing and Googling haven't helped.  Digging
through src/sys/kern/* is rewarding, but so far no help.  It seemed
like a SIGCONT would be appropriate, but am I correct in that this is
not the case?

2. Should my application have to do anything specific on a resume?  Of
course this depends on the application, but regarding the X display,
it doesn't immediately appear to me that my application should have to
do anything.

My app is using rudimentary double-buffering: backbuffer is a Pixmap
that's painted black on each call (XFillRectangle), the graphics are
(Continue reading)

CTE | 1 Aug 2010 22:48

restore from tape error sun v120 d240

Hi all,

Running a Sun Fire V120 w/ StorEdge D240 Media Tray.

st0 at scsibus2 targ 4 lun 0: <HP, C5683A, C005> SCSI2 1/sequential
removable

Ran the following for backup:

/sbin/dump -0au -f /dev/nrst0 /dev/sd0a
/sbin/dump -0au -f /dev/nrst0 /dev/sd0k
/sbin/dump -0au -f /dev/nrst0 /dev/sd0d
/sbin/dump -0au -f /dev/nrst0 /dev/sd0f
/sbin/dump -0au -f /dev/nrst0 /dev/sd0g
/sbin/dump -0au -f /dev/nrst0 /dev/sd0h
/sbin/dump -0au -f /dev/nrst0 /dev/sd0j
/sbin/dump -0au -f /dev/nrst0 /dev/sd0i
/sbin/dump -0au -f /dev/nrst0 /dev/sd0e

mt -f /dev/rst0 rewind

When I try to restore I get the following:

# restore -i -f /dev/rst0
restore: tape read error: Input/output error

or

# restore -tvs 1 -f /dev/rst0
restore: tape read error: Input/output error
(Continue reading)

Peter Merritt | 1 Aug 2010 22:49

OBSD 4.7 and Via C7 motherboards problem

I have a firewall that has been running several versions of OpenBSD
successfully, the last being 4.6. After installing 4.7, I could not get
the firewall to pass any traffic from the lan side. We have been having
thunderstorms lately and I thought may be something was wrong with the
nics so I changed the MB our for something similar, another c7
motherboard with 2 nics. I had the same problem, I can ping outside the
network as well as the lan computers from the firewall. Tcpdump shows
the lan traffic hitting the lan side, but no response back to the lan
computers, lan traffic never gets to wan side nic. I put in a very
minimal pf.conf and it still works the same. I'm at a loss what is
wrong. pf.conf and dmess follows. Any ideas would be greatly
appreciated.

Peter
Motherboard #1 Jetway 7f4k1G5D-LF 1.5ghz
Motherboard #2 Jetway J7F4              1.2 Ghz

# sysctl net.inet.ip.forwarding
net.inet.ip.forwarding=1

# cat pf.min
ext_if = "re0"
int_if = "re1"

match out log on egress from  (self)   to any                    tag
EGRESS nat-to ($ext_if:0) port 1024:65535

#pass all
pass out log on $ext_if all
pass out log  on $int_if all
(Continue reading)

Robert | 2 Aug 2010 01:30
Favicon

Re: OBSD 4.7 and Via C7 motherboards problem

On Sun, 1 Aug 2010 13:49:07 -0700
"Peter Merritt" <pwmerritt <at> weirdwater.org> wrote:

> minimal pf.conf and it still works the same. I'm at a loss what is
> wrong. pf.conf and dmess follows. Any ideas would be greatly
> appreciated.

Just some ideas:
* check the routing tables on the client if they point to the firewall
and on the firewall if it points outward (default routes etc.)
* run ifconfig on the firewall to see if the Internet-facing nic is in
the egress group

regards,
Robert

Peter Merritt | 2 Aug 2010 03:43

Re: OBSD 4.7 and Via C7 motherboards problem

Thanks for the help, does look correct to me.
                                    Peter

re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        lladdr 00:30:18:ad:ed:96
        priority: 0
        groups: egress
        media: Ethernet autoselect (100baseTX
full-duplex,rxpause,txpause)
        status: active
        inet6 fe80::230:18ff:fead:ed96%re0 prefixlen 64 scopeid 0x1
        inet XX.171.201.186 netmask 0xfffff800 broadcast XX.171.207.255

re1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        lladdr 00:30:18:ad:ed:97
        priority: 0
        media: Ethernet autoselect (100baseTX
full-duplex,rxpause,txpause)
        status: active
        inet6 fe80::230:18ff:fead:ed97%re1 prefixlen 64 scopeid 0x2
        inet 192.168.0.254 netmask 0xffffff00 broadcast 192.168.0.255

Routing table on windows client:

========================================================================
===
Active Routes:
Network Destination        Netmask          Gateway       Interface
Metric
          0.0.0.0          0.0.0.0    192.168.0.254    192.168.0.11
(Continue reading)

Theo de Raadt | 2 Aug 2010 05:47
Picon
Favicon

Re: Question about suspend+resume & X11-application buggy-ness

> I have a small X application I use on my laptop that behaves buggy
> after some suspend+resumes.  Detailed description below, but first...
> 
> HOLY HELL thank you to all the devs who made suspend+resume work!  I
> had almost forgotten what it was like to suspend+walk-to-work+resume
> and be on my way.  Thank you again.
> 
> The application is a small, horizontal stats display-er.   After most
> suspend+resume's it continues to work fine.  It always works fine
> after the first resume.  After 3-5 resume's, there's a ~50% chance the
> display goes "buggy" (details below).  In trying to resolve the
> problem, I am curious about the following:
> 
> 1. Initially, I tried to catch a resume thinking a SIGCONT would be
> issued, and manually clear the display and re-draw.  This doesn't
> appear to happen.  Out of curiosity, on a resume is any signal issued
> to each process?

Suspend and resumes are completely invisible, except that time makes
an uncomfortable jump forward.  Processes are not made aware in any
way.  There is no API to sense the transition (at this time).

BTW, sending any signal would be violate the rules.  We cannot
re-purpose standardized signals for our own uses.

> 2. Should my application have to do anything specific on a resume?

No.

> My app is using rudimentary double-buffering: backbuffer is a Pixmap
(Continue reading)


Gmane