Is there anything I can do to get my PRs merged here? github.com/omniosorg/omnios-extra/pulls/extrowerk

Also can somebody confirm, my messages gets sent to this channel?

I am asking for review since long, but got no answer.

yes, i can read your messages :o)

it's just that most of this channel isn't hyper-active, i'm afraid

Oh, thanks for the reply, now I know at least my messages are clear and loud.

I am trying to update from 52 to 54 ... seems to have worked but wheh I reboot it is still 52

GrayGhost: what does beadm says?

On my side it says:

omnios-r151056d-1 NR / 17,00G static 2025-11-27 18:41

bootBK - - 119K static 2025-12-02 12:29

r151054 NR / 1.78G static 2025-12-02 12:39

so you are in 54 and the next boot will be also the same.

when I ssh in it say 151052

I assume you have attempted to run "pkg update -r -v" already. -r means recursive, so think about it before you run it.

weird

no I have not

-r updates all the linked zones, as far as I understand

but before that

please do the following:

# pkg publisher

and check the output. you can paste it here

 

PUBLISHER TYPE STATUS P LOCATION

omnios origin online F pkg.omnios.org/r151054/core

omnios mirror online F us-west.mirror.omnios.org/r151052/core

extra.omnios origin online F pkg.omnios.org/r151054/extra

extra.omnios mirror online F us-west.mirror.omnios.org/r151052/extra

oh, you have mirrors defined, for 52

you should delete them first.

how do I delete them ?

I would try : pkg unset-publisher us-west.mirror.omnios.org/r151052/core

but maybe it is pkg unset-publisher omnios and then pkg unset-publisher omnios.extra

you can simply unset all of them, later on it is easy to recreate them. You can find the correct publishers in the release notes.

Let me find a link.

Just try to unset all of them.

MAybe for the mirrors you need to pass -m aswell, i don't recall.

# pkg set-publisher -r -O pkg.omnios.org/r151056/core omnios

# pkg set-publisher -r -O pkg.omnios.org/r151056/extra extra.omnios

whith this commands you can set the correct publishers, so use any means to remove the old 54 and 53 ones.

In case you are in europe, I use the listed ones, they are really quick nowadays, no need for the us mirror.

now I have

PUBLISHER TYPE STATUS P LOCATION

omnios origin online F pkg.omnios.org/r151056/core

omnios mirror online F us-west.mirror.omnios.org/r151052/core

extra.omnios origin online F pkg.omnios.org/r151056/extra

extra.omnios mirror online F us-west.mirror.omnios.org/r151052/extra

you need to remove the old mirrors

let me check the manpage

can I go from 52 to 56 ...?

I went from 52 to 54, and from 54 to 56.

you can do the same, applying the correct publishers.

that is what I thought

but first let's find out how to remove the us mirrors

I am in the us

it that matters

the 056 announcement said you have to go via 054 if updating from 052.

then do that, but first remove all publishers.

like : pkg unset-publisher omnios

pkg unset-publisher extra.omnios

check if they are gone with : pkg publisher

they are all gone now ... had to also do without the estra a second time

if all is gone you should add the 54 publishers.

let me get the links

pkg set-publisher -r -O pkg.omnios.org/r151054/core omnios

and

pkg set-publisher -r -O pkg.omnios.org/r151054/extra extra.omnios

check the outut of the : pkg publisher

if you don't have time pressure the european server should be fine.

later on you can add the mirrors, if necessary.

PUBLISHER TYPE STATUS P LOCATION

omnios origin online F pkg.omnios.org/r151054/core

extra.omnios origin online F pkg.omnios.org/r151054/extra

looks good.

do you have any ipkg branded zones?

I don't think so

sudo pkg update -f -r --be-name=r151054

check with "zoneadm list -v"

is that correct ?

check first the ipkg zones.

hc@omnios:~$ zoneadm list -v

ID NAME STATUS PATH BRAND IP

0 global running / ipkg shared

zoneadm list -v shows the zone brand. you can ignore the global zone.

ok

the command you have posted earlier "sudo pkg update -f -r --be-name=r151054" is ok.

you can run it now

Good luck!

pkg update: The boot environment 'r151054' already exists.

do I have to delete it ?

then just "pkg update"

you have probably already created the snapshot

seem to be working :)

when it is finished .... init 6 ?

I always name my BEs like "r151054-last" to clearly identify this is the last one in that revision.

init 6 or simply reboot

somewhere I read that after an install you must init 6 and not reboot ... but what do I know ... not much

do you have physical contact with the server? is it near to you?

yes

then it is not important.

the guide says do *NOT* use "reboot now", because it will instruct the bootloader to load the kernel called "now" at the next boot.

reboot is safe.

init 6 aswell.

then I do it again with 56 ...or since 54 is long term I can stay with it ???

you can stay with it, if you want, or oyu can go to update to 56.

Is the publisher fast enough?

I have already updated to 56 on my NAS. works well.

We're running 054. No problems to report.

I haven't had any issue with 54.

Updated just for the keks and for fun.

thank you for the help ... or should I wait with that till it reboots :)

keks like "biscuit"

better to stay till it is successfully booted into the new env.

allmost done

so oyu have attempted to update your server earlier, as the snaőshot was already there. Did the update failed somewhere? Or maybe the mis-versioned mirror publisher somehow rejected your update attempts?

rebooting now

I already had a mis-versioned mirror before, unsetting them solved my issue. Hope this will fix yours aswell.

Ich drücke die Daumen!

I'll press my thumbs for you!

after your server comes up check the BE with beadm.

BE Active Mountpoint Space Policy Created

omnios-r151052 - - 68.65M static 2025-02-04 13:59

omnios-r151052l - - 3.80M static 2025-02-05 07:43

omnios-r151052av - - 3.14M static 2025-10-28 10:00

bootBK - - 119K static 2025-12-02 12:29

r151054 - - 4.64M static 2025-12-02 12:39

omnios-r151054ad NR / 2.72G static 2025-12-02 14:02

it came up with 54 :)

WOAH!

YOU JUST DID IT!

CONRATS! I wa shere fingers crossed all the time.

should I delete the 52's

Now it is your decision if you stays with the LTS or to update to 56.

I will think about it

you can, but you don't have to. Wait a bit, if you have enough space.

You can delete them the next monday or so.

chek first if everything is OK

I have lots of space two 4 tb drives and just me expermenting with a server

In case you have any pkgsrc zones, you should update them in the zones, as there was a new pkgsrc release in the meantime

but from your previous paste it seems you don't have any zones, right?

except the GlobalZone.

It appears to be working properly

Thank You for the help

Immer wieder gerne! Glad I was able to help you.

If I want to delete the 52's where will I find them ?

you can list, find and delete the BEs with beadm

beadm destroy <BEname>

beadm will simply list all the BEs

yes it does

it seems you are a newcomer in Illumos / Solarish world. If this is so, the OmniOS user guide yócould be useful for you. Consider to dive in

you are correct ... I will look at the user guide

not real new to linux ... but not very good at command line ... but learning

linux and solarish systems like OmniOS have lot in common, but also many differences.

one I noticed is the Ctrl R does not start a reverse search

in this terminal

ctrl shift R works :)

I personally like simple unixy systems better if I have to decide. However there is no simple systems nowadays. So If I need to decide I pick Solarish descendant Illumos, so like OmniOS.

possibly it dependy on your local and / or on your shell. check the used shell like "echo $SHELL"

I am unsing Linux mint lmde

with xfce

if your system uses some oldschool shell, you can fix it easily.

Welcome here then!

enjoy the upgrade to mature unix, GrayGhost! :D

We definetely need some omniOS stickers.

For your auto bumper ?

yeah, sure!

and random outside lanterns

and pub toilets

sure!

omniOS is using ksh shell ... ???

if "echo $SHELL" returns that, then yes.

You can change it. AFAIK bash is available in the base install. Check it with "which bash" first.

or you can switch to zsh aswell.

zsh is also a command line environment.

at my level it does not make much differance ... they are all close to the same

zsh is a bad choice IMO

it can emulate most other shells - badly

GrayGhost: just wait until you try the csh ;o)

Zsh is one of the best shells. I used to use tcsh on Linux, before Fish.

how so? i mean, it does a lot of stuff that does not really belong in a shell, similar to powershell.

It's highly configurable and at one point probably had more features than Bash.

It's got fancy prompts and a right-side prompt, too.

how many features does a command prompt need?

there are quite a few security implications in feature bloat, and performance *is* relevant.

that said, i will NOT try to convince you :)

I am attemting to change to bash .. with the chsh command ... not found

try usermod.

(e.g. usermod -s /path/to/your/bash GrayGhost)

tux0r I get invalid syntax with sudo usermod -s /usr/bin/bash

of course. because you did not add the user name.

thank now it worked :)

If you're having fun with chsh, wait until roles and profiles come up.

:D

learning VERY slowly

Kinda tough on this old brain

it's never too late for better software