Kernels with just "OpenBSD 7.5" will appear for some time before
pub/OpenBSD/7.5/*/packages are available.
--
Sent from a phone, apologies for poor formatting.
On 21 February 2024 20:36:39 Kirill A. Korinsky wrote:
On Wed, 21 Feb 2024 21:11:05 +0100,
Stuart Henderson wrote:
If you're usin
Well, in a few weeks you will see why you need it.
On Wed, 21 Feb 2024 21:11:05 +0100,
Stuart Henderson wrote:
>
> If you're using sysupgrade -s, you also want -Dsnap in pkg_add.
>
After double check in man it seems not nessesary, let me quote:
%c Expands to the string "snapshots" when running a -current or -beta
kernel, or if th
On 2024-02-21, b...@fea.st wrote:
> FWIW if you guys want to yell at me for spreading bad ideas,
> I've posted how to do automatic updates here:
>
> https://openbsd.pages.dev/auto-updates/
If you're using sysupgrade -s, you also want -Dsnap in pkg_add.
On Wed, 21 Feb 2024 18:05:56 +0100,
b...@fea.st wrote:
>
> FWIW if you guys want to yell at me for spreading bad ideas,
> I've posted how to do automatic updates here:
>
> https://openbsd.pages.dev/auto-updates/
>
> I'm both trying out the Hugo package and like, documenting
> how I've set things
FWIW if you guys want to yell at me for spreading bad ideas,
I've posted how to do automatic updates here:
https://openbsd.pages.dev/auto-updates/
I'm both trying out the Hugo package and like, documenting
how I've set things up in case I have to reinstall.
Time moves fast and I'm damn impressed
On 2024-02-20, obs...@loopw.com wrote:
>
>
>> On Feb 20, 2024, at 2:31 AM, Thomas Schmidt
>> wrote:
>>
>> OP did indeed mean `sysupgrade`,
>
> which makes little sense _unless_ on -current, which will guarantee to break
> this every sixth months when -current shifts about.
>
>> but fwiw, `sysp
obs...@loopw.com wrote:
> Most of the patches don’t require a reboot. This idea sounds horrible for
> uptime. Sorry. I’m not rebooting something because a font was patched…
syspatch outputs a message that the system needs a reboot. This could be
parsed.
..@loopw.com:
>>> On Feb 15, 2024, at 10:12 AM, b...@fea.st wrote:
>>> am I the only one using automatic OS updates
>>> 0 3 * * * root sysupgrade
>> Maybe you meant “syspatch” there?
>> Syspatching via cron is questionable - Some of the patches
OP did indeed mean `sysupgrade`, but fwiw, `syspatch && reboot` reboots
your system if a patch as applied. I got it in all of my servers'
cronjobs.
- Thomas
Am 17.02.2024 um 02:24 schrieb obs...@loopw.com:
On Feb 15, 2024, at 10:12 AM, b...@fea.st wrote:
am I the only one using
On Fri, Feb 16, 2024, at 17:09, Jan Stary wrote:
> And this saves you what, ten keystrokes a day?
Yes, it felt silly typing the same things every day and waiting for
the computer to update.
(If an update takes 4 minutes per day to babysit, that's about
2 hours per month)
On Fri, Feb 16, 2024, a
On Thu, Feb 15, 2024, at 21:52, Florian Obser wrote:
> > 0 3 * * * root sysupgrade
>
> This will stop working at the next release. Assuming you want to run -current.
Thanks, changed to 'sysupgrade -s'.
> >30 3 * * * root pkg_add -u
>
> This will most likely run after package
> On Feb 15, 2024, at 10:12 AM, b...@fea.st wrote:
> am I the only one using automatic OS updates
> 0 3 * * * root sysupgrade
Maybe you meant “syspatch” there?
Syspatching via cron is questionable - Some of the patches wont be loaded until
the box is rebooted.
I
On Fri, Feb 16, 2024 at 12:10:18PM -0800, Lyndon Nerenberg (VE7TFX/VE6BBM)
wrote:
> At work I manage a herd of a dozen OpenBSD machines. We "upgrade"
> by perforing a full network install.
+1
All of our servers are upgraded the same way - fresh install, and
restore the configuration and user da
Kevin Williams writes:
> The main use case I see for this is to manage a fleet of more than 10 or
> so machines/VMs/instances. rdist or a package such as Ansible could
> manage the crontab and possibly search announce@ on marc.info for
> keywords to hold off on the upgrade.
Blind updating out o
, b...@fea.st wrote:
So I was curious, am I the only one using automatic OS updates
in cron to keep the fish fresh and the bits dust free?
0 3 * * * root sysupgrade
And this saves you what, ten keystrokes a day?
Possibly hitting a bad moment to update blindly?
> On 2024-02-15, b...@fea.st wrote:
> > So I was curious, am I the only one using automatic OS updates
> > in cron to keep the fish fresh and the bits dust free?
> > 0 3 * * * root sysupgrade
And this saves you what, ten keystrokes a day?
Possibly hitting a
On 2024-02-15, b...@fea.st wrote:
> So I was curious, am I the only one using automatic OS updates
> in cron to keep the fish fresh and the bits dust free?
>
> I think I read somewhere that it's not recommended but I'm not
> running a server so it seems like a good ide
On 15 February 2024 19:12:11 CET, b...@fea.st wrote:
>So I was curious, am I the only one using automatic OS updates
>in cron to keep the fish fresh and the bits dust free?
>
>I think I read somewhere that it's not recommended but I'm not
>running a server so it see
, but then you wouldn't be running -current unless you
are aware of the risks. ;-)
On Thu, Feb 15, 2024 at 1:16 PM wrote:
>
> So I was curious, am I the only one using automatic OS updates
> in cron to keep the fish fresh and the bits dust free?
>
> I think I read somewhere tha
So I was curious, am I the only one using automatic OS updates
in cron to keep the fish fresh and the bits dust free?
I think I read somewhere that it's not recommended but I'm not
running a server so it seems like a good idea to me.
/etc/crontab:
# Example of job
21 matches
Mail list logo
