On November 21, 2014 7:57:22 AM CET, Pete Vickers
wrote:
>Hi,
>
>I suspect this may be the wrong list for this question. However
>although strictly it's a Bourne shell script query, it only seem to act
>up under OpenBSD (for me).
>
>Essentially I have a job which needs to be run periodically. So
21 ноÑб. 2014 г. 10:00 полÑзоваÑÐµÐ»Ñ "Pete Vickers"
напиÑал:
>
> Hi,
>
> I suspect this may be the wrong list for this question. However although
strictly it's a Bourne shell script query, it only seem to act up under
OpenBSD (for me).
>
> Essentially I have a job which need
Hi,
I suspect this may be the wrong list for this question. However although
strictly it's a Bourne shell script query, it only seem to act up under OpenBSD
(for me).
Essentially I have a job which needs to be run periodically. So I have a shell
script to do the necessary commands, and this is
$ dmesg
drm: initializing kernel modesetting (RS480 0x1002:0x5954 0x103C:0x2A26).
radeondrm0: VRAM: 64M 0x1C00 - 0x1FFF (64M used)
radeondrm0: GTT: 512M 0x2000 - 0x3FFF
drm: PCIE GART of 512M enabled (table at 0x02BA5000).
error: [drm:pid0:r
On 20.11.2014 23:40, Austin Gilbert wrote:
On Nov 20, 2014, at 4:08 PM, bodie wrote:
What is the date of your bsd.rd and snapshot? They are new most of
the time daily.
Like eg. now 20-Nov-2014 21:40 7.2M
Perhaps I got burned by cheating? I grabbed install56.iso burned it
to a CD and boot
The tm_mon already adjusts by 1, so the allowed range should be 0 -
11. Since mktime(3) is permissive in what it accepts, I think this
check is correct.
The second part handles the (theoretically valid but essentially
useless) parsing of a configuration file with an ISO 8601 date with
leap second
> Depending on what you configured apcupsd to do and what sysctl
> exposes, you may be able to create equivalent behavior using
> sensorsd(8). There's a brief overview in the comments of the undeadly
> article below, to serve as starting point for your needs:
>
> http://undeadly.org/cgi?action=art
On Thu, Nov 20, 2014 at 11:03 AM, Steven Surdock
wrote:
> I just upgrade from 5.5 to 5.6 on i386 and apcupsd won't recognize my UPS
> plugged into a USB port. On 5.5 the UPS was attached to ugen0 but on 5.6 it
> say uhidev0. Apcupsd mentions that the uhidev0 device type won't work. I
> see t
Well, I'm not sure what happened but all is well now...
# drill @127.0.0.1 ftp.nluug.nl
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 9907
;; flags: qr rd ra ; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 3
;; QUESTION SECTION:
;; ftp.nluug.nl.IN A
;; ANSWER SE
On 11/20/14 19:24, trondd wrote:
When you sent this, I had a new UPS in the mail on its way to me that I
specifically bought to be compatible with OBSD.
I, too, have the same issue.
Tim.
On Thu, Nov 20, 2014 at 11:03 AM, Steven Surdock <
ssurd...@engineered-net.com> wrote:
I just upgrade fro
Works for me :)
root@rel56[~] echo $PKG_PATH
http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/
root@rel56[~] pkg_info -Q mosh
mosh-1.2.4p1
root@rel56[~] dig ftp.nluug.nl
; <<>> DiG 9.4.2-P2 <<>> ftp.nluug.nl
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NO
I am able to access the mirror via a web browser, however there may be
something wrong with my dns:
# drill @127.0.0.1 http://ftp.nluug.nl
;; ->>HEADER<<- opcode: QUERY, rcode: NXDOMAIN, id: 55283
;; flags: qr rd ra ; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;; http:/
Sent: Thursday, November 20, 2014 at 8:06 PM
From: "John Smith"
To: misc@openbsd.org
Subject: No address associated with PKG_PATH mirror
Hello, I get the following error when using any of the pkg_* commands:$
echo $PKG_PATH
http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/ $ pkg_info -Q
mos
Hello, I get the following error when using any of the pkg_* commands:$
echo $PKG_PATH
http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/ $ pkg_info -Q
mosh
Error from http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/
ftp: ftp.nluug.nl: no address associated with
namehttp://ftp.nluug.nl/pu
When you sent this, I had a new UPS in the mail on its way to me that I
specifically bought to be compatible with OBSD.
I, too, have the same issue.
Tim.
On Thu, Nov 20, 2014 at 11:03 AM, Steven Surdock <
ssurd...@engineered-net.com> wrote:
> I just upgrade from 5.5 to 5.6 on i386 and apcupsd w
On 20/11/14(Thu) 15:49, Austin Gilbert wrote:
> On Nov 20, 2014, at 2:33 PM, Chris Cappuccio wrote:
>
> > Austin Gilbert [austin.gilb...@gmail.com] wrote:
> >>> On Nov 20, 2014, at 1:27 PM, Otto Moerbeek wrote:
> >>>
> On Thu, Nov 20, 2014 at 12:37:58PM -0600, Austin Gilbert wrote:
>
On Nov 20, 2014, at 4:08 PM, bodie wrote:
>
> What is the date of your bsd.rd and snapshot? They are new most of the time
> daily.
> Like eg. now 20-Nov-2014 21:407.2M
Perhaps I got burned by cheating? I grabbed install56.iso burned it to a CD and
booted that. I didn’t verify the bsd.
Austin Gilbert [austin.gilb...@gmail.com] wrote:
>
> I saw the news about the USB 3 driver in current and was very excited about
> that. The first thing I did was grab a snapshot. Sadly, the snapshot BSD.rd
> behaves the same as the stable 5.6 release (as of the 16th).
xhci is commented out on
On Thu, Nov 20, 2014 at 5:02 PM, Fred wrote:
> On 11/20/14 21:47, sven falempin wrote:
>>
>> How an openBSD dev is reading the /dev/cua when the cua is a ksh shall
>> on the other side ?
>> stty is obscure to me,
>>
>> I may install minicom or screen but how do you do that ?
>>
>
> cu(1)?
>
I di
On 20.11.2014 22:49, Austin Gilbert wrote:
On Nov 20, 2014, at 2:33 PM, Chris Cappuccio
wrote:
Austin Gilbert [austin.gilb...@gmail.com] wrote:
On Nov 20, 2014, at 1:27 PM, Otto Moerbeek wrote:
On Thu, Nov 20, 2014 at 12:37:58PM -0600, Austin Gilbert wrote:
I have an amd64 based Mac Mini
On 11/20/14 21:47, sven falempin wrote:
How an openBSD dev is reading the /dev/cua when the cua is a ksh shall
on the other side ?
stty is obscure to me,
I may install minicom or screen but how do you do that ?
cu(1)?
On Nov 20, 2014, at 2:33 PM, Chris Cappuccio wrote:
> Austin Gilbert [austin.gilb...@gmail.com] wrote:
>>> On Nov 20, 2014, at 1:27 PM, Otto Moerbeek wrote:
>>>
On Thu, Nov 20, 2014 at 12:37:58PM -0600, Austin Gilbert wrote:
I have an amd64 based Mac Mini which I would like to r
How an openBSD dev is reading the /dev/cua when the cua is a ksh shall
on the other side ?
stty is obscure to me,
I may install minicom or screen but how do you do that ?
--
-
() a
On Thu, Nov 20, 2014 at 3:57 PM, Alan McKay wrote:
> peer1 = '( "ping -q -c 1 -w 1 10.1.1.1 > /dev/null 2>&1" every 10)'
> peer2 = '( "ping -q -c 1 -w 1 10.20.1.1 > /dev/null 2>&1" every 10)'
At present I am thinking that my problem would go away if I changed my
pings to "-c 3 -w 3" instead of 1s
Hi folks,
After a 5.1 to 5.5 upgrade on a redundant firewall pair, every once in
a while my FW2 (backup) promotes itself and then immediately demotes
itself again. Which I find very odd because it is doing so based on
pinging its peer every 10 seconds, and so the value of that boolean
should only
On 20 November 2014 20:13:42 GMT+00:00, Austin Gilbert
wrote:
>I have no serial ports I can redirect the console to.
>
>I gather I'm just dead in the water then. I assume the normal OS
>developer
>would debug under friendlier conditions. ;(
I was going to suggest yaifo, but it looks like it's d
Austin Gilbert [austin.gilb...@gmail.com] wrote:
> > On Nov 20, 2014, at 1:27 PM, Otto Moerbeek wrote:
> >
> >> On Thu, Nov 20, 2014 at 12:37:58PM -0600, Austin Gilbert wrote:
> >>
> >> I have an amd64 based Mac Mini which I would like to run OpenBSD on.
> >>
> >> With OpenBSD 5.6, the USB keyboar
On 2014-11-20 18:37, Austin Gilbert wrote:
I have an amd64 based Mac Mini which I would like to run OpenBSD on.
With OpenBSD 5.6, the USB keyboard works at the “boot>” prompt, but
not after booting BSD.rd. The Mac Mini has USB 3 ports, I thought
perhaps the newly minted USB 3 support in current
Austin Gilbert said:
> Is there anything I can do at the “boot>” prompt to try
> disabling/enabling different device drivers for the USB ports so the
> keyboard will work under BSD.rd?
Your best bet would probably be to install OpenBSD in unattended mode[1]
and get dmesg via ssh. That said, you
> On Nov 20, 2014, at 1:27 PM, Otto Moerbeek wrote:
>
>> On Thu, Nov 20, 2014 at 12:37:58PM -0600, Austin Gilbert wrote:
>>
>> I have an amd64 based Mac Mini which I would like to run OpenBSD on.
>>
>> With OpenBSD 5.6, the USB keyboard works at the ?boot>? prompt, but not
after booting BSD.rd. Th
On Thu, Nov 20, 2014 at 12:37:58PM -0600, Austin Gilbert wrote:
> I have an amd64 based Mac Mini which I would like to run OpenBSD on.
>
> With OpenBSD 5.6, the USB keyboard works at the ?boot>? prompt, but not after
> booting BSD.rd. The Mac Mini has USB 3 ports, I thought perhaps the newly
>
I have an amd64 based Mac Mini which I would like to run OpenBSD on.
With OpenBSD 5.6, the USB keyboard works at the “boot>” prompt, but not after
booting BSD.rd. The Mac Mini has USB 3 ports, I thought perhaps the newly
minted USB 3 support in current could help, but the nightly snapshot behav
On Thu, Nov 20, 2014 at 18:07, Luca Ferrari wrote:
> Hi all,
> this may sound trivial, in the case please insult me, but I've a
> little doubt about disk devices.
> In the OpenBSD way there are two devices: a block one and a character
> one (and I believe this is the rightmost way). You do low leve
On 20.11.2014 18:07, Luca Ferrari wrote:
Hi all,
this may sound trivial, in the case please insult me, but I've a
little doubt about disk devices.
In the OpenBSD way there are two devices: a block one and a character
one (and I believe this is the rightmost way). You do low level
operations on th
Hi all,
this may sound trivial, in the case please insult me, but I've a
little doubt about disk devices.
In the OpenBSD way there are two devices: a block one and a character
one (and I believe this is the rightmost way). You do low level
operations on the raw device and mount the block device.
O
On Thu, 20 Nov 2014 16:57:08 +0100, Janne Johansson
wrote:
> Please don't mix "you" and "we" in the text on who is doing what.
>
Indeed, thanks.
A new version with the wording more consistent with the general tone
(I hope).
Index: faq14.html
I just upgrade from 5.5 to 5.6 on i386 and apcupsd won't recognize my UPS
plugged into a USB port. On 5.5 the UPS was attached to ugen0 but on 5.6 it
say uhidev0. Apcupsd mentions that the uhidev0 device type won't work. I see
that I can get some info from sensord (which is cool). Any sugges
Please don't mix "you" and "we" in the text on who is doing what.
2014-11-20 16:34 GMT+01:00 Daniel Jakots :
> On Sun, 16 Nov 2014 20:09:35 +0100, Daniel Jakots
> wrote:
>
> > I wanted to add some content to FAQ14
>
> Here it is.
>
> This can be useful for people who want to encrypt only their
On Sun, 16 Nov 2014 20:09:35 +0100, Daniel Jakots
wrote:
> I wanted to add some content to FAQ14
Here it is.
This can be useful for people who want to encrypt only their /home or
people who want to automatically mount another disk encrypted at boot
(me).
Cheers,
Daniel
Index: faq14.html
=
On 11/19/14 22:27, Nick Holland wrote:
On 11/19/14 19:38, Dutch Ingraham wrote:
On 11/19/14 18:18, Bertrand Janin wrote:
Dutch Ingraham wrote :
Just asking for a sanity check. I tried installing 5.6 from CD on a
WD1600AAJS HDD and was presented with "Available disks are: none." This
seems to
Hi all,
is anyone by anychance working on this LAN device support in OpenBSD?
Not sure how much portable and applicable is eg. code from FreeBSD for
that.
$ sudo lspci -vx -s 07:00.0
07:00.0 Ethernet controller: Qualcomm Atheros QCA8171 Gigabit Ethernet
(rev 10)
Subsystem: Lenovo De
On 19/11/14(Wed) 11:39, Scott Bonds wrote:
> > I don't know what you mean by "unreliable" nor which snapshot you
> > tried, that sad for me, 'cause I cannot learn from your experience :/
>
> Sorry about that Martin, I'll try to be more helpful by providing more
> details. The snapshot I tried and
Folks,
just updated to latest snapshot (Nov 20):
root@poseidon:[~]> uname -a
OpenBSD poseidon.atlantide.net 5.6 GENERIC.MP#579 amd64
and noticed that lease declarations in /etc/dhclient.conf no longer
work:
root@poseidon:[~]> cat /etc/dhclient.conf
# $OpenBSD: dhclient.conf,v 1.2 2011/04/04 11
43 matches
Mail list logo
