|
An oracle product? A mess? Never. Never.
|
#
¿
Apr 3, 2019 03:22
|
|
|
|
| # ¿ Apr 24, 2024 23:21 |
|
|
Takes No Damage posted:Are there any cool and good distros that are roadmapped to continue supporting 32bit? I've been putting Lubuntu on all my old hardware for a while now, and just tried installing 18.10 on a hand-me-down Toshiba laptop I just inherited. But it seems that 32bit, while claimed to be supported for this release, is a bit busted (at least on this particular hardware). Additionally, they've announced that they're sunetting i386 from 19.04 forward. I could reinstall 18.04 with is LTS until 2021, but after that I'm in the wind. What's your motivation for staying purely x86?
|
|
#
¿
Apr 9, 2019 01:47
|
|
|
mystes posted:Your laptop isn't going to have a 32 bit processor in 2019. Even if it came with 32 bit windows because it only has 2gb or ram and even if it only has 32-bit UEFI it will still run 64 bit linux fine. Unless the machine he got is that old, which scares me 
|
|
#
¿
Apr 9, 2019 17:25
|
|
|
Hollow Talk posted:Everything newer than the Core 2 supports x86-64, as do some older things. This should be fine. True. I picked up a cheap Lenovo Thinkpad with Quad AMD for like $90 for my InfoSec class, and its fully x86-64, and fully VTd comliant.
|
|
#
¿
Apr 9, 2019 21:33
|
|
|
VostokProgram posted:Bit of a strange question but, if I built a computer without a GPU what could I do to actually install and configure Linux on it? Obviously once the network is up you can ssh in and do whatever but how do you get it to that point? On an embedded board with no screen I would connect to a serial port to use the shell, can I do something similar on a PC? http://www.sundby.com/index.php/install-ubuntu-16-04-with-usb-stick-and-serial-console/ Built out PfSense boxes via this method. As long as your BIOS is set to boot off whatever is plugged in, it should work.
|
|
#
¿
Apr 26, 2019 19:16
|
|
|
apropos man posted:Interesting. Thanks. https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/networking_guide/ch-configure_network_bridging
|
|
#
¿
May 24, 2019 14:51
|
|
|
|
| # ¿ Apr 24, 2024 23:21 |
|
|
other people posted:When a NIC driver loads, kernelspace assigns a name in the format ethX where X is the lowest currently unused number. The kernel is inherently stateless and there is no guarantee drivers will always load in the same order so the kernel-assigned ethX names cannot be expected to be consistent across reboots ( though if you only have one interface or they all use the same driver it probably will be 99% of the time). So for consistency, an OS must havr some userspace component to rename the interfaces when they appear. For most (all?) current distros this is some set of udev rules/scripts/helpers. net.ifnames is a setting recognized by systemd-udev to enable/disable the enoX/ensX/enpXsY style naming; it means nothing to the kernel itself. Most distros seem to have persistent-net enabled in udev, especially Server distros.
|
|
#
¿
May 24, 2019 18:14
|
|