sigcode

is this project linux only?

This comic strip is the second thing I visualize when I think of MAD magazine.

The first is the drawing of Alfred Newman's face.

It is interesting how different generations are seemingly cut off from different sets of information about the same subject.

Unless it fits in 512 bytes this is not a "kernel" but is just instructions to jump to another address, where there is more small bootstrap code that loads another program, maybe a bootloader that loads another program, maybe a kernel.

Those who multiboot Windows with some other OS that uses disklabels may notice that Windows expects to always be the first OS. Any other bootstrap code put into that first sector will be overwritten by a Windows install.

If it is only used as a "BIOS" then is it unreasonably adding the surface area for bugs and attacks? Is it much larger and more complex than legacy BIOS?

Is this trade-off proportional to the benefits it provides: obviating need to for developers to understand backwards compatibility?

What would be the negatives to this approach?

I have been doing this for many years and have still not found any.

Currently I prefer RO space embedded in the kernel for the "core" OS and mfs/tmpfs overlay for a RW, larger "additional" OS.

If RW portion crashes, the system falls back to the RO portion.

The issue is not simply privacy, it's control of the hardware.

You should not close apps because you may interfere with tracking your location and other data collection.

Data collection is necessary to enrich your "user experience". When we know what you want we can fulfill your every wish! Just say "OK, Google". It will be great!

The developers behind this crap do not hear from satisfied users. Because the truth is no one really cares about this stuff. They care about things like reception and battery life...

except for some nerds like the ones who comment on HN who can easily point out all the stupidity of these "business" models.

When users are like puppets on a string, helplessly dependent. When there are no alternatives, no competition. Is that a business? And I suppose shooting fish in a barrel is game of skill.

Oddly enough, Googlers read HN comments and frequently defend the company, speaking only for themselves of course. Why should they care that anyone sees Android for what it really is? Whining nerds do not count, right? So why pay attention to what they think?

If developers of Android and iOS had any respect, if they had a conscience, then they would not be usurping people's computing resources for their own ends. Sure, users will be oblivious to what is going on and they will not complain. That does not mean it's OK to do these things.

Some years ago, there was another fellow who wrote a set of NaCl utilities that were very simple, UNIX filters. While I was "scared of the code" because he's not a renown cryptographer (does he need to be?), I was thankful for a simple, working example. There really weren't any publicly available at the time.

I really appreciate when people share these self-learning projects.

I thought one of the motivations behind this library was that you did not need to be an "expert" to use it.

Edit: Ignore this. I was blocking AWS.

Are you sure?

Could it be the author just wanted a BSD licensed screen alternative or some other reason(s)?

"The keybindings are different" argument seems quite silly since you can easily change them to whatever you want. It's like when people say they will not use Lua because indices start at 1 instead of 0.

tmux may be thought of as an alternative, not a replacement.

Whether that's correct is an open question.

Example: If I start a build world in a screen window, then detach and later I want to get a "screen shot" or "screen grab" of the output without re-attaching, how do I do that?

Also, tmux's "clipboard buffer(s)", e.g., tmux loadb, tmux lsb, etc., seems a little more versatile than screen, but I'm open to suggestions from screen users how to do these things in screen.

Here's what I use in tmux for the Example:

   cat tt
   case $1 in
   ""|-b|-E|-S|-t)
   tmux capturep $@ 
   exec tmux showb $@ 
   ;;
   *)exit
   esac

  write(1, hello, sizeof(hello)-1);