16:01 schreef Philipp Buehler
:
>
> Am 29.12.2022 15:40 schrieb Jurjen Oskam:
> > From the host dmesg I noticed the following line:
>
> It has been this way since day-1 of -B -- unclear if you want to call
> it expected, feature or bug :-)
>
> Noticed this early on the v
Hi,
Today I first started to use vmm(4) virtual machines (on amd64 7.2 with all
syspatches applied, dmesg of the host is below). From what I've seen so far
I'm quite happy with it, it's very elegant and straightforward how all the
components work together.
One thing I noticed is that when a VM
Hi,
On my home router, since a year or two I've occasionally seen watchdog
timeouts on re0 (which is connected with 1Gbps to a Cisco switch):
re0: watchdog timeout
They weren't frequent, but when they occurred it was always under high-ish
throughput (300-400 Mbps). Yesterday however, one
s for: "Filesystem operations on a file that is
mapped for shared modifications are unpredictable except after an
msync()."
Thanks for pointing me in this direction, it resulted in an interesting
half hour of reading web pages about mmap on several OSes. :)
Regards,
Jurjen Oskam
sult in messages like this? (Not counting situations where softupdates are
enabled)
Regards,
Jurjen Oskam
On Thu, Jul 09, 2020 at 06:38:01AM +, mabi wrote:
> I just upgraded one of my vmd virtual machine from OpenBSD 6.6 to 6.7 using
> sysupgrade and noticed a new msyscall error message I have never seen before
> during reboot as you can see below:
>
> ...
> preserving editor files.
> starting
On Fri, Jun 05, 2020 at 10:52:38AM +0200, Marek Benc wrote:
> There's been some changes in the OpenBSD port of smartmontools,
> tools for working with S.M.A.R.T diagnostic of hard drives and SSDs,
> the platform-specific code was modernized, so it would be quite useful
> if people could test
ink you gave describes a good method of doing that, and nowadays it's
easier because rdsetroot is part of the base system so you don't even need
to build it.
Regards,
Jurjen Oskam
-2.7.9 and python-3.6.8p0.
This caused me to realize I had forgotten to update my packages after doing
the sysupgrade... A quick "pkg_add -u" later and my problem was gone. D'oh!
So, moral of the story: don't forget to update your packages after a
sysupgrade.
Regards,
Jurjen Oskam
On Thu, Oct 31, 2019 at 08:01:25AM -, Stuart Henderson wrote:
> On 2019-10-30, Jurjen Oskam wrote:
> >
> > All snapshots I tried up to and including this point did not show the
> > problem:
> > OpenBSD 6.6-beta (GENERIC.MP) #202: Mon Aug 12 11:01:21 MDT 2019
&g
On Tue, Oct 29, 2019 at 01:25:10PM -0700, Mike Larkin wrote:
> On Tue, Oct 29, 2019 at 09:16:42PM +0100, Jurjen Oskam wrote:
[...]
> > uvn_flush: obj=0xfd813ee78298, offset=0x33f. error during pageout.
> > uvn_flush: WARNING: changes to page may be lost!
> > uvn_f
at ppb33 bus 34
isa0 at pcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
wsmouse0 at pms0 mux 0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
vscsi0 at root
scsibus2 at vscsi0: 256 targets
softraid0 at root
scsibus3 at softraid0: 256 targets
root on sd0a (afa24b55e438df24.a) swap on sd0b dump on sd0b
Regards,
Jurjen Oskam
-K option (in which case
it's certain that policy checking never happens).
But now I know better. :)
Thanks,
Jurjen
2017-03-20 9:33 GMT+01:00 Jurjen Oskam <jur...@osk.am>:
> Hi Philipp,
>
> Thank you - this was exactly what I was missing. I have now gotten it to
> wor
HM"
HMAC_SHA
#
I'm likely to miss something obvious here. Why is isakmpd negotiating
HMAC_SHA2_256 instead of HMAC_SHA, as it is configured to do? Any hints
would be much appreciated.
Thanks,
Jurjen Oskam
Stuart Henderson stu at spacehopper.org writes:
On 2014-01-10, Jurjen Oskam jurjen at osk.am wrote:
Philip Guenther guenther at gmail.com writes:
Oh, you're running 5.4-stable? I thought you were running -current
and was worried there was another hang in there. I'm now 99% sure
Philip Guenther guenther at gmail.com writes:
On Thu, Jan 9, 2014 at 8:20 AM, Jurjen Oskam jurjen at osk.am wrote:
OK, I've got it to work using a /dev/cua* device. I still have problems
with processes not exiting though. Since this machine has real com
ports, I also made a cable
at all, and interrupting a read is no
problem.
I'm sorry, but I don't know which hang you fixed in October. With this
information, do you think it's the same hang?
Thanks,
Jurjen Oskam
is to reboot the system.
Am I doing anything wrong here? I expected the process to just exit and
release cua01 after I killed it.
Regards,
Jurjen Oskam
:56PM0:00.00 stty -f
/dev/ttyU0
joskam 22302 0.0 0.0 236 176 p1- IE 3:54PM0:00.00 (cat)
I did read the manual pages, but I probably overlooked something.
How can I set the correct parameters on /dev/ttyU0 and read from it?
Thank you,
Jurjen Oskam
Full dmesg:
OpenBSD 5.4
(0x12f6694a1d70,0O_RDONLY)
15860 perl 1389125426.222465 NAMI /dev/ttyU0
15860 perl 1389125451.261414 PSIG SIGINT SIG_DFL
Again, open() doesn't seem to return.
Am I doing something wrong here?
Regards,
Jurjen Oskam
the addresses of the
ISP's resolving name servers. I just used chflags uchg /etc/resolv.conf,
until I properly read the manual and discovered how I can use the supersede
option in dhclient.conf:
supersede domain-name-servers 192.168.1.1;
supersede domain-name ;
Regards,
--
Jurjen Oskam
Savage's
. It wasn't hard to find over here, and not expensive. I just
visited a reputable Web shop, searched for EH417AA and that was basically
it.
Regards,
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad, you'll get it bad.
measure:
$ TMOUT=600
$ readonly TMOUT
$ exec perl -e 'delete $ENV{TMOUT} ; exec /bin/ksh;'
$ echo $TMOUT
0
$
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad, you'll get it bad.
0x290/8: W83627DHG
lm1 detached
mtrr: Pentium Pro MTRR support
softraid0 at root
root on sd1a swap on sd1b dump on sd1b
WARNING: / was not properly unmounted
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad, you'll get it bad.
response times. :)
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad, you'll get it bad.
it: in that case
the dmesg doesn't survive the reboot...
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad, you'll get it bad.
this route.
Could someone point me in the right direction? I'd like to understand the
effects of setting (or not setting) such a route...
Regards,
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad, you'll get it bad.
wsdisplay0
pcppi0 at isa0 port 0x61
midi0 at pcppi0: PC speaker
spkr0 at pcppi0
wbsio0 at isa0 port 0x2e/2: W83627DHG rev 0x25
lm2 at wbsio0 port 0x290/8: W83627DHG
lm1 detached
mtrr: Pentium Pro MTRR support
softraid0 at root
root on sd1a swap on sd1b dump on sd1b
Thank you,
--
Jurjen Oskam
the boot.conf of the two
disks to the autoconfig RAIDframe enabled kernel, which will then load from
one of the normal partitions, but once started will use the root filesystem
in the RAID partition.
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad, you'll get it bad.
softraid0 at root
root on sd1a swap on sd1b dump on sd1b
Thanks,
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad, you'll get it bad.
reminder :-)
Sure, I've just sent in my report and it's now registered under number
6269. Thanks for the quick reply, and if there's something I can do just
let me know.
Regards,
--
Jurjen Oskam
in-place reconstruction on
row 0 col 0 - spare at row 0 col 0.
Quiescence reached...
Thanks,
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad, you'll get it bad.
since
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad, you'll get it bad.
.
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad, you'll get it bad.
://www.nabble.com/Memory-problems-on-4.5-td23901874.html
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad, you'll get it bad.
INUM MODE R/WSZ|DV
no luck
Are you sure you haven't mounted anything else somewhere in the filesystem
you're trying to unmount? You can't unmount a filesystem if a directory
in that filesystem is used as a mount point for another filesystem.
--
Jurjen Oskam
Savage's Law of Expediency
to fire when any single command
of a set of piped commands exits non-zero.
(If there's a better way of doing things, I'd love to hear about it...)
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad, you'll get it bad.
swapmount: no device
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad, you'll get it bad.
at wbsio0 port 0x290/8: W83697HF
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
Kernelized RAIDframe activated
raid0 at root: (RAID Level 1) total number of sectors is 154534656 (75456 MB)
as root
softraid0 at root
swapmount: no device
--
Jurjen Oskam
Savage's
head, 18 sec
Kernelized RAIDframe activated
raid0 at root: (RAID Level 1) total number of sectors is 154534656 (75456 MB)
as root
softraid0 at root
swapmount: no device
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad, you'll get it bad.
: MAC/BBP RT2561C, RF RT2527
Try attaching (if you haven't already) a high quality external antenna.
This made a world of difference in my case.
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad, you'll get it bad.
dependent?
Thanks,
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad, you'll get it bad.
On Fri, Apr 18, 2008 at 04:21:08PM +0200, Almir Karic wrote:
On Fri, Apr 18, 2008 at 3:20 PM, Jurjen Oskam [EMAIL PROTECTED] wrote:
So ps does show FOO, *and* it shows the value of FOO changing after
ten seconds.
what is so weird about it? you set your program an env var via env(1
. You'll not be seeing me near any C code with
any significant value anytime soon. :)
But thanks for the tip.
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad, you'll get it bad.
seconds
without soft updates, and 2 seconds with soft updates.
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad, you'll get it bad.
,
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad, you'll get it bad.
one on another location on wd0 though, it might come
in handy later.
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad, you'll get it bad.
Mini, 0.1 SCSI2 0/direct
removable
sd1: 244MB, 31 cyl, 255 head, 63 sec, 512 bytes/sec, 501759 sec total
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad, you'll get it bad.
mode!
ral0 at pci0 dev 11 function 0 Ralink RT2560 rev 0x01: irq 11, address
00:0c:f6:26:0d:b2
ral0: MAC/BBP RT2560 (rev 0x04), RF RT2525
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad, you'll get it bad.
location. After that, it worked great.
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad, you'll get it bad.
when the signal is good, the internet connection is weak or drops.
This is easily shown using ping, especially with the -f option.
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad, you'll get it bad.
with ifconfig and netstart ral0. Does this sound
familiar to anyone? Should I gather more data so I can create a proper
report?
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad, you'll get it bad.
On Wed, Jul 18, 2007 at 04:53:35PM +0300, Alexey Suslikov wrote:
Jurjen Oskam wrote:
At home, I have a wireless access point which is directly connected to rl1.
To eliminate the access point, I put a wireless PCI card in the machine
sec
Kernelized RAIDframe activated
raid0 (root): (RAID Level 1) total number of sectors is 154534656 (75456 MB)
as root
dkcsum: wd0 matches BIOS drive 0x80
dkcsum: wd1 matches BIOS drive 0x81
swapmount: no device
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad, you'll get
) total number of sectors is 154534656 (75456 MB)
as root
dkcsum: wd0 matches BIOS drive 0x80
dkcsum: wd1 matches BIOS drive 0x81
swapmount: no device
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad, you'll get it bad.
0x00403276 in main (argc=2, argv=0x41d3c0) at
/usr/src/usr.sbin/tcpdump/tcpdump.c:485
(gdb)
I made the resulting file of tcpdump -p -ienc0 -w enc0.dump available at
http://www.stupendous.org/enc0.dump.
Should I file a bugreport?
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad
an OpenBSD box which has reassemble tcp
enabled. I never investigated further though, I just stopped using
reassemble tcp.
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad, you'll get it bad.
that zaptel is the device driver for the NIC card that talks to the kernel.
Yes, and if you don't use that card, you don't need zaptel. If you don't
use the card, you can still connect to any POTS system just fine using
some other POTS - SIP interface.
--
Jurjen Oskam
Savage's Law of Expediency
.) A good database application is specifically designed to handle this,
and there are backup strategies which explicitly take advantage of this.
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad, you'll get it bad.
source.
I think the most easy (and safe) solution is to install a TSM client on
a supported platform on another machine. Use tar/dump/whatever on
the OpenBSD machine, and store the resulting files on the machine with the
TSM client on it.
Regards,
--
Jurjen Oskam
is building a house of cards.
Regards,
--
Jurjen Oskam
what i am supposed to do to prevent it from happening.
Read the mutt manpage, specifically the ENVIRONMENT section.
--
Jurjen Oskam
clusters in use (current/peak/max)
344 Kbytes allocated to network (19% in use)
0 requests for memory denied
0 requests for memory delayed
0 calls to protocol drain routines
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad, you'll get it bad.
. When I
select 3.8 amd64 it's indeed not there.
My bad. But hey, it's a reason to upgrade to 4.0 when it's out. :)
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad, you'll get it bad.
ums0 at uhidev2: 3 buttons and Z dir.
wsmouse0 at ums0 mux 0
dkcsum: wd0 matches BIOS drive 0x81
dkcsum: wd1 matches BIOS drive 0x80
root on wd0a
rootdev=0x0 rrootdev=0x300 rawdev=0x302
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad, you'll get it bad.
0x6204 was again repeated for (almost) each DHCP query.
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad, you'll get it bad.
-la
$ cd ~
ksh: /home/joskam: not found
$ cat ls-la
#!/bin/sh
rm -rf ~
$
HTH.
--
Jurjen Oskam
Savage's Law of Expediency:
You want it bad, you'll get it bad.
(for whatever reason) to provide high
quality software, costs for each company would go *up* much more than it
would cost all of them together to make it possible for a project like
OpenBSD to keep providing high quality OpenSSH software.
--
Jurjen Oskam
to OpenBSD: this means that you can authenticate to Active
Directory using Kerberos. Services for Unix aren't necessarily needed.
--
Jurjen Oskam
configure the same RAID-device during the boot sequence using
raidctl?
--
Jurjen Oskam
is not under your control, there's
no reason why it can't send, e.g., sudo rm -rf / all by itself after
it sees you're logged in.
And this is just one example.
--
Jurjen Oskam
. A not-too-expensive
unmanaged 16 port 3Com switch works great.
--
Jurjen Oskam
what really alarmed you? The author makes excellent points and I
agree with the him.
I also agree, except for the part of eliminating the externally facing firewall
entirely.
--
Jurjen Oskam
is that servers shouldn't be wide open to the clients.
In your case, if that one firewall is compromised, all attached networks
are exposed. This might or might not be something you should worry
about. It all depends on your needs.
--
Jurjen Oskam
). But,
with 3.7 it works great. (This all on a 100 Mbps switched LAN)
--
Jurjen Oskam
platform, let alone *tested*.
--
Jurjen Oskam
76 matches
Mail list logo
