Quote:
Originally Posted by rkelsen
You run as root? :P
|
The browser 'root' is a crippled root. root in name only,
with capabilities dropped within a chroot, within a Xephyr
Real root (boot) is just Linux kernel (tracking 6.6 line at
present), busybox, framebuffer, ssh, framebuffer vnc viewer,
enough to wifi net connect and ssh or vnc. I have a local
(same laptop) squashed filesystem of a full gui desktop
(Fatdog, with chrome, libreoffice ...etc.) that I overlayfs
mount as though a headless system, and initiate vncserver
within that ... and then chroot/fb-vnc into that. When vnc
data flow is just via lo (local) its in effect the same as
connecting via Gb/sec lan speed, so vnc works really well.
No X or pulse ...etc. just framebuffer.
A nice feature of having a full gui desktop (chrome/libre/etc)
displaying via a framebuffer is that you can more easily
'bleed' onto the screen. For instance if in a terminal on
ctrl-alt-F3 with a full gui desktop on ctrl-alt-F2, then
a youtube video playing on ctrl-alt-f2 will bleed through to
the terminal screen - just size and position that video window
to fit in with the terminal screen. Or the other way around,
my clock and battery tray entries are framebuffer based, that
bleed through to the gui's tray. As is my battery low warning
a full screen overlay of a battery that I overlay into the
framebuffer, so even when in chrome a large 'transparent'
battery image flashes onto the screen every 10 seconds as a
warning that the battery is getting low.
And with vnc you can connect to pretty much anything as
alternative desktops, on my phone I have termux/X/ssh/vncserver
and otter browser that I can ssh/vnc into, or remote kvm/qemu
vm's that are set to serve their display via vnc. So I can
have linux, android, windows, mac gui desktops all available
concurrently, yet the boot system is only a 16MB single
vmlinuz file, with all modules/firmware and initramfs built in
(boots in a second, from a usb that once booted is removed).
Top right of image battery and clock are framebuffer, as is the
battery image that is just a simple raw image created using
dd if=/dev/fb0 of=batt.raw ... when just a battery image was
visible on the framebuffer, that is then xor'd onto the framebuffer
at intervals whenever the battery level is low.