Kevin Chadwick wrote on Tue [2021-Feb-16 12:52:42 +]:
> On 2/15/21 2:14 PM, Ed Ahlsen-Girard wrote:
> > I am confident that I can speak for for ... a non-zero number of
> > people who use sysupgrade the way it says to on the box and would miss
> > it if it went away.
>
> +1
>
> Even t
On Tue, February 16, 2021 1:16 pm, Mitch K. wrote:
>
> I've been unaware of sysupgrade until now. Looks like it was introduced
> in 6.6.
>
> I've done several dot release upgrades manually. The process is
> straightforward and
> well-documented, like the rest of OpenBSD. It took me ~15-30 minutes p
On Mon, February 15, 2021 11:14 am, Ed Ahlsen-Girard wrote:
> I am confident that I can speak for for ... a non-zero number of
> people who use sysupgrade the way it says to on the box and would miss
> it if it went away.
>
+1 . Its simple to use, stable, convenient, luckly will bring more p
On 2/15/21 2:14 PM, Ed Ahlsen-Girard wrote:
> I am confident that I can speak for for ... a non-zero number of
> people who use sysupgrade the way it says to on the box and would miss
> it if it went away.
+1
Even though it is a little surprising that some people don't realise how easy it
is
On 2/15/21 7:21 PM, Judah Kocher wrote:
Hello Theo,
I never for a moment intended to convey that anyone "owed" me support
of any kind for my outside-the-box use of this tool. While I don't
understand your vitriolic response to someone else's application of
your software for their own perso
On 2/15/21 6:23 PM, Luke A. Call wrote:
On 2021-02-15 09:33:03+, Ottavio Caruso
wrote:
On 14/02/2021 23:44, Theo de Raadt wrote:
When we get reports like this where people "touch the insides", both
Florian and I regret that sysupgrade ever arrived in the system.
We want to delete
> On Sun, 14 Feb 2021 16:44:37 -0700
> "Theo de Raadt" wrote:
>
>> You are outside the box, by changing tons of stuff.
>>
>> People who operate inside the box won't be able to help you.
>>
>> And it is even less likely when you are dishonest in the original
>> email. You claimed your sysupgrade us
Hello,
Does sysupgrade leave any kind of logging behind which could help me to
pinpoint why it is failing on one system while working on another
apparently identical system?
You should get emails:
Subject: hostname upgrade response file
Subject: hostname upgrade log
Subject: hostname rc.sysm
On Mon, Feb 15, 2021 at 12:21:11PM -0500, Judah Kocher wrote:
> Hello Theo,
>
> I never for a moment intended to convey that anyone "owed" me support of any
> kind for my outside-the-box use of this tool.
You couldn't be bothered to even send a dmesg or a copy of the script
with the first email.
On Sun, 14 Feb 2021 16:44:37 -0700
"Theo de Raadt" wrote:
> You are outside the box, by changing tons of stuff.
>
> People who operate inside the box won't be able to help you.
>
> And it is even less likely when you are dishonest in the original
> email. You claimed your sysupgrade use was com
Judah
> I did not and do not expect anyone else to solve my problem for me.
Your dishonesty is consistant.
We supply it all as software. You can study it and find your problem.
Blaming me solves nothing.
Hello Theo,
I never for a moment intended to convey that anyone "owed" me support of
any kind for my outside-the-box use of this tool. While I don't
understand your vitriolic response to someone else's application of your
software for their own personal use in a way you do not condone, you are
On 2021-02-15 09:33:03+, Ottavio Caruso
wrote:
> On 14/02/2021 23:44, Theo de Raadt wrote:
> > When we get reports like this where people "touch the insides", both
> > Florian and I regret that sysupgrade ever arrived in the system.
> > We want to delete sysupgrade.
>
> If this is not ju
On 14/02/2021 23:44, Theo de Raadt wrote:
When we get reports like this where people "touch the insides", both
Florian and I regret that sysupgrade ever arrived in the system.
We want to delete sysupgrade.
If this is not just a provocative statement, +1 from me.
I've never liked unatten
On Sun, Feb 14, 2021 at 06:39:15PM -0500, Judah Kocher wrote:
> I had this nicely formatted when I sent it, but it seems to have been
> reformatted elsewhere in transit. Hopefully this helps but if not I will
> leave it be.
>
> On 2/14/21 6:27 PM, Judah Kocher wrote:
> > Thanks to each of you for
> On Feb 14, 2021, at 3:48 PM, Theo de Raadt wrote:
>
> We want to delete sysupgrade.
I would expect this would merely be a slight roadblock to people hell-bent on
doing things that aren’t documented or supported, while making release upgrades
harder for newbies lacking the urge to “customi
You are outside the box, by changing tons of stuff.
People who operate inside the box won't be able to help you.
And it is even less likely when you are dishonest in the original email.
You claimed your sysupgrade use was completely normal, but it isn't.
It is far from normal.
When we get repor
I had this nicely formatted when I sent it, but it seems to have been
reformatted elsewhere in transit. Hopefully this helps but if not I will
leave it be.
On 2/14/21 6:27 PM, Judah Kocher wrote:
Thanks to each of you for your replies,
Lesson 1: always get machines with remote console access
You are using sysupgrade -n, and then modifying the payload?
Let's be serious about this:
I think everyone should stop helping you, you are on your own because
what you are showing now is completely different from your original
simple claim that "sysupgrade does not work".
Or you should pay some
Thanks to each of you for your replies, Lesson 1: always get machines
with remote console access. It wil save the day some day and help in
diagnosing issues. Having remote console access would be sweet, but
unfortunately that goes far beyond the hobbyist price point I currently
have to work wit
On 2/14/21 7:02 PM, Judah Kocher wrote:
Hello folks,
I am having an issue with sysupgrade and I have had trouble finding
the source of the problem so I hope someone here might be able and
willing to point me in the right direction.
I have 6 small systems running OpenBSD -current and I hav
What are the permissions on the bsd.upgrade that's left behind?
If they are still +x then your issue is with the boot loader, maybe that
boot.conf otto suggested. If they are -x then the boot loader started the
install kernel but something went wrong.
On 14 February 2021 18:02:07 CET, Judah Koch
On Sun, Feb 14, 2021 at 12:02:07PM -0500, Judah Kocher wrote:
> Hello folks,
>
> I am having an issue with sysupgrade and I have had trouble finding the
> source of the problem so I hope someone here might be able and willing to
> point me in the right direction.
>
> I have 6 small systems runni
Hello folks,
I am having an issue with sysupgrade and I have had trouble finding the
source of the problem so I hope someone here might be able and willing
to point me in the right direction.
I have 6 small systems running OpenBSD -current and I have a basic
script which upgrades to the late
24 matches
Mail list logo
