The lack of Xsetup might be desired functionality but that's contrary
to xenodm(1):
After resetting the X server, xenodm runs the Xsetup script
to assist in setting up the screen the user sees along with
the xlogin widget.
The xlogin widget, which xenodm presents, offers the f
The description of ksh(1)'s handling of CDPATH is not quite complete
and, worse, contradictory in the two locations it's mentioned. sh(1)
barely touches on it but is Not Wrong so I've left it alone.
(FWIW I also checked the CDPATH scanning code and actually poked
at a real shell so I've confirmed
Machine is a new PC Engines apu.1d with / on the a 4GB SD card.
Was yanked off the table and had its power pulled. When rebooting / was
deemed uncheckable and when doing so myself the kernel paniced.
# cat /etc/fstab
85ee1fbed3aff0b6.a / ffs ro,noatime 1 0
85ee1fbed3aff0b6.d /usr ffs ro,softdep,n
>Synopsis: CVS fails to check out large files on amd64, sometimes
>Category: user amd64
>Environment:
System : OpenBSD 5.8
Details : OpenBSD 5.8 (GENERIC.MP) #1236: Sun Aug 16 02:31:04 MDT
2015
dera...@amd64.openbsd.org:/usr/src/sys/arch
Stuart Henderson writes:
> On 2016/02/01 12:44, cho...@jtan.com wrote:
> > >Synopsis: CVS fails to check out large files on amd64, sometimes
> > >Category: user amd64
> > >Environment:
> > System : OpenBSD 5.8
> > Details : OpenBSD 5.8 (GENERIC.MP) #1236: Sun Aug 16 02:31:04 MDT
>Synopsis: athn PCI card (AR9281) AP not found by scan on some devices
>Category: wifi driver?
>Environment:
System : OpenBSD 5.8
Details : OpenBSD 5.8 (GENERIC) #1170: Sun Aug 16 02:26:00 MDT 2015
dera...@amd64.openbsd.org:/usr/src/sys/a
Stefan Sperling writes:
> On Sun, Mar 06, 2016 at 10:22:17PM +0200, cho...@jtan.com wrote:
> > >Synopsis: athn PCI card (AR9281) AP not found by scan on some devices
> > >Category: wifi driver?
> > >Environment:
> > System : OpenBSD 5.8
> > Details : OpenBSD 5.8 (GENERIC) #1170:
Stefan Sperling writes:
> On Sun, Mar 06, 2016 at 10:22:17PM +0200, cho...@jtan.com wrote:
> > >Description:
> > /etc/hostname.athn0 contains:
> > inet 192.168.42.1 255.255.255.0
> > mediaopt hostap chan 56
> > nwid Testies
> > wpakey insecure
>
> Note that setting an address puts the interfac
>Synopsis: Terrible athn performance after upgrade to 6.2
>Category: kernel
>Environment:
System : OpenBSD 6.2
Details : OpenBSD 6.2 (GENERIC.MP) #134: Tue Oct 3 21:22:29 MDT
2017
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compil
The description of the -d flag states that it prevents the redirection
of stdin to /dev/null but it should say stdout.
Matthew
A grammatical error in login.conf(5):
--- login.conf.5?rev=1.64 Sun Jan 6 15:27:44 2019
+++ login.conf.5Sun Jan 6 15:28:10 2019
@@ -104,7 +104,7 @@
.Pp
.It auth Ta list Ta Dv passwd Ta
Allowed authentication styles.
-The first value is the default styles.
+The first value is the
I've just run syspatch on a 6.5 box and obviously I've allocated the space
poorly but because of that, this happened:
drogo# syspatch
Get/Verify syspatch65-001_rip6cks... 100% |***| 196 KB
00:00
Installing patch 001_rip6cksum
Get/Verify syspatch65-002_srtp.tgz 100% |
Unrelated to my other syspatch email, I ran syspatch inside a chroot (same
server so ignore the identical hostname) and this happened:
drogo# syspatch
Get/Verify syspatch65-002_srtp.tgz 100% |*| 4316 KB
00:04
Installing patch 002_srtp
Get/Verify syspatch65-003_mds.tgz
Antoine Jacoutot writes:
> That is because 001 only includes kernel object files which you do not have
> since you run under a chroot and didn't extract /usr/share/relink/kernel.tgz
> So syspatch(8) considers you don't have that "set" installed.
> syspatch-003 on the other end includes a header cha
This isn't a bug per se, more of an incongruity in how security-centric tools
work wrt root, specifically doas and chroot/su/other:
joe@drogo$ doas -s
drogo# doas -u chohag -s
doas (root@drogo) password:
doas: Authorization failed
drogo# chroot -u chohag /
drogo$ ^D
drogo#
Ingo Schwarze writes:
> I see nothing wrong with it. It is easier to describe in the manual
Indeed I was not suggesting that there was something wrong; being asked for a
password when doing something which root could implicitly do simply confused me
for a moment which prompted figuring out what
Theo de Raadt writes:
> I don't see the point.
>
> If you get asked the question, and you know the answer, you answer it.
> Why is that not the end of the story?
When I used doas the other day to gain the rights of a user it asked me for a
password which I didn't expect, as I was root. Confirming
Ted Unangst writes:
> Ted Unangst wrote:
> > I think this is not the right note, but after some review I just realized we
> > don't ever say that a password is required. It's merely hinted at in various
> > options. I'll make a note of that.
>
> Just a simple sentence, but I think it makes explicit
I decided late in an application's life to start using pledge, so
I put a call in at the top and started running it and adding the
requirements reported by dmesg on each iteration.
Eventually it reported that the tty promise was breached so I added
that and it reported again that the tty promise w
Bryan Steele writes:
> https://www.openbsd.org/faq/faq4.html#Download
>
> > The install72.iso and install72.img images do not contain an SHA256.sig
> > file, so the installer will complain that it can't check the signature
> > of the included sets:
> >
> > Directory does not contain SHA256.sig. Con
If the function implementing xcb_connect is called directly with a
custom xcb_auth_info_t then checking that the screen in $DISPLAY
is valid is skipped.
Matthew
Index: xcb_util.c
===
RCS file: /src/datum/openbsd/cvs/xenocara/dist/lib
I haven't looked into what's causing this behaviour yet because I
was cooking but I did manage to make it reproducable. Also it's very
unlikely to show up in normal daily use.
I was playing a series of flac files through mplayer (single process,
many files) in a root shell on the text console (DIS
Matthieu Herrb writes:
> On Tue, Jan 31, 2023 at 10:31:34PM +, cho...@jtan.com wrote:
> > If the function implementing xcb_connect is called directly with a
> > custom xcb_auth_info_t then checking that the screen in $DISPLAY
> > is valid is skipped.
> >
> > Matthew
>
> Hi,
>
> Thank you for t
Jason McIntyre writes:
> On Sun, Jun 16, 2024 at 03:05:24AM -0300, Crystal Kolipe wrote:
> > On Sat, Jun 15, 2024 at 06:45:21PM -0500, Tim Chase wrote:
> > > According to
> > >
> > > $ man [ | grep -A4 -e "-L.*f"
> > > -L file
> > > True if file exists and is a symbolic link. This
In CTL_NET_NAMES, ECMA is added as "emca" which looks like a typo
even in French. The value won't be used anywhere though which is
likely why it slipped through. It's been there since day one.
Matthew
Index: sys/sys/socket.h
===
RCS
[gs]etsockopt(2) points out that SO_TYPE, SO_DOMAIN, SO_PROTOCOL
and SO_ERROR are read-only but does not include SO_PEERCRED in that
list. Also in the initial big list at the top of the page, SO_PEERCRED
is not singled out as get only.
This patch shuffles the lines around to put SO_PEERCRED with i
Rather than shouting into the void, after the last time this company
sent the list a message informing us all that we had been signed
up to something or other, someone evidently did the legwork to
contact the company and request that the record be removed.
This was the follow-up email explaining t
Jason McIntyre writes:
> On Sun, Nov 10, 2024 at 10:09:58PM +, cho...@jtan.com wrote:
> > I had the ascii manpage open and while it was sitting there I thought
> > that something looked off about it. I took a closer look and realised
> > that the columns of symbols in the hexadecimal set are le
I had the ascii manpage open and while it was sitting there I thought
that something looked off about it. I took a closer look and realised
that the columns of symbols in the hexadecimal set are left of the
octal and decimal sets by one character.
The included patch moves a space character from af
A demonstration should be sufficient I think.
mdoc(7) in a terminal:
... Spacing is suppressed after opening delimiters and before
closing delimiters. For example,
.Aq ( [ word ] ) .
renders as:
([⟨word⟩]).
But http://man.openbsd.org/mdoc.7 appears as:
Summary: Large writes (eg. copying /dev/random) to an mpii device
quickly fails and locks up any further IO on the device.
I am not familiar with device drivers but I can do whatever is
necessary to probe this driver and/or device because there's nothing
on this machine yet so there's nothing on i
31 matches
Mail list logo
