> Theoretically, given a sufficient networking configuration/VPN/etc., you could pull your smart card out of the Sun Ray in your university office, go home, and then drop your smart card into a Sun Ray at home and still have everything back where you left off.
They (well, the late models) had a Cisco compatible VPN client built in. Worked like a charm at my place of work in the late naughts.
Well, iSCSI is a standard, so chances are better that it's supported in a non-Linux OS, e.g. MS Windows. Years ago I booted a Windows (7, iirc) client that way, but gave up on it (too much hassle and performance limited by the network) when SSDs became cheap.
It is relatively easy to configure. Just install Linux after windows, and Linux will generally automatically setup a boot-selection screen for you. The installer should detect windows and even shrink the partitions for you.
You can install a prettier looking boot selection menu like rEFInd, but the default works just as well, and I think the mainstream distros all setup secure boot too. On my pc it was very easy, on my (8yr old) laptop I had to add some secure boot keys and the bios was very confusing, using terms that didn’t seem to match what they should have been.
My setup has worked almost entirely flawlessly and survived updates from both OSes. Only issue being “larger” windows feature updates putting windows back as the first OS in the list, but that happens maybe once or twice a year? And it’s a quick bios change to fix the order.
I've never had this experience dual-booting, neither with UEFI nor Grub. I've been using Linux for nearly 15 years, 13 of those dual booting. Dozens of systems from laptops to desktops. Windows would always purge the boot entries. I'd have to manually fix booting, constantly. This happened with Ubuntu, Arch Linux and recently NixOS and through all the Windows editions till 11. I had to install Windows for a lan party recently and lo and behold on the second day NixOS is gone from the boot list and unbootable. Nothing of value is lost when it gets purged, but it's a damn annoying tax to pay just to be able to play video games.
Luckily gaming now works well enough that the only reason to use Windows was gone. Well, apart from some online games played during lan parties.
The Debian installer is less than optimal for repartitioning.
The Linux NTFS resizing code also has a tendency to trigger data corruption. Not really Linux' fault, but it's a good reason to do partitioning from inside of Windows, which can be a pain already.
Another issue I've run into is Windows creating a very small (~300MiB) EFI partition that barely fits the Windows bootloader, let alone a Linux bootloader and kernel. You can resize and recreate the partition of course, but reconfiguring Windows to use a different boot partition is a special kind of hell I try to avoid.
For Debian and most other distros, secure boot isn't a problem. Installers are all using a signed, trusted-by-default bootloader.
There are some exceptions (some hardware from Microsoft doesn't trust the third party certificate used, for instance, and Red Hat Enterprise has their own root of trust if you opt into that), but they're very rarely ever an issue.
It's not unusual for lisp interpreters to lack TCO. Also the (relative) popularity of dynamic binding in Common Lisp reduced the opportunities for TCO.
There's not really a consensus in the parts of the CL community that I'm familiar with on whether or not code relying on TCO is idiomatic or not.
to answer that question we need to first look at the alternatives. whee else could session management go? and then we can consider the benefits and drawbacks of each approach.
if you are thinking of tmux then the problem here is that tmux is in itself a terminal.
to get session management away from the terminal it would need to be done in such a way that when the session tool connects the session it merely acts as a proxy or less, but does not interpret and then translate the signals that come from the session like tmux does.
this is not trivial, at least with the current way terminals work.
I‘m not sure I understand the question. Some people use similar kinds of sessions in terminal multiplexers such as tmux (is that what you have in mind?), but this leads to problems (interpretations of key sequences, etc.) that the Kitty solution sidesteps.
Er? social security covers more than just healthcare and the issue with on-line data in context of healthcare is patients' history, which i) is sensitive and ii) needs to be shared among health care providers.
Yes, but he only looked at Venus from the aspect of research which is missing half, or more, of the point of a Mars mission.
The advantage of Mars is that it is ( hypothetically ) acceptably compatible with persistent surface-based habitation. Not an easy life, certainly not compared to Earth, but more sustainable than balloons floating in sulphuric clouds.
Venus doesn't offer an 'alternative cradle' option unless we invent anti-gravity. Until then the emphasis will be on finding a way to improve human civilisation's resilience.
The point of the blog post is that while flying humans across the solar system to Venus so they can float in clouds of opaque sulfuric acid above a hellscape of certain death sounds and objectively is ridiculous, it's still easier and arguably more sensible than trying to send humans to Mars and back.
But, if our airship in the Venusian atmosphere finds nothing interesting (no life signs), then there’s not much more to do at Venus, because atmosphere is all mixed and all the same. Going to the surface, even for a day or two, is hard and very expensive.
OTOH Mars - that can be explored for many years, on the surface and below the surface. We might still find nothing, but it’ll take hundreds of years to be sure.
They (well, the late models) had a Cisco compatible VPN client built in. Worked like a charm at my place of work in the late naughts.