Re: as cannot do endbr64 instructions (too old)
On Wed, Jan 03, 2024 at 08:50:43AM +0100, Lorenz (xha) wrote:
> On Tue, Jan 02, 2024 at 08:32:00PM -, Stuart Henderson wrote:
> > I can't say. Though I doubt there would much objection if it's clean and
> > not a copy of a GPLv3-licensed upstream commit.
>
> what about this?
>
> i am not sure about the situation on arm64. it looks like newer gnu
> assemblers don't like bti instructions unless explicitly enabled.
> llvm seems to be using hint #34 for compatibility.
>
> is /usr/bin/as the GNU assembler on arm64 aswell?
There is no as(1) installed on arm64.
-Otto
>
> Index: include/opcode/i386.h
> ===
> RCS file: /cvs/src/gnu/usr.bin/binutils-2.17/include/opcode/i386.h,v
> retrieving revision 1.11
> diff -C5 -r1.11 i386.h
> *** include/opcode/i386.h 9 Sep 2018 21:59:43 - 1.11
> --- include/opcode/i386.h 3 Jan 2024 07:35:49 -
> ***
> *** 1532,1541
> --- 1532,1545
>
> /* Intel PCID extension */
> {"invpcid", 2, 0x660f3882, X, CpuNEW|CpuNo64,
> Modrm|IgnoreSize|No_bSuf|No_wSuf|No_sSuf|No_qSuf|No_xSuf|NoRex64, {
> BaseIndex|Disp8|Disp16|Disp32|Disp32S, Reg32 } },
> {"invpcid", 2, 0x660f3882, X, CpuNEW|Cpu64,
> Modrm|IgnoreSize|No_bSuf|No_wSuf|No_sSuf|No_qSuf|No_xSuf|NoRex64, {
> BaseIndex|Disp8|Disp16|Disp32|Disp32S, Reg64 } },
>
> + /* Intel Indirect Branch Tracking extensions */
> + {"endbr64", 0, 0xF30F1E, 0xFA, Cpu64, NoSuf|ImmExt, { 0, 0, 0 } },
> + {"endbr32", 0, 0xF30F1E, 0xFB, CpuNo64, NoSuf|ImmExt, { 0, 0, 0 } },
> +
> /* sentinel */
> {NULL, 0, 0, 0, 0, 0, { 0, 0, 0} }
> };
> #undef X
> #undef NoSuf
>
Re: How to access Xauthority for VNC Server
Hello there • Adam Retter [2024-01-02 23:14]: > Apologies but I am a little bit unclear about how X authfiles should > work in OpenBSD. > > I have started with a fresh OpenBSD 7.4 install, and I opted to > install the X Window System. My goal is to be able to export my > display over VNC as I have no access to the mouse and keyboard of the > machine. > > I have installed the VNC Server software by running as root - pkg_add tigervnc > > To be able to run the VNC Server, it needs access to the X Authority > file. I want to ideally run the VNC Server under a non-root account. I > have found an authority file under /etc/X11/xenodm/authdir/authfiles/ > however its name seems to be randomly decided each time xenodm is > started during System boot. For example at present it is > /etc/X11/xenodm/authdir/authfiles/A:0-r4dlnM but that will change if > the system is rebooted. > > To run the VNC Server, I think I need to execute something like the > following command: > > XAUTHORITY=/etc/X11/xenodm/authdir/authfiles/A:0-r4dlnM x0vncserver > -display :0 -PasswordFile ~/.vnc/passwd > > It is not clear to me how I can set this up so that x0vncserver can > access the correctly named auth file each time the machine restarts, > and also under which account it would be considered best practice to > run x0vncserver... Should I run it under my user account, the `_x11` > account, or an account created just for that purpose? > Ideally the VNC Server would start during system startup also. > > I also note that the auth files such as > /etc/X11/xenodm/authdir/authfiles/A:0-r4dlnM are owned by the `_x11` > account and group, and are only readable by the owner (mode 0600). > > Please advise on the best way to set this up? You might want to look at Xvnc rather than x0vncserver. Xvnc is started by vncserver, which you can run as your normal user. > Kind regards. Adam. Here's a setup that used to work at some point, it could give you some ideas. Note how vncserver is started in the user's tmux session -- this way I can attach to it and see what is going on. To run at startup, you could either add a line to rc.local, or (ab)use crontab's @reboot facility. In /etc/rc.local echo -n ' VNC' su -l -c '/home//bin/runxvnc.sh 2>&1' >/dev/null & Then in /home//bin/runxvnc.sh #!/bin/sh tmux new-session -d -s Xvnc \ /usr/local/bin/vncserver :2 \ -geometry 1920x1080 \ -depth 32 \ -fg \ -xstartup ~/.vnc/xstartup \ -interface 127.0.0.1 \ -rfbport 5901 \ -rfbauth ~/.vnc/passwd \ -alwaysshared And in ~/.vnc/xstartup #!/bin/sh unset SESSION_MANAGER unset DBUS_SESSION_BUS_ADDRESS [ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources export LC_CTYPE="en_US.UTF-8" /usr/local/bin/startxfce4 > -- > Adam Retter > > skype: adam.retter > tweet: adamretter > http://www.adamretter.org.uk > -- -- Kirill Miazine
Re: ProtectLi w/ OpenBSD
On 2024-01-03, Kenneth Hendrickson wrote: > Is there any newer information than this: > https://OpenBsdMailBox.blogspot.com/2023/05/protectli-vp2420-with-dasharo.html That is exactly how a boot looks if you are on a device with serial console and don't tell the boot loader to use the serial console. stty com0 set tty com0 boot -- Please keep replies on the mailing list.
ignore dns dhcpleased
Hi,
I noticed that ignoring nameservers from leases only works
on IPv4 addresses.
in /etc/dhcpleased.conf
interface vio0 {
ignore dns
}
resolvd still adds a IPv6 nameserver
nameserver 2001:19f0:300:1704::6 # resolvd: vio0
Is this intentional?
Best regards,
Peter
Re: ignore dns dhcpleased
On Wed, Jan 03, 2024 at 12:15:04PM +0100, Peter Wens wrote:
> Hi,
>
> I noticed that ignoring nameservers from leases only works
> on IPv4 addresses.
>
> in /etc/dhcpleased.conf
>
> interface vio0 {
> ignore dns
> }
>
> resolvd still adds a IPv6 nameserver
>
> nameserver 2001:19f0:300:1704::6 # resolvd: vio0
>
> Is this intentional?
>
>
> Best regards,
>
> Peter
>
This very likely happens via slaacd, as v6 route proposals can
contais DNS resolver info. AFAIK, there is no way to tell slaacd to
not send DNS entries to resolvd, so you should try to tell the device
sending the v6 route advertisements to stop include DNS info.
-Otto
Re: ignore dns dhcpleased
Hi Otto,
I checked it, and yes it's slaacd
...
rdns_proposal_state_transition[vio0] PROPOSAL_NOT_CONFIGURED ->
PROPOSAL_CONFIGURED, timo: 3588
gen_rdns_proposal: iface 1: fe80::f...
...
Don't know how to disable this (e.g. vultr), so for now i disable resolvd.
On 1/3/24 13:20, Otto Moerbeek wrote:
On Wed, Jan 03, 2024 at 12:15:04PM +0100, Peter Wens wrote:
Hi,
I noticed that ignoring nameservers from leases only works
on IPv4 addresses.
in /etc/dhcpleased.conf
interface vio0 {
ignore dns
}
resolvd still adds a IPv6 nameserver
nameserver 2001:19f0:300:1704::6 # resolvd: vio0
Is this intentional?
Best regards,
Peter
This very likely happens via slaacd, as v6 route proposals can
contais DNS resolver info. AFAIK, there is no way to tell slaacd to
not send DNS entries to resolvd, so you should try to tell the device
sending the v6 route advertisements to stop include DNS info.
-Otto
Re: ignore dns dhcpleased
On 2024-01-03, Peter Wens wrote: > Hi Otto, > > I checked it, and yes it's slaacd > > ... > rdns_proposal_state_transition[vio0] PROPOSAL_NOT_CONFIGURED -> > PROPOSAL_CONFIGURED, timo: 3588 > gen_rdns_proposal: iface 1: fe80::f... > ... > > Don't know how to disable this (e.g. vultr), so for now i disable resolvd. If you want to force a specific server, that's often the right answer anyway. An alternative is to use unwind with its config file.
Re: ignore dns dhcpleased
I was using unwind, but i changed over to use unbound instead and so i noticed the changes made in resolv.conf by resolvd. On 1/3/24 13:37, Stuart Henderson wrote: On 2024-01-03, Peter Wens wrote: Hi Otto, I checked it, and yes it's slaacd ... rdns_proposal_state_transition[vio0] PROPOSAL_NOT_CONFIGURED -> PROPOSAL_CONFIGURED, timo: 3588 gen_rdns_proposal: iface 1: fe80::f... ... Don't know how to disable this (e.g. vultr), so for now i disable resolvd. If you want to force a specific server, that's often the right answer anyway. An alternative is to use unwind with its config file.
Script doesn't stop opensearch
Hello,
I don't understand how the startup/stop script works
# cat /etc/rc.d/opensearch
#!/bin/ksh
daemon="/usr/local/opensearch/bin/opensearch"
daemon_flags="-d -p /var/run/opensearch/opensearch.pid"
daemon_user="_opensearch"
. /etc/rc.d/rc.subr
pexp="$(/usr/local/bin/javaPathHelper -c opensearch)
.*org.opensearch.bootstrap.OpenSearch.*"
rc_reload=NO
rc_pre() {
install -d -o _opensearch /var/run/opensearch/
}
rc_cmd $1
I can confirm that the pid I see in /var/run/opensearch/opensearch.pid is the
same I see in ps ax | grep opensearch
However when I want to stop the process
# /etc/rc.d/opensearch stop
Nothing happens
And I don't understand how this stop command would do something like that
# kill -15 `cat /var/run/opensearch/opensearch.pid`
Thank you
Re: man.openbsd.org, cvsweb.openbsd.org maintenance
man.openbsd.org, cvsweb.openbsd.org, openbsd.cs.toronto.edu obsdacvs.cs.toronto.edu are all back up and running. Snapshots and packages should be up to date, now, too. My apologies for the inconvenience. Nick. On 12/19/23 15:38, Nick Holland wrote: Hello, man.openbsd.org, cvsweb.openbsd.org, openbsd.cs.toronto.edu and obsdacvs.cs.toronto.edu will be unavailable for site maintenance starting Thursday, December 21 about 6:00am ET (UTC-5) and hopefully be back up and running by Saturday, December 23, 6:00am ET. Sorry for any inconvenience. Nick.
Re: Script doesn't stop opensearch
> Am 04.01.2024 um 00:06 schrieb Mik J : > > However when I want to stop the process > # /etc/rc.d/opensearch stop > Nothing happens try: # rcctl stop opensearch You are not supposed to ever call the /etc/rc.d/* scripts directly. HTH Mike
Re: Run VM with 16G or more?
On Tue, Jan 02, 2024 at 08:29:03PM +0100, Kirill A. Korinsky wrote: > And one more noticed bug in vmd regarding memory. > > If I changed memory in /etc/vm.conf for running machine, run rcctl reload vmd, > and restart VM... It has no effect. > > The VM should be shutdown before reload. > > -- > wbr, Kirill > yes, vmctl reload does not reload specifications for currently running VMs.
