You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
The ways in which Ubuntu manages to break things always baffle me. Their new 18.04 server installer UI is reporting a 1TB RAID volume (typical LSI RAID stuff) as 8TB. kernel/fdisk report the right size. Trying to find out how they managed to mess *this* up.
Found it. They multiply a 'size' attribute in sysfs, that is always in 512-byte units, by the logical block size (4096 in this case). https://github.com/CanonicalLtd/probert/blob/master/probert/utils.py#L239 … Still unfixed, which leads me to believe ~nobody is using their new server installer, or people would be complaining.
Nevermind the idea that if the logical_block_size file doesn't exist, they assume size is in *bytes* and don't multiply by anything. Whoever wrote this code just pulled this stuff out of nowhere, they didn't actually test anything but the 512-byte-disk case.
I personally don't use the new "live" installer; it froze our hypervisor when it tried to install with LVM (where I forced the installer **not** to do that), causing a full reboot on the remote hypervisor.
That sounds like a hypervisor bug if a guest managed to kill the host...
Speaking as somebody who works with servers and server folks for a living — nobody is using Ubuntu as as server.
We are... (not my choice)
subiquity? It doesn't work on PE R720s with the latest firmware. You know, one of the most popular server models among homelabbers. I had to use debootstrap and then finish the install LFS-style.
You can use the netinstall ISO, that doesn't use subiquity.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
