101010.pl

Kevin Karhan :verified:<a href="https://equestria.social/@SweetAIBelle" class="u-url mention" rel="nofollow noopener" target="_blank">@SweetAIBelle</a> very nifty...<ul><li>Personally, I wish there were more "<a href="https://infosec.space/tags/LiveCD" class="mention hashtag" rel="nofollow noopener" target="_blank">#LiveCD</a>" (or rather "<a href="https://infosec.space/tags/LiveUSB" class="mention hashtag" rel="nofollow noopener" target="_blank">#LiveUSB</a>") distros like <a href="https://venera.social/profile/tails_live" class="u-url mention" rel="nofollow noopener" target="_blank">@tails_live</a> / <a href="https://fosstodon.org/@tails" class="u-url mention" rel="nofollow noopener" target="_blank">@tails</a> / <a href="https://infosec.space/tags/Tails" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tails</a> and <a href="https://infosec.exchange/@kalilinux" class="u-url mention" rel="nofollow noopener" target="_blank">@kalilinux</a> that that offer a comprehensive set of <a href="https://infosec.space/tags/tools" class="mention hashtag" rel="nofollow noopener" target="_blank">#tools</a> and benefits for users.</li></ul>Ideally with some nifty tools (compareable to Tails' <a href="https://infosec.space/tags/PersistentSotrage" class="mention hashtag" rel="nofollow noopener" target="_blank">#PersistentSotrage</a>) to allow mounting local/remote storage as <code>$HOME</code> and potentially leverage <code>toram</code> as boot option.<ul><li>Bonus if that works via <a href="https://infosec.space/tags/iPXE" class="mention hashtag" rel="nofollow noopener" target="_blank">#iPXE</a> for a <a href="https://infosec.space/tags/Diskless" class="mention hashtag" rel="nofollow noopener" target="_blank">#Diskless</a> <a href="https://infosec.space/tags/Administrator" class="mention hashtag" rel="nofollow noopener" target="_blank">#Administrator</a> Desktop to boot into.</li></ul>Certainly that "<a href="https://infosec.space/tags/RescueLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#RescueLinux</a>" part is mid- to ongterm goal of OS/1337 and I am working on it (abeit at a pace slower than I want to cuz 'things happen in meatspace' and those sadly require my full attention...<ul><li>Needless to say it's always good to have a nifty system at hand (worst-case I'd install <a href="https://ubuntu.social/@ubuntu" class="u-url mention" rel="nofollow noopener" target="_blank">@ubuntu</a> / <a href="https://infosec.space/tags/UbuntuLTS" class="mention hashtag" rel="nofollow noopener" target="_blank">#UbuntuLTS</a> <a href="https://infosec.space/tags/Desktop" class="mention hashtag" rel="nofollow noopener" target="_blank">#Desktop</a> on an external SSD/HDD and have that at hand) if one doesn't have their Distro on a hot-swappable / toolless replaceable drive anyway...</li></ul>Using <a href="https://infosec.space/tags/ArchLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#ArchLinux</a> is quite good because it makes it easy to get started and adapt said system as need be.<a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener" target="_blank">#OS1337</a>

Kevin Karhan :verified:<a href="https://hachyderm.io/@dalias" class="u-url mention" rel="nofollow noopener" target="_blank">@dalias</a> <a href="https://peoplemaking.games/@eniko" class="u-url mention" rel="nofollow noopener" target="_blank">@eniko</a> Personally, I'll sooner or later have to engange the whole <a href="https://infosec.space/tags/ARMv5" class="mention hashtag" rel="nofollow noopener" target="_blank">#ARMv5</a> / <a href="https://infosec.space/tags/ARM11r7" class="mention hashtag" rel="nofollow noopener" target="_blank">#ARM11r7</a> / <a href="https://infosec.space/tags/RaspberryPi" class="mention hashtag" rel="nofollow noopener" target="_blank">#RaspberryPi</a> architecture anyway with OS/1337.<ul><li>Tho given it's a minimalist Linux merely booting an initramfs and never doing any writes, there should be no indurance issues.</li></ul>But I know a <a href="https://infosec.space/tags/readonly" class="mention hashtag" rel="nofollow noopener" target="_blank">#readonly</a> - OS isn't practical and where it is people already use <a href="https://infosec.space/tags/iPXE" class="mention hashtag" rel="nofollow noopener" target="_blank">#iPXE</a> & <a href="https://infosec.space/tags/iSCSI" class="mention hashtag" rel="nofollow noopener" target="_blank">#iSCSI</a> for <a href="https://infosec.space/tags/diskless" class="mention hashtag" rel="nofollow noopener" target="_blank">#diskless</a> setups!<ul><li>THO AFAICT there should be an option to basically partition the system and only keep <code>/boot</code> on an SD card, and the rest could be on any USB mass storage device (i.e. SSD or even HDD)...</li></ul>That being said Raspberry Pi do have the key advantage of being by far the best in terms of <a href="https://infosec.space/tags/documentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#documentation</a>.<a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener" target="_blank">#OS1337</a> <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://infosec.space/tags/distro" class="mention hashtag" rel="nofollow noopener" target="_blank">#distro</a> <a href="https://infosec.space/tags/development" class="mention hashtag" rel="nofollow noopener" target="_blank">#development</a>

Kevin Karhan :verified:<a href="https://social.linux.pizza/@http" class="u-url mention" rel="nofollow noopener" target="_blank">@http</a> <a href="https://sakurajima.moe/@Rob298" class="u-url mention" rel="nofollow noopener" target="_blank">@Rob298</a> precisely that!<ul><li>Also most corp/org/edu networks only backup the <code>$HOME</code> directory and sometimes even allow syncing them across distros & keep them across version updates, so all the settings, addons and stuff remaib where they are: in said <code>/home/</code> subfolders!</li><li>In fact most places with a sizeable <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a>-<a href="https://infosec.space/tags/Desktop" class="mention hashtag" rel="nofollow noopener" target="_blank">#Desktop</a> landscape will just keep the /home/ directory on a redundant, <a href="https://infosec.space/tags/iSCSI" class="mention hashtag" rel="nofollow noopener" target="_blank">#iSCSI</a>-SAN and <a href="https://infosec.space/tags/netboot" class="mention hashtag" rel="nofollow noopener" target="_blank">#netboot</a> their <a href="https://infosec.space/tags/DisklessWorkstation" class="mention hashtag" rel="nofollow noopener" target="_blank">#DisklessWorkstation</a>|s via <a href="https://infosec.space/tags/iPXE" class="mention hashtag" rel="nofollow noopener" target="_blank">#iPXE</a>, as this way burglars stealing devices most likely end up with a locked-down machine (anything but booting the preset network targets won't work without admin password!) that is a paperweight to them and espechally no data, which is crucial when it comes to <a href="https://infosec.space/tags/ITsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#ITsec</a>, <a href="https://infosec.space/tags/InfoSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#InfoSec</a>, <a href="https://infosec.space/tags/OpSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpSec</a> & <a href="https://infosec.space/tags/ComSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#ComSec</a>. </li></ul>Cuz it's way easier to secure 1-5 server rooms than thousands of publicly accessible machines on multiple campuses.<ul><li>It's also a real godsent for technicians as they can just login / boot into a diagnostics system and quickly see what's wrong if a system has issues (if they don't already see it in their dashboard that collects logs, telling them they need to replace the CPU fan or clean a machine as it's overheating)...</li></ul>

Kevin Karhan :verified:Anyway, the short-term solution would be to setup some <a href="https://infosec.space/tags/iPXE" class="mention hashtag" rel="nofollow noopener" target="_blank">#iPXE</a> <a href="https://github.com/OS-1337/netboot" rel="nofollow noopener" target="_blank">"Internet Boot Server"</a> on <code>boot.os1337.com</code> <a href="https://ipxe.org/start" rel="nofollow noopener" target="_blank">to</a> download <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener" target="_blank">@OS1337</a> into RAM and boot that...Cuz that may be a quick and dirty option to get the latest version at boot... <a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener" target="_blank">#OS1337</a> <a href="https://infosec.space/tags/PXE" class="mention hashtag" rel="nofollow noopener" target="_blank">#PXE</a> <a href="https://infosec.space/tags/booting" class="mention hashtag" rel="nofollow noopener" target="_blank">#booting</a> <a href="https://infosec.space/tags/boot" class="mention hashtag" rel="nofollow noopener" target="_blank">#boot</a>

Kevin Karhan :verified:<a href="https://mastodon.monoceros.co.za/@uastronomer" class="u-url mention" rel="nofollow noopener" target="_blank">@uastronomer</a> it's something I.did implement in the past (abeit <a href="https://infosec.space/tags/KVM" class="mention hashtag" rel="nofollow noopener" target="_blank">#KVM</a> + <a href="https://infosec.space/tags/Proxmox" class="mention hashtag" rel="nofollow noopener" target="_blank">#Proxmox</a>, but the steps are similar enough):You can seperate <a href="https://infosec.space/tags/Storage" class="mention hashtag" rel="nofollow noopener" target="_blank">#Storage</a> and <a href="https://infosec.space/tags/Compute" class="mention hashtag" rel="nofollow noopener" target="_blank">#Compute</a> given you have a Storage-LAN that is fast enough (and does at least 9k if not 64k Jumbo Frames) and have the "Compute Nodes" entirely <a href="https://infosec.space/tags/diskless" class="mention hashtag" rel="nofollow noopener" target="_blank">#diskless</a> (booting via <a href="https://infosec.space/tags/iPXE" class="mention hashtag" rel="nofollow noopener" target="_blank">#iPXE</a> from the <a href="https://infosec.space/tags/SAN" class="mention hashtag" rel="nofollow noopener" target="_blank">#SAN</a>) and then mount the storage via <a href="https://infosec.space/tags/iSCSI" class="mention hashtag" rel="nofollow noopener" target="_blank">#iSCSI</a> or <a href="https://infosec.space/tags/Ceph" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ceph</a>.<ul><li>Basically it allows you to scale Compute and Storage independently from each other as they are transparent layers and not be confined to limits of a single chassis / IO options of a single node.</li></ul>

DansLeRuSH ᴱᶰ« <a href="https://netboot.xyz" rel="nofollow noopener" translate="no" target="_blank">https://netboot.xyz</a> lets you <a href="https://floss.social/tags/PXE" class="mention hashtag" rel="nofollow noopener" target="_blank">#PXE</a> boot various OS installers or utilities from a single tool over the network. This lets you use one media for many types of OS or tools. The <a href="https://floss.social/tags/iPXE" class="mention hashtag" rel="nofollow noopener" target="_blank">#iPXE</a> project is used to provide a user friendly menu from within the BIOS that lets you easily choose the OS you want along with any specific types of versions or bootable flags.You can remote attach the ISO to servers, set it up as a rescue option in <a href="https://floss.social/tags/GRUB" class="mention hashtag" rel="nofollow noopener" target="_blank">#GRUB</a> or even set up your home network to boot to it by default »

:debian: 𝚜𝚎𝚕𝚎𝚊 :opensuse:Does anyone here have a public ipxe/netboot.xyz server?I lost all my USB-sticks and I need to reinstall a machine<a href="https://social.linux.pizza/tags/askfedi" class="mention hashtag" rel="nofollow noopener" target="_blank">#askfedi</a> <a href="https://social.linux.pizza/tags/askfediverse" class="mention hashtag" rel="nofollow noopener" target="_blank">#askfediverse</a> <a href="https://social.linux.pizza/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://social.linux.pizza/tags/ipxe" class="mention hashtag" rel="nofollow noopener" target="_blank">#ipxe</a> <a href="https://social.linux.pizza/tags/pxe" class="mention hashtag" rel="nofollow noopener" target="_blank">#pxe</a> <a href="https://social.linux.pizza/tags/boot" class="mention hashtag" rel="nofollow noopener" target="_blank">#boot</a>

Recent searches

Search options

Administered by:

Server stats:

#ipxe