Re: How to customise the OS update process
Hi Rubén， on Sat, 6 Apr 2024 12:12:00 + Rubén Llorente wrote: > An option I can think about is downloading the upgrade kernel and > booting from it, instead of using sysupgrade. The upgrade process will > let you select which sets you want to install and which ones you want > to exclude. I see. However, manual installation was a background that 'has never been done well, so we want to avoid it'. > In practice, I think you are better off just installing all the sets > and being done with it. Stuart also mentioned it and found it easy and appropriate. From now on I will use it with all the packages in it. Thank you very much. Sincerely yours, --- WATANABE, Takeo t...@kasaneiro.jp > WATANABE Takeo wrote: >> Hi everyone, >> The most common way to upgrade OpenBSD is to use "sysupgrade". >> However, I do not want to install certain packages (e.g. game). >> # When the host is built, it is not installed, because the >> Is there any way to upgrade to fulfil these wishes? >
Re: How to customise the OS update process
Hi Sturt,
on Sat, 6 Apr 2024 12:02:24 - (UTC)
Stuart Henderson wrote:
> sysupgrade -n
> rm /home/_sysupgrade/{x,game}*.tgz
> reboot
That's right.
I did not read the "man" very carefully about "syspgrade".
It was a good learning experience. Thank you.
> Though I wouldn't bother unless very constrained on storage space.
> A lot of time has been wasted by developers over the years when people
> have not installed xbase (or worse, installed an old one but not updated
> it) and run into problems with packages.
So that's how it happened.
I understand it well now.
These are the packages that you have to install and then
I will install all these packages and put them into operation.
Thank you so much.
Sincerely yours
---
WATANABE, Takeo
t...@kasaneiro.jp
> On 2024-04-06, WATANABE Takeo wrote:
>> Hi everyone,
>>
>> The most common way to upgrade OpenBSD is to use "sysupgrade".
>>
>> However, I do not want to install certain packages (e.g. game).
>> # When the host is built, it is not installed, because the
>>
>> Is there any way to upgrade to fulfil these wishes?
>>
>> I wrote "/auto_upgrade.conf" and
>> I tried "sysupgrade" with the following in "/auto_upgrade.conf",
>> but all packages were installed.
>>
>> ---
>> Location of sets = disk
>> Pathname to the sets = /home/_sysupgrade/
>> Set name(s) = -x*
>> Set name(s) = -game*
>> Set name(s) = done
>> Directory does not contain SHA256.sig. Continue without verification = yes
>> ---
>>
>> If you have found errors in this method or know of other methods,
>> please let us know.
>>
>> Sincerely yours.
>>
>> ---
>> WATANABE, Takeo
>> t...@kasaneiro.jp
>>
>>
>
>
> --
> Please keep replies on the mailing list.
>
7.5 NO hard drive?
Hello i have 1 DELL Latitude E4300 that had OBSD 7.3 working correctly, but i decided to do a clean installation of 7.5 deleting everything on it with a live cd linux; then tested 7.5 and it says NO disk. After that i tested Linux, NetBSD, FreeBSD all them where installed without a problem; But, OBSD 7.3 7.4 7.5 said NO disk! It is something related to OBSD? What could happened? How to install OBSD 7.5 PS: Thanks for the new version 7.5 i run 2 laptops and 1 server with it! Thanks
Re: Migrate to different FS layout of OpenBSD
On Sat, 06 Apr 2024 23:14:39 +0200, Peter Hessler wrote: > > RAID0 is called that because zero is what you'll recover if you lose a > disk. This is amazingly dangerous, and you're going to have a bad time. > > Do a backup, then restore from backup. > I was totally misslead. I mean that I have RAID1 which is know as mirror. To be clear: here a two identical servers where I'd like to change FS layout, and before I go to reinstall everything, I can try this approach. -- wbr, Kirill
Re: Migrate to different FS layout of OpenBSD
Kirill A. Korinsky writes: > Folks, > > I'm looking for a way to migrate to different layout some OpenBSD systems. > > So, questions: > 1. Has anyone done something like this before? > 2. Do you have any instruction or that to expect? Yes. What to expect? There is a very good chance data will be lost, so before you proceed back everything up. Of course no backup is complete without testing that it can be restored, so verify that you can turn your backup back into a working system. Because you now have a backup abandon the idea of doing shenanigans that will probably go wrong and install OpenBSD fresh on a set of discs formatted however you like then restore your backup. Matthew
Re: Migrate to different FS layout of OpenBSD
RAID0 is called that because zero is what you'll recover if you lose a disk. This is amazingly dangerous, and you're going to have a bad time. Do a backup, then restore from backup. On 2024 Apr 06 (Sat) at 22:43:05 +0200 (+0200), Kirill A. Korinsky wrote: :Folks, : :I'm looking for a way to migrate to different layout some OpenBSD systems. : :All of them has RAID0 and as far as I think I may something like this: : :1. Remove second disk from RAID. :2. Build a new RAID0 on the second disk. :3. Make desires layout on the second RAID. :4. dump | restore :5. Boot from the second RAID. :6. Add the first disk to the second RAID. : :I have re-read https://www.openbsd.org/faq/faq14.html a few times and I :feel that this is quite risky. : :So, questions: :1. Has anyone done something like this before? :2. Do you have any instruction or that to expect? : :Thanks in advance. : :-- :wbr, Kirill : -- Celebrate Hannibal Day this year. Take an elephant to lunch.
Migrate to different FS layout of OpenBSD
Folks, I'm looking for a way to migrate to different layout some OpenBSD systems. All of them has RAID0 and as far as I think I may something like this: 1. Remove second disk from RAID. 2. Build a new RAID0 on the second disk. 3. Make desires layout on the second RAID. 4. dump | restore 5. Boot from the second RAID. 6. Add the first disk to the second RAID. I have re-read https://www.openbsd.org/faq/faq14.html a few times and I feel that this is quite risky. So, questions: 1. Has anyone done something like this before? 2. Do you have any instruction or that to expect? Thanks in advance. -- wbr, Kirill
Re: ipv6 assistance
Someone with pull at UPC^W ziggo^W vodafone^W liberty global could potentially get that situation improved. On 6 April 2024 19:04:52 CEST, Peter Hessler wrote: >OpenBSD natively supports IPv6 addressing via static configuration and >SLAAC. We do not have a DHCPv6 client in base, so currently you have to >use a package for that. > > >On 2024 Apr 06 (Sat) at 13:01:31 -0400 (-0400), Sonic wrote: >:That works - I didn't realize I needed to install a package to have ipv6 >:work with OpenBSD. >: >:Thank you. > -- Sent from a mobile device. Please excuse poor formatting.
Re: 7.5 /var/log/messages - vfprintf %s NULL in "%.*s"
Дана 24/04/06 06:04PM, Stuart Henderson написа: > The fact that these all started hitting this with the same printf string > (including tmux, which is in base) makes me wonder if it's coming from a > library, the most likely being libcurses which was updated between 7.4 > and 7.5 (which all of those use). > > Try to ascertain what's going on when that message is logged. ktrace > might give some clues. Of course, the package containing the code passing NULL to *printf should be identified first, and the bug report should be sent to that package. It is entirely possible that it is libcurses or another library. In the case of dunst, it was dunst. Passing NULL to *printf is Undefined Behavior in C, and there is a StackOverflow answer detailing the reasons at [1]. [1]: https://stackoverflow.com/a/11589500
Re: 7.5 /var/log/messages - vfprintf %s NULL in "%.*s"
On 2024-04-06, Страхиња Радић wrote: > Дана 24/04/06 02:42PM, Eivind Eide написа: >> tmux: vfprintf %s NULL in "%.*s" >> bash: vfprintf %s NULL in "%.*s" >> multitail: vfprintf %s NULL in "%.*s" >> vim: vfprintf %s NULL in "%.*s" > > This happens in OpenBSD when a program passes NULL pointer to *printf family > of > functions. The bug reports should be directed upstream to individual > packages. The fact that these all started hitting this with the same printf string (including tmux, which is in base) makes me wonder if it's coming from a library, the most likely being libcurses which was updated between 7.4 and 7.5 (which all of those use). Try to ascertain what's going on when that message is logged. ktrace might give some clues. Alternatively try to identify what's triggering it (this isn't normal - I don't recall ever seeing that from tmux/vim myself) - could be an environment variable. Can you reproduce it if you reset the environment (env -i)? How about if you use a different TERM?
Re: ipv6 assistance
OpenBSD natively supports IPv6 addressing via static configuration and SLAAC. We do not have a DHCPv6 client in base, so currently you have to use a package for that. On 2024 Apr 06 (Sat) at 13:01:31 -0400 (-0400), Sonic wrote: :That works - I didn't realize I needed to install a package to have ipv6 :work with OpenBSD. : :Thank you. -- 186,282 miles per second: It isn't just a good idea, it's the law!
Re: ipv6 assistance
That works - I didn't realize I needed to install a package to have ipv6 work with OpenBSD. Thank you.
Re: ipv6 assistance
On Sat, Apr 6, 2024 at 8:10 AM Sonic wrote: > > Running -current on my router and finally (after years) decided to move into > using ipv6. > I added "inet6 autoconf" to hostname.em0 (also has "inet autoconf") and I get > a link local address: > = > # ifconfig em0 > em0:inet6 fe80::2132:31ff:fe0b:7ea4%em0 prefixlen 64 scopeid 0x1 > inet 69.31.273.6 netmask 0xfc00 broadcast 69.31.273.255 > = > And an ipv6 default route: > = > Internet6: > Destination Gateway > Flags Refs Use Mtu Prio Iface > default fe80::301:5bcf:fe75:2646%em0 > UGS0 22 - 8 em0 > = > Which matches the default router proposal listed by slaacctl: > = > em0: > index: 1 running: yes temporary: yes > lladdr: 40:62:31:0b:7e:a4 > inet6: fe80::2132:31ff:fe0b:7ea4%em0 > Router Advertisement from fe80::201:5cff:fe75:2646%em0 > received: 2024-04-06 10:49:17; 0s ago > Cur Hop Limit: 0, M: 1, O: 1, Router Lifetime: 1800s > Default Router Preference: Medium > Reachable Time: 360ms, Retrans Timer: 1000ms > prefix: 2001:623:8016:54::/64 > On-link: 0, Autonomous address-configuration: 0 > vltime: 604800, pltime: 302400 > prefix: 2001:623:6007:a5::/64 > On-link: 0, Autonomous address-configuration: 0 > vltime: 604800, pltime: 302400 > prefix: 2001:623:500e:16::/64 > On-link: 0, Autonomous address-configuration: 0 > vltime: 604800, pltime: 302400 > prefix: 2001:623:4020:a5::/64 > On-link: 0, Autonomous address-configuration: 0 > vltime: 604800, pltime: 302400 > Default router proposals > id:1, state: PROPOSAL_CONFIGURED > router: fe80::301:5bcf:fe75:2646%em0 > router lifetime: 1800 > Preference: Medium > updated: 2024-04-06 10:49:17; 0s ago, timeout: 1788s > = > However, there's no other ipv6 address on the interface - I suspect an > address from one of those 2001: prefix groups needs to be assigned. > Should not dhcpleased handle this? > Most of the web posts I find deal with the pre-dhcpleased days. > > I'm on Comcast (Xfinity) in the US. i have comcast, and i use dhcpcd for ipv6. replace rge0 and vport0 with your wan/lan interface.. # /etc/dhcpcd.conf ipv6only duid persistent vendorclassid option rapid_commit option interface_mtu # make dhcpcd not touch nameservers. nohook resolv.conf require dhcp_server_identifier slaac private allowinterfaces rge0 interface rge0 ipv6rs iaid 1 ia_na 1 ia_pd 1/::/64 vport0/0/64 > > Thank you, > Chris > > >
Re: 7.5 /var/log/messages - vfprintf %s NULL in "%.*s"
Дана 24/04/06 02:42PM, Eivind Eide написа: > tmux: vfprintf %s NULL in "%.*s" > bash: vfprintf %s NULL in "%.*s" > multitail: vfprintf %s NULL in "%.*s" > vim: vfprintf %s NULL in "%.*s" This happens in OpenBSD when a program passes NULL pointer to *printf family of functions. The bug reports should be directed upstream to individual packages. See, for example, a similar issue I filed to dunst's Github[1]. Apparently, some developers think passing NULL to *printf is a-okay. [1]: https://github.com/dunst-project/dunst/issues/1305
Re: ipv6 assistance
On Sat, Apr 6, 2024, at 10:09 AM, Sonic wrote: > I'm on Comcast (Xfinity) in the US. Your setup will be specific to your ISP. I'm on AT Fiber, which uses SLAAC for the WAN interface and DHCPv6-PD for internal interfaces. I do the latter with dhcpcd. A quick search indicates Xfinity uses DHCPv6 for the WAN interface and DHCPv6-PD for internal interfaces. I haven't confirmed any of that, as I'm not a customer. You should be able to translate most Xfinity guides for use with OpenBSD, I would think. Brian Conway Owner RCE Software, LLC
ipv6 assistance
Running -current on my router and finally (after years) decided to move into using ipv6. I added "inet6 autoconf" to hostname.em0 (also has "inet autoconf") and I get a link local address: = # ifconfig em0 em0:inet6 fe80::2132:31ff:fe0b:7ea4%em0 prefixlen 64 scopeid 0x1 inet 69.31.273.6 netmask 0xfc00 broadcast 69.31.273.255 = And an ipv6 default route: = Internet6: Destination Gateway Flags Refs Use Mtu Prio Iface default fe80::301:5bcf:fe75:2646%em0 UGS0 22 - 8 em0 = Which matches the default router proposal listed by slaacctl: = em0: index: 1 running: yes temporary: yes lladdr: 40:62:31:0b:7e:a4 inet6: fe80::2132:31ff:fe0b:7ea4%em0 Router Advertisement from fe80::201:5cff:fe75:2646%em0 received: 2024-04-06 10:49:17; 0s ago Cur Hop Limit: 0, M: 1, O: 1, Router Lifetime: 1800s Default Router Preference: Medium Reachable Time: 360ms, Retrans Timer: 1000ms prefix: 2001:623:8016:54::/64 On-link: 0, Autonomous address-configuration: 0 vltime: 604800, pltime: 302400 prefix: 2001:623:6007:a5::/64 On-link: 0, Autonomous address-configuration: 0 vltime: 604800, pltime: 302400 prefix: 2001:623:500e:16::/64 On-link: 0, Autonomous address-configuration: 0 vltime: 604800, pltime: 302400 prefix: 2001:623:4020:a5::/64 On-link: 0, Autonomous address-configuration: 0 vltime: 604800, pltime: 302400 Default router proposals id:1, state: PROPOSAL_CONFIGURED router: fe80::301:5bcf:fe75:2646%em0 router lifetime: 1800 Preference: Medium updated: 2024-04-06 10:49:17; 0s ago, timeout: 1788s = However, there's no other ipv6 address on the interface - I suspect an address from one of those 2001: prefix groups needs to be assigned. Should not dhcpleased handle this? Most of the web posts I find deal with the pre-dhcpleased days. I'm on Comcast (Xfinity) in the US. Thank you, Chris
7.5 /var/log/messages - vfprintf %s NULL in "%.*s"
After upgrading to 7.5 amd64 -stable (and all ports updated) I get these messages in /var/log/messages. This is with bash from ports inside tmux over SSH: tmux: vfprintf %s NULL in "%.*s" bash: vfprintf %s NULL in "%.*s" multitail: vfprintf %s NULL in "%.*s" vim: vfprintf %s NULL in "%.*s" tmux: vfprintf %s NULL in "%.*s" bash: vfprintf %s NULL in "%.*s" multitail: vfprintf %s NULL in "%.*s" bash: vfprintf %s NULL in "%.*s" top: vfprintf %s NULL in "%.*s" top: vfprintf %s NULL in "%.*s" bash: vfprintf %s NULL in "%.*s" last message repeated 2 times irssi: vfprintf %s NULL in "%.*s" bash: vfprintf %s NULL in "%.*s" bash: vfprintf %s NULL in "%.*s" mutt: vfprintf %s NULL in "%.*s" vim: vfprintf %s NULL in "%.*s" -- Eivind Eide "ONLY THOSE WHO ATTEMPT THE IMPOSSIBLE WILL ACHIEVE THE ABSURD" - Oceania Association of Autonomous Astronauts
Re: How to customise the OS update process
An option I can think about is downloading the upgrade kernel and booting from it, instead of using sysupgrade. The upgrade process will let you select which sets you want to install and which ones you want to exclude. In practice, I think you are better off just installing all the sets and being done with it. The old BSD Games rock hard. WATANABE Takeo wrote: Hi everyone, The most common way to upgrade OpenBSD is to use "sysupgrade". However, I do not want to install certain packages (e.g. game). # When the host is built, it is not installed, because the Is there any way to upgrade to fulfil these wishes?
Re: How to customise the OS update process
sysupgrade -n
rm /home/_sysupgrade/{x,game}*.tgz
reboot
Though I wouldn't bother unless very constrained on storage space.
A lot of time has been wasted by developers over the years when people
have not installed xbase (or worse, installed an old one but not updated
it) and run into problems with packages.
On 2024-04-06, WATANABE Takeo wrote:
> Hi everyone,
>
> The most common way to upgrade OpenBSD is to use "sysupgrade".
>
> However, I do not want to install certain packages (e.g. game).
> # When the host is built, it is not installed, because the
>
> Is there any way to upgrade to fulfil these wishes?
>
> I wrote "/auto_upgrade.conf" and
> I tried "sysupgrade" with the following in "/auto_upgrade.conf",
> but all packages were installed.
>
> ---
> Location of sets = disk
> Pathname to the sets = /home/_sysupgrade/
> Set name(s) = -x*
> Set name(s) = -game*
> Set name(s) = done
> Directory does not contain SHA256.sig. Continue without verification = yes
> ---
>
> If you have found errors in this method or know of other methods,
> please let us know.
>
> Sincerely yours.
>
> ---
> WATANABE, Takeo
> t...@kasaneiro.jp
>
>
--
Please keep replies on the mailing list.
How to customise the OS update process
Hi everyone, The most common way to upgrade OpenBSD is to use "sysupgrade". However, I do not want to install certain packages (e.g. game). # When the host is built, it is not installed, because the Is there any way to upgrade to fulfil these wishes? I wrote "/auto_upgrade.conf" and I tried "sysupgrade" with the following in "/auto_upgrade.conf", but all packages were installed. --- Location of sets = disk Pathname to the sets = /home/_sysupgrade/ Set name(s) = -x* Set name(s) = -game* Set name(s) = done Directory does not contain SHA256.sig. Continue without verification = yes --- If you have found errors in this method or know of other methods, please let us know. Sincerely yours. --- WATANABE, Takeo t...@kasaneiro.jp
