hi, I was wondering where can I find some ressources for starting with OmniOS ? The wiki wiki.omniosce.org doesn't seem reachable anymore

I'm looking for some resources about the basic stuff like how to check the listening ports or how to manage the services

Chat-ron, do you have previous Unix admin experience? Where are you starting from?

I'm a Linux a FreeBSD sysadmin

You'll find the FBSD experience more useful than Linux, IMHO.

have you checked out the left side menu at omnios.org ? There's some getting started info there.

Solaris-based OSs use svcs to manage services. It's like systemd only good. (It also pre-dates systemd by several years.)

yes I did check omnios.org, and the info are pretty limited on it

It's not as trivial to understand as /etc/rc.*, though.

svcs and svcadm are the commands you'll use a lot for service management.

as far as listening ports, I stick with my old friend lsof(1).

I see, svcadm looks really like systemd

other way 'round, but <shrug>

the file format is different and locations are different and SMF a bit less complex, IMHO.

SMF is...

yeah systemd can be complex when you want to make your own unit files, by saying that it looks the same I meant this about the command

I've never though of using lsof for checking listening ports, it seems a little overkill

I was more looking for a equivalent of netstat -nlp4, something like that

but it doesn't seem there is a -l parameter in the omnios netstat

I guess you could use -a and do some filtering on the output.

It's not something I've thought about.

I see x)

I've never used netstat -nlp4, looks interesting. TIL

I'm the kind of person who still uses ifconfig.

I think you still have to use it on IllumOS or *BSD :p

omnios has ... interesting ... ideas for network configuration tools.

dladm and friends still throw me for loops.

what do you mean ?

The equivalent to -p is -u.

ipadm and dladm to be specific.

Part of it is I'm daily touching and managing linux boxes but rarely need to do anything with my OmniOS file servers so always have to re-learn how to do things there.

same with my FBSD file servers.

yeah, that's the same for me

everytime I switch to FreeBSD I've to remind myself where are stored the files

Ironically, leenux is my least favorite of all the OSs I've ever managed, with the possible exception of early-years AIX.

but the others need less management xD

well, ok, pre-2.5.1 Solaris was pretty vile.

Well, file servers shouldn't need much touching.

make sure the filesystems are configured correctly, shared properly, and backed up as needed then leave them alone.

Should have mentioned patch regularly.

you still have to make the updates

beadm is nice that way.

beadm ? what does it do ?

it adm's your be's (be = boot environment)

"oops, this patch broke the world, I'll have to boot from the previous - working - one."

If you upgrade a new BE is created. You then can activate-and-boot the new one, and per ^^^ rollback if needed.

zfs snapshots are sooooo fantastic.

It's also great for trying new things as a developer (let's install new driver X on this BE...).

yes ZFS is nice but a little memory consuming

ALSO you can bring up a DEBUG kernel of your existing release BE in a new BE with OmniOS (and I think OI too).

My OmniOS (and FBSD) boxes are exclusively used for file service. Anything that makes that more reliable is win.

and I don't like the way the encryption is handled by him, I prefer luks for this

so the way you are talking about the BE let me think that the updates are kind of like with FreeBSD : pkg is only about the user apps, and for the system updates you have to use an other tool ?

pkg updates everything in OmniOS

it knows about the be stuff.

To finish the thought from earlier... I'm happy to throw RAM at ZFS for speed and reliability.

It's not like I'm using it for anything else.

That said, OmniOS is really focused at zones but I completely ignore that.

FreeBSD knows about BEs, too, governed by bectl(8), pretty similar to beadm(8). Omnios' default pkg+beadm integration is much cooler, though.

(IMHO)

cool. I've never noticed that (haven't looked).

TIL

And people say IRC isn't useful anymore.

man bectl | awk -v RS= /Summer/ | fmt -w 55

HISTORY

bectl is based on beadm(1) and was implemented as

a project for the 2017 Summer of Code, along with

libbe(3).

is there a way to enable the screen blanking ?

I've installed my OmniOS on an old laptop

I've only ever used it via text console or ssh. I've no idea what, if any, GUI it might have available.

(let alone how to use one.)

those red laptops were ... interesting.

In a 'my god, that's not a laptop, that's an aircraft carrier' kind of way, if nothing else.

What where they launching?

I'm not looking for a gui, but for enable the screensaver of the screen with the terminal

you have this on linux with xset

toasterson, they thought they were launching a new lucrative way to sell Solaris and hardware.

Instead it seems what they launched were shiny Ferrari Red boat anchors.

I meant the Aircraft carriers :)

I was too.

3 yrs ago, I bought an old Atom N270 netbook second-hand for 50 EUR, originally sold by "Aldi" (super-market chain here, aiming at the low-price segment), just to have a look at the installed MS Windows 10. After 72 hours of being not impressed, I nuked the Win10 to replace it with Solaris-10. Works nicely (no wifi, though) -- one cannot get more "consumer-grade" than that, I'd say.

cnet.com/reviews/acer-ferrari-5000-review perhaps

I remember Sun employees bringing them to Usenix conferences.

They were very easy to spot. Nothing else was quite that shade of red.

Those sparc voyagers were easy to spot, too :-)

Were they also Ferrari red? Maybe that's what I was thinking of.

It's been a long time and I've slept since then.

They were 17" or 19" or something really insane, IIRC.

ah, nope. I don't think I ever touched one of those.

(Yes, the Voyager does come with a bag to lug it around.)

so it can voyage

yay, inventory time.

Voyagers are pretty rare finds. Those Tadpole sparc notebook later became a bit more common.

I guess I'll be going to campus next Friday.

I remember hearing about the tadpole.

don't remember *what* I heard about it.

oh right! Those. en.wikipedia.org/wiki/Tadpole_Computer

rusted shut.

Yupp. Speaking of screen blankers: I am happy with the omnios console on my X220. I'd be even happier if it used the 1366x768 mode instead of the 1024x768 standard VESA size, then scaled by the box. Would there be any way to get to the native 1366x768 res?

Yes, you can put settings in a file, I'll look it up

Something like this: echo 1366x768x16 > /boot/conf.d/bootres

great -- let me try that right away!

The /boot/conf.d/bootres didn't work so far. I got some syntax? error msg during boot which flashed out of sight much too quickly. (Not trace of it in dmesg, /var/log, or /var/run). I found "boot_resolution=1024x768" etc. /boot/defaults/loader.conf though, and will tweak those.

That made the system to continue the kernel-load with 800x600 (the default loader_resolution).

Defining both loader_resolution and boot_resolution=1366x768 made everything to use 1024x768.

My best guess is that only std VESA BIOS (VBE) modes are accepted, and 1366x768 isn't one.