You could use tmux, run $ sleep 5; zzz;
then detach from tmux and ^D to logout before system suspends.
On Wed, May 7, 2014 at 8:44 PM, Alessandro DE LAURENZIS <
just22@gmail.com> wrote:
> Hi Tristan,
>
> No, I'm trying to lock the wscons, not an X session...
>
> Cheers
>
> On 7 May 2014 22:4
Hi Shawn,
This report needs more information.
First, could you upgrade to -current and see if the behaviour is
preserved?
Second, please share the acpidump on that machine, the apm performance
adjustment mode, the present fans and their status when this happens.
Thanks for the report,
Paul
Hi Tristan,
No, I'm trying to lock the wscons, not an X session...
Cheers
On 7 May 2014 22:42:35 CEST, Tristan PILAT wrote:
>> On Mon, Apr 21, 2014 at 4:51 PM, Alessandro DE LAURENZIS <
>> just22@gmail.com> wrote:
>>
>> > Hello,
>> >
>> > I google-ed a lot, but it seems that there is no tri
> -Current is incredibly stable. Commits that break the tree are
> fairly rare and get repaired quickly. Before using a -current
> system in something important you want to test it, but you
> want to test a stock -stable system before using it for your
> applications, too. Most of my systems tha
On 05/07/14 19:01, Stuart Henderson wrote:
My advice is: stick to releases for now on important systems that
you mustn't break, but also setup on a spare machine or VM that you
don't mind breaking from time to time, use base os + package
snapshots, maybe play with compiling a few things yourself
OpenBSDs userland is base qualified code such as nginx and extra
packages are kept separate in /usr/local.
For both snapshots and especially for building yourself follow
www.openbsd.org/faq/current.html
For building from source; man release is brill.
Sync issues with packages built after upgrade
>My advice is: stick to releases for now on important systems that
>you mustn't break, but also setup on a spare machine or VM that you
>don't mind breaking from time to time, use base os + package
>snapshots, maybe play with compiling a few things yourself -
>basically play around and find out wha
On Tue, May 6, 2014 at 1:09 PM, Daniel Melameth wrote:
> On Tue, May 6, 2014 at 9:55 AM, Marko Cupać wrote:
>> I have just upgraded (actually reinstalled from scratch) one of my
>> firewalls to 5.5 release, and I have noticed that 'systat queues' no
>> longer shows P/S and B/S values. pftop does
My advice is: stick to releases for now on important systems that
you mustn't break, but also setup on a spare machine or VM that you
don't mind breaking from time to time, use base os + package
snapshots, maybe play with compiling a few things yourself -
basically play around and find out what wor
On 05/07/14 21:41, Manuel Pages wrote:
1. Know your mirror:
A person who wants to do that should find out the
policies of making snapshots for a particular mirror.
Depending on the architecture, mostly once a day. Which is enough!
I mean the OpenBSD userland. Package snapshots take a little long
On Wed, May 07, 2014 at 10:41:49PM +0300, Manuel Pages wrote:
> As Mr. Grosse points out (and I was originally aware of it),
> using snapshot userspace provides only an
> approximation of current userspace without any
> guarantees that snapshots
> are "up to date enough".
To be clear, I was speak
> On Mon, Apr 21, 2014 at 4:51 PM, Alessandro DE LAURENZIS <
> just22@gmail.com> wrote:
>
> > Hello,
> >
> > I google-ed a lot, but it seems that there is no trivial solution to
> > this point.
> >
> > I extensively use console (and tmux), ending up with a lot of
> > simultaneously open shells;
On Fri, May 2, 2014 at 1:27 AM, LEVAI Daniel wrote:
> I've recently upgraded one of my systems to 55 from 54 (btw, for me, the
> most painful upgrade since ~3.9; I don't know what happened but
> everything was against me), and one of the obstacles was the openldap
> upgrade. I was using openldap-
Alright, thanks for being ever-so-helpful.
I'll do my best to compile my understanding of the system
taking into account the response that is accumulated here.
As Mr. Grosse points out (and I was originally aware of it),
using snapshot userspace provides only an
approximation of current userspace
maybe related?
http://marc.info/?l=openbsd-cvs&m=138183876907016&w=2
I also stumbled over an old nawk short after, no clue if that could have
been invoked.
On 07.05.2014 04:21, Stuart Henderson wrote:
What arch is this Daniel? I've done multiple 5.4->5.5 upgrades
with OpenLDAP/bdb without nee
> When I run X, I get the following result (from Xorg.0.log):
[...]
> [ 42880.713] (II) intel: Driver for Intel(R) HD Graphics: 2000-5000
> [ 42880.713] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100
> [ 42880.713] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200
> [ 42880.713]
Donovan Watteau [tso...@gmail.com] wrote:
>
> Yes, but I want to explicitly configure flow control, not speed or
> duplex. AFAIK this can't be forced with mediaopt. And forcing
> speed/duplex doesn't have any effect on the status of flow control.
Try it.
2014-05-07 18:28 GMT+02:00 Chris Cappuccio :
> Donovan Watteau [tso...@gmail.com] wrote:
>> Hi,
>>
>> Is there a way to force the disabling of flow control on em(4)?
>>
>> Henning said (http://marc.info/?l=openbsd-misc&m=123003276308084&w=2):
>> > flow control is enabled on openbsd whenever the pee
On Wed, May 07, 2014 at 02:11:09AM +, Stuart Henderson wrote:
> On 2014-05-02, Thorsten Bonck wrote:
> > On Fri, May 02, 2014 at 08:14:40PM +, Peter J. Philipp wrote:
> >> On Fri, May 02, 2014 at 09:14:16PM +0200, thors...@bonck.net wrote:
> >> > > maybe you could try to put pppoe0 on rl0,
Donovan Watteau [tso...@gmail.com] wrote:
> Hi,
>
> Is there a way to force the disabling of flow control on em(4)?
>
> Henning said (http://marc.info/?l=openbsd-misc&m=123003276308084&w=2):
> > flow control is enabled on openbsd whenever the peer supports it; done
> > in the autonegotiation phas
On Wed, May 07, 2014 at 18:51, Manuel Pages wrote:
> Dear list,
> Using manuals I have figured out how to follow
> -current by means of buliding kernel and rebuilding
> userspace. Also I can see that with a known amount
> of caution it's possiblle to use snapshots with -current
> and update userspa
Hi Manuel,
Manuel Pages wrote on Wed, May 07, 2014 at 06:51:00PM +0300:
> Using manuals I have figured out how to follow
> -current by means of buliding kernel and rebuilding
> userspace.
There is usually no need to do that, unless you want to do
bleeding edge base system development and the lat
On 2014-05-07 11:52, Manuel Pages wrote:
Errata: ``"snapshot" pigs'' should read
``"snapshot" pkgs''.
Please blame automatic completion.
On May 7, 2014 6:51 PM, "Manuel Pages"
wrote:
Dear list,
Using manuals I have figured out how to follow
-current by means of buliding kernel and rebuildin
Errata: ``"snapshot" pigs'' should read
``"snapshot" pkgs''.
Please blame automatic completion.
On May 7, 2014 6:51 PM, "Manuel Pages" wrote:
> Dear list,
> Using manuals I have figured out how to follow
> -current by means of buliding kernel and rebuilding
> userspace. Also I can see that with
I just upgraded a friend's somewhat geriatric i386 box from 5.4-release
to 5.5-release. On 5.5 the console is getting spammed with "acpitz0:
_AL0[0] _PR0 failed". This didn't happen with 5.4, or for that matter,
any previous version of OpenBSD that's been on it that I can remember.
dmesg follows:
Dear list,
Using manuals I have figured out how to follow
-current by means of buliding kernel and rebuilding
userspace. Also I can see that with a known amount
of caution it's possiblle to use snapshots with -current
and update userspace with pkg_add -u.
What escapes my mind though is how do sets
On Wed, May 7, 2014 at 4:44 PM, Manuel Pages wrote:
> Rebuilding kernel helped.
> Now I run -current MP kernel and everything works like a charm.
> Much love and gratefulness to you, Tomash.
>
Happy to help. Welcome in OpenBSD where 99% of time everything works and
fault is on the other end :-)
(still did not receive the 5.5 cd btw)
I built a bsd.rd with a bigger ramdisk, MINIROOT is 35840 (0x8C00).
i do make bsd.rd and everythings build fine, but the kernel does not boot
i have just time to see the first number of loading [x]
and instant reboot, i have no COM output on this machin
Rebuilding kernel helped.
Now I run -current MP kernel and everything works like a charm.
Much love and gratefulness to you, Tomash.
I see you compile the kernel by yourself, GENERIC.MP is what you want.
- Ben
On 05/07/14 15:40, Manuel Pages wrote:
Dear Tomaš,
thank you so much for your support, thanks to you I felt encouraged to
finally
update my BIOS. It solved the driver problem (and by the looks of it,
improved
fan perf
On sze, máj 07, 2014 at 02:21:38 +, Stuart Henderson wrote:
> What arch is this Daniel? I've done multiple 5.4->5.5 upgrades
> with OpenLDAP/bdb without need for additional steps, but they were
> all on amd64.
[...]
Oh, this was i386.
Daniel
--
LÉVAI Dániel
PGP key ID = 0x83B63A8F
Key fing
On 7 May 2014 04:11, Stuart Henderson wrote:
> On 2014-05-02, Thorsten Bonck wrote:
>> On Fri, May 02, 2014 at 08:14:40PM +, Peter J. Philipp wrote:
>>> On Fri, May 02, 2014 at 09:14:16PM +0200, thors...@bonck.net wrote:
>>> > > maybe you could try to put pppoe0 on rl0, untag vlan10 on switch
Dear Tomaš,
thank you so much for your support, thanks to you I felt encouraged to
finally
update my BIOS. It solved the driver problem (and by the looks of it,
improved
fan performance, but it's handwaving); however as far as I can tell from
dmesg
and system performance, only one core is used sti
On Tue, 6 May 2014 13:09:25 -0600
Daniel Melameth wrote:
> I believe this has been resolved in
> http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin/systat/pftop.c.diff?r1=1.24;r2=1.25,
> but I have not yet confirmed.
I have also noticed that output of 'systat queues' shows much larger
number of P
Hi,
Is there a way to force the disabling of flow control on em(4)?
Henning said (http://marc.info/?l=openbsd-misc&m=123003276308084&w=2):
> flow control is enabled on openbsd whenever the peer supports it; done
> in the autonegotiation phase. there is no button to turn it off. why
> should there
On Wed, May 7, 2014 at 2:00 PM, Manuel Pages wrote:
> Wow, I didn't catch it. It's kinda shocking.
> Is there any data bank regarding Thinkpads, it's BIOS and OpenBSD?
>
Yes, in my head and on Internet :-)
1) Checked your dmesg
2) Saw issue with cpu
3) Checked BIOS in your dmesg
4) Went to
http:
Wow, I didn't catch it. It's kinda shocking.
Is there any data bank regarding Thinkpads, it's BIOS and OpenBSD?
On Wed, May 7, 2014 at 1:43 PM, Manuel Pages wrote:
> I'm so sorry!
> http://f.nn.lv/n5/7c/ii/dmesg.full
>
Thx
First of all I will be focusing on why you can't see more then 1 core out
of your CPU. 5 BIOS updates are missing on your computer. Maybe OpenBSD
will not be ok about some of them or wi
Em 07-05-2014 08:36, Janne Johansson escreveu:
> Could be that the standard for tar specifies a max length and that gnu tar
> either uses some extension for longer names, or it just doesn't care.
>
>
>
> 2014-05-07 11:05 GMT+02:00 Robert Connolly :
>
>> Why does BSD tar complain about long file nam
The exact error message is always helpfull.
Nevertheless, see "man 1 pax" and search for "ustar"
GNU tar uses a "extended" tar format to store longer pathnames.
Ben
On 05/07/14 11:05, Robert Connolly wrote:
Why does BSD tar complain about long file names, and GNU does not?
I'm so sorry!
http://f.nn.lv/n5/7c/ii/dmesg.full
On Wed, May 7, 2014 at 2:36 PM, Tomas Bodzar wrote:
>
>
>
> On Wed, May 7, 2014 at 1:23 PM, Manuel Pages
> wrote:
>
>> Hello list, first post here \o/
>>
>> The question is about drivers for "Intel HD Graphics 3000" rev 0x09
>> (not a hybrid wit
On Wed, May 7, 2014 at 1:23 PM, Manuel Pages wrote:
> Hello list, first post here \o/
>
> The question is about drivers for "Intel HD Graphics 3000" rev 0x09
> (not a hybrid with some nVIDIA nonsense).
>
> When I run X, I get the following result (from Xorg.0.log):
>
> ```
> [ 42880.697] (II) Load
Could be that the standard for tar specifies a max length and that gnu tar
either uses some extension for longer names, or it just doesn't care.
2014-05-07 11:05 GMT+02:00 Robert Connolly :
> Why does BSD tar complain about long file names, and GNU does not?
>
> I'm running amd64.
>
> Thanks
>
Hello list, first post here \o/
The question is about drivers for "Intel HD Graphics 3000" rev 0x09
(not a hybrid with some nVIDIA nonsense).
When I run X, I get the following result (from Xorg.0.log):
```
[ 42880.697] (II) LoadModule: "intel"
[ 42880.698] (II) Loading /usr/X11R6/lib/modules/dri
On 05/07/2014 12:41 PM, Marko Cupać wrote:
> On Wed, 07 May 2014 12:23:12 +0200
> Blaise Hizded wrote:
>
>> As Henning Brauer said, the rewrite are applied immediately. So the
>> first match rule will rewrite IP from the packet and the second match
>> will be evaluated on the new IP rewritten.
>>
On Wed, 07 May 2014 12:23:12 +0200
Blaise Hizded wrote:
> As Henning Brauer said, the rewrite are applied immediately. So the
> first match rule will rewrite IP from the packet and the second match
> will be evaluated on the new IP rewritten.
> There is no win, the packet is passed thru all match
On 05/07/2014 12:17 PM, Marko Cupać wrote:
> Thank you for reply.
>
> I have been trying some trial and error tests, and I came to similar
> conclusion, but I would like to understand the design idea behind match
> rule.
>
> Who wins, the first or the last matching rule? Or do they all stick
> toge
Thank you for reply.
I have been trying some trial and error tests, and I came to similar
conclusion, but I would like to understand the design idea behind match
rule.
Who wins, the first or the last matching rule? Or do they all stick
together? What if they are conflicting, like in this case?
T
Why does BSD tar complain about long file names, and GNU does not?
I'm running amd64.
Thanks
49 matches
Mail list logo
