| === chris14_ is now known as chris14 | ||
| === ch0ps3y is now known as Guest4810 | ||
| === ch0ps3y is now known as Guest4010 | ||
| === ch0ps3y is now known as Guest7135 | ||
| === ch0ps3y is now known as Guest9260 | ||
| === ch0ps3y is now known as Guest8621 | ||
| pvl1 | hey all, does ubuntu server 22.04 have an "expectation" for the dev path of a cloud seed disc? im mounting multiple iso's over a bmc (dont ask), it boots subiquity fine, but the os doesnt mount the second disc (sr1) where the cloud-init config files are | 13:58 |
|---|---|---|
| pvl1 | idk if i can swap the discs, or if that would make a diff in the first place | 14:01 |
| === ch0ps3y is now known as Guest9626 | ||
| dbungert | pvl1: I do similar things in qemu regularly, so I think that should work. I wonder what the difference is other than the bmc setup | 14:05 |
| pvl1 | hi dbungert i noticed in qemu, there is a distinction between mounting a drive and an disc/iso | 14:06 |
| dbungert | mmm, I'll check my setup, the see ISO may well be treated as a disc | 14:06 |
| dbungert | *seed | 14:06 |
| pvl1 | whats interesting is that snap tries to auto-import , idk what that means | 14:09 |
| dbungert | I *think* that auto-import is harmless, and indeed my setup is providing the seed ISO as a -drive | 14:11 |
| pvl1 | oh snap i think its workign but theres errors in my yaml syntax | 14:12 |
| pvl1 | looking thru the cloud-init logs im seeing it | 14:12 |
| pvl1 | weird bc journal/dmesg dont mention a mount, nor does it show up as a mount | 14:12 |
| pvl1 | i guess cloud-init at somepoint imports the data | 14:12 |
| dbungert | I believe cloud-init mounts it temporarily to obtain the data, then unmounts it when done | 14:13 |
| pvl1 | seems to be the case, sorry everyone false alarm | 14:22 |
| === ch0ps3y is now known as Guest6671 | ||
| Windy | is fwupd needed in EC2? I have a new 24.04 instance and it's using 11% of the memory. | 16:59 |
| === ch0ps3y is now known as Guest1212 | ||
| sdeziel | Windy: `sudo fwupdmgr get-devices` should tell you if there are devices that are update-able. I'm curious of the results you'll get on EC2 :) | 17:12 |
| JanC | fwupd should not run permanently also? | 17:13 |
| Windy | get-upgrades tells me that "Amazon Elastic Block Store" has no available firmware updates | 17:23 |
| Windy | but /usr/libexec/fwupd/fwupd is definitely at the top of the memory usage in htop | 17:24 |
| Windy | oh, sorry, ran 'get-devices' also which shows the EBS stuff, and a Xeon Platinum 8259CL CPU | 17:25 |
| Windy | the cpu is not listed as Updatable | 17:25 |
| JanC | "Amazon Elastic Block Store" is listed as "updatable"? | 17:25 |
| Windy | yep | 17:25 |
| JanC | interesting :) | 17:25 |
| patdk-lap | running it on mine just says, unsupported platform | 17:26 |
| JanC | I guess in theory you could use that sort of thing to load an OS-specific configuration to a virtual device or something like that... | 17:27 |
| Windy | patdk-lap: is that 24.04? can I ask which AMI? I grabbed the latest from https://cloud-images.ubuntu.com/locator/ec2/ last week | 17:27 |
| patdk-lap | no, this isn't 24.04 | 17:27 |
| === ch0ps3y is now known as Guest9132 | ||
| === ch0ps3y is now known as Guest5921 | ||
| === ch0ps3y is now known as Guest4688 | ||
| === ch0ps3y is now known as Guest276 | ||
| === ch0ps3y is now known as Guest1594 | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!