Conversation
RIP ASBESTOS CC @7666 END OF AN ERA
1
0
4
@meso @7666 what happened this time?
1
0
2
@snacks @7666 he decomissioned the old servers i gotta set mitra up on the new oe
1
0
4
@meso @snacks this fat fuck had weeks lmao. i even made custom cloud-init deployable openb*d images so I could deploy them by CLI which took me like a week and a half to build and took over 100 garbage unit tests to ensure they come out of the oven right (3x what debian needs)
2
2
5
@7666 @snacks the spanish work ethic takes another victim
0
0
4

@7666 @meso @snacks also thats crazy. did you cook them from scratch? openbsd doesn't have a way of making cloud-init images right?

1
0
0
@pernia @meso @snacks it does support cloud-init using some open source scripts someone made. someone even made their own qcow2 images but i ain't trusting that.

i have to pull down an image, convert to a qcow2, and then have a little startup ramdisk embedded in the template to resize the disk on first boot to the full disk size because openbsd does not allow online resizing so not even the customer would be able to resize it themselves.
1
0
0
@7666 @pernia @meso freebsd and dragonflybsd seem to be the only ones with sane fs supprt somehow. You'd think having a usable file sysrem would be a high priority
1
0
1

@snacks @7666 @meso openbsd's filesystem is fucking shit. hopefully that'll change soon https://marc.info/?l=openbsd-tech&m=178948744271633

1
0
0
@meso @pernia @snacks ok but the fact that i can just fdisk a whole new partition table without shutting the machine down or unmounting root is pretty fuckin important over in linux land
1
0
0

@7666 @meso @snacks its very important anywhere and being stuck with a /var thats too little and unable to change because its wedged in between 5 brittle unresizable slices is complete bullshit. and you better hope your /home isn't fragmented and you can shrink+move it to get free space because thats what ur going to have to do with every single slice between /var and /home

0
0
0