Shakedown Social

0 posts0 participants0 posts today

Kevin Karhan :verified:<a href="https://equestria.social/@SweetAIBelle" class="u-url mention" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#LiveCD</a>" (or rather "<a href="https://infosec.space/tags/LiveUSB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LiveUSB</a>") distros like <a href="https://venera.social/profile/tails_live" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@tails_live</a> / <a href="https://fosstodon.org/@tails" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@tails</a> / <a href="https://infosec.space/tags/Tails" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tails</a> and <a href="https://infosec.exchange/@kalilinux" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@kalilinux</a> that that offer a comprehensive set of <a href="https://infosec.space/tags/tools" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" 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 noreferrer" target="_blank">#iPXE</a> for a <a href="https://infosec.space/tags/Diskless" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Diskless</a> <a href="https://infosec.space/tags/Administrator" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" 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 noreferrer" target="_blank">@ubuntu</a> / <a href="https://infosec.space/tags/UbuntuLTS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UbuntuLTS</a> <a href="https://infosec.space/tags/Desktop" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" 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 noreferrer" target="_blank">#OS1337</a>

Kevin Karhan :verified:<a href="https://hachyderm.io/@dalias" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@dalias</a> <a href="https://peoplemaking.games/@eniko" class="u-url mention" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#ARMv5</a> / <a href="https://infosec.space/tags/ARM11r7" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ARM11r7</a> / <a href="https://infosec.space/tags/RaspberryPi" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" 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 noreferrer" target="_blank">#iPXE</a> & <a href="https://infosec.space/tags/iSCSI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#iSCSI</a> for <a href="https://infosec.space/tags/diskless" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#documentation</a>.<a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OS1337</a> <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> <a href="https://infosec.space/tags/distro" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#distro</a> <a href="https://infosec.space/tags/development" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#development</a>

Kevin Karhan :verified:<a href="https://mastodon.monoceros.co.za/@uastronomer" class="u-url mention" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#KVM</a> + <a href="https://infosec.space/tags/Proxmox" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#Storage</a> and <a href="https://infosec.space/tags/Compute" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#diskless</a> (booting via <a href="https://infosec.space/tags/iPXE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#iPXE</a> from the <a href="https://infosec.space/tags/SAN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SAN</a>) and then mount the storage via <a href="https://infosec.space/tags/iSCSI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#iSCSI</a> or <a href="https://infosec.space/tags/Ceph" class="mention hashtag" rel="nofollow noopener noreferrer" 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 & it's I/O options...</li></ul>Did a bigger project (easily 8-digits in hardware, as per MSRP) where a Employer/Client did <a href="https://infosec.space/tags/CloudExit" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CloudExit</a> amidst escalating costs and <a href="https://infosec.space/tags/ROI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ROI</a> being within quarters (if not months at the predicted growth rate)...

Kevin Karhan :verified:<a href="https://mastodon.de/@the_moep" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@the_moep</a> Again: I've not tested / used / installed it yet so I can't formulate an educated opinion beyond: "Will keep it in mind as an option" ...<ul><li>I don't want to discount it, I'm just very wary of recommendations, as those have backfired on me, with <a href="https://infosec.space/tags/PorteusKiosk" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PorteusKiosk</a> currently sadly "<a href="https://infosec.space/tags/Enshittifying" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Enshittifying</a>" in a <a href="https://infosec.space/tags/grsecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#grsecurity</a> /#RedHat - Style by subsequently <a href="https://infosec.space/tags/paywalling" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#paywalling</a> even the most basic functionality and me having just gotten confirmation that basic functions like "<a href="https://infosec.space/tags/diskless" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#diskless</a> clients" have been silently axed.</li></ul>

Recent searches

Search options

Administered by:

Server stats:

#diskless