@samirx Granted AFAIK @tails_live / @tails / #Tails does some #signature and #Checksum checks to enshure it's integrity, as anything but the seperate #PersistentStorage partition is mounted #ReadOnly...
@samirx Granted AFAIK @tails_live / @tails / #Tails does some #signature and #Checksum checks to enshure it's integrity, as anything but the seperate #PersistentStorage partition is mounted #ReadOnly...
@dalias @eniko Personally, I'll sooner or later have to engange the whole #ARMv5 / #ARM11r7 / #RaspberryPi architecture anyway with OS/1337.
But I know a #readonly - OS isn't practical and where it is people already use #iPXE & #iSCSI for #diskless setups!
/boot
on an SD card, and the rest could be on any USB mass storage device (i.e. SSD or even HDD)...That being said Raspberry Pi do have the key advantage of being by far the best in terms of #documentation.
@HoustonDog @hyakinthos OFC, and speed isn't even the problem as @OS1337 is quite smol, so stocking with the royality-free to implement #SPI-Interface may be an option.
Which is kinda sad as I'm shure there are many systems like #DigitalSignage that are somewhat tamper-proof and in the interest of lowering maintenance should be setup as read-only, espechally on cheap flash that has very few write cycles if not lacks wear-leveling and garbage collection...
@landley yeah, basically I'm looking for a stage 1 thingy that BIOS can see as bootable device and that allows to do the usual "yeet kernel+initramfs into ram and floor it".
Worst-case I could just look for some sort of #SATA-DOM / -Board that offers a hardware write protection or can do #readonly #Flash instead...
-- :please_boost:
:boost: :boosted:
Speaking of #ROMs for #ix86 / #amd64: Does anyone know a good way to implement something like #Linux in #ROM like the #Tandy #1000RL & #1000RLX did with #MSDOS & #DeskMate (as @vwestlife showed)...
I mean, it would be a way cleaner setup to boot OS/1337 to than booting a #CDROM?
Ideally something that can take #BIOS-style ROM Chips that one can put on a board without write-enable connected so they're read-only!
Still having like a #minimalist #Linux distro in Boot-ROM would be nifty, espechally when it comes to making a #SecureComputing "#SSH #Terminal"...
(I don't expect something like a PCI(e Mini)Card but I'd not be against it!)
Wayback Machine Back Online After Last Week’s Cyberattacks #internet #internetarchive #news #online #readonly #waybackmachine
https://www.lowyat.net/2024/335016/wayback-machine-back-online-oct-2024/
In fact I'd love to see someone actually implement @OS1337 as a #BootROM [or like a #readonly - #eMMC for #ThinClient if not #EEPROM] so it can be the fastest booting #Linux machine...
One of the most fundamental yet little-known features of FreeBSD is its ability to be used in read-only mode very easily. By installing the system on a UFS file system, you just need to modify the fstab file, change "rw" to "ro," and reboot. On the next boot, the system will automatically create mount points in RAM for the main directories (/tmp, log, etc.), and it will run perfectly.
This was the main reason why, many years ago, I chose FreeBSD for almost all my embedded systems. Even today, on my Raspberry Pies, I keep the SD cards in read-only mode and use external storage in read-write mode. This ensures that, in case of an unexpected poweroff, the system will come back up, and there will be no wear on the memory card.
My #Linux #partition somehow became #read-only. Now I have to fix this… somehow
#Fedora #Help #KDE
@kuf so much important climate science needs #semantifying - making it so you can ask questions of the content as to being #readonly - here is a recent example US Plan for Energy Decarbonisation - guess what - just one big PDF Blob - #nomorepdfblobs heh? https://mastodon.social/@Snoro/111251795055220455
@thelinuxEXP with #immutable #linux #distros, users cannot uninstall or replace default applications because they are installed as #readonly. For me, this is a limitation not a feature and thus I prefer #tradotional linux distros in order to customise my desktop environment to my liking.
As my #weekendCodeProjects often are web-based, I have to debug #JavaScript code that was written by an amateur (me) on a regular basis.
My N=1 sample indicates that Javascript’s variable-scoping is responsible for ~80% of issues with the code. The rest is weird type-scoping bugs and the author (again, me) trying/failing to be clever.