HN user
Not the OP, but if they mentioned they did it from Termux you can install an X server and a full desktop browser like Firefox either directly or via a chroot/proot "container" via for example proot-distro [0].
I'm using VictoriaMetrics (VM) to store basic weather data, like temperature and humidity. My initial setup was based on Prometheus however it seemed very hard to set a high data retention value, default was something like 15 days if I recall correctly.
Since I would actually like to store all recorded values permanently, I could partially achieve this with VM which let me set a higher threshold, like 100 years. Still not 'forever' as I would have liked, but I guess me and my flimsy weather data setup will have other things than the retention threshold to worry about in 100 years.
Would be nice to learn the reason why an infinite threshold is not allowed.
3 dB would be halving/doubling. With 10 dB, you would get a ratio of 10x.
As a fellow alternative Ubuntu user, one additional difference is the LTS support schedule which is shorter for Ubuntu alternatives. For example, Xubuntu 24.04 is supported until 2027, while Ubuntu 24.04 is supported until 2029.
Interestingly, as I understood it, when a release such as Xubuntu goes out of support it does not stop getting updates that are not specific to that respective flavor, so in a way you still have some indirect support, but feels a bit like a gamble.
One nice benefit for optical media is that it's hard read only by default. This makes it easy to ensure the install media does not get corrupted by overwrites or malware.
They mention Zen 2 and 3, any info on Zen 1? Would it simply apply as well?
For some cars, getting to reverse requires to press down the shifter and then shift to the same position as 1st. I think this scheme would not work in such cases.
That's a good list of reasons, however it seems the biggest concern is if you run a dedicated DNS service on your network.
For a simple home network setup, as long as naming conflicts can be managed, it looks like mDNS is quite handy.
On a side note, I find .local to be best suited for the purpose, since from the language perspective it's easier on international users than .localhost
The newly proposed .internal comes close, but .local still looks more semantically flexible or maybe this is a cognitive bias of mine.
They list under hardware requirements "a powerful graphics card with at least 6 GB VRAM is recommended. Otherwise generating images will take very long"
Does anyone have any idea what would very long mean on a 4GB VRAM card?
After more than 15 years of average default Ubuntu user, I also had to move, in my case I went to OpenSuse Tumbleweed (TW).
While there were a lot of Ubuntu changes over the years, that I managed to adapt to, this time I realised it was too much work on my side as a user:
- for snaps, since I have data spread across different mounts, I had to apply some bindfs cludge to address the hardcoded paths that snaps get access to.
- for Gnome I got tired of having to install all kinds of 3rd party extensions for basic UI features like right click actions.
Debian or derivative would have been my initial choice too, I went with OpenSuse because it's got a strong developer backing and very responsive update schedule, it's a rolling release which means that it has quite new packages but also if updates break it, you can quickly revert it with snapper. Some downsides to consider are that this is not a Debian derivate so, while most guides on the Internet can be 'ported' to OpenSuse it's a bit more involving. That said they also feature quite some good docs, so many common scenarios are covered.
PS I know you can get the same Gnome on OpenSuse, but the upside is that one has access to more recent alternative DEs, which can replace Gnome on rolling releases.
Piling some more alternatives, a fork to snapdrop:
From the author: https://github.com/schlagmichdoch/pairdrop#differences-to-sn...
I've been doing just that with a Raspberry Pi Zero W and a USB ethernet adapter. The eth adapter is set to dhcp, and the wifi sets a hotspot. The wireguard adapter is routed/from to wifi with firewall rules. I even tested the Pi plugged to a powerbank and it still works.
Not OP and certainly not in the anti-IPv6 camp.
I'm wondering though: could you build a case that under IPv4, a misconfigured NAT would only result in lost connectivity for nodes behind the router, while for IPv6 a misconfigured firewall and worse triggered through a vulnerability, would then result in protected nodes being exposed?
I know NAT-PMP (port mapping) vulnerabilities exist, allowing external actors to set port mappings to hosts behind NAT, but this seems a bit harder to exploit than a bypassed firewall.
I use this on Windows because of the dual pane layout which allows me to easily move/copy files around, but also do other nice stuff like file diffs, though probably other apps out there can also do these things. It's also preety snappy when dealing with zip archives unlike Windows file explorer.
To be noted this app is also available on Android, comes in very handy and it also has plugins for network storage shares such as SMB. I got bitten in the past by other file managers on Android that turned into adware infested cesspools.
You probably need to look into disabling the Android phantom process killer. I had a similar issue and could not get DEs such as XFCE running for a long time and after the fix it was smooth sailing.
There are meanwhile quite a few Google references, the one I used at the time is referenced on this comment in the issuetracker: https://issuetracker.google.com/issues/205156966#comment52
How do you handle security updates? Can these be done separately?
Or if you're confident enough in your macro definition you can do C-u 0 C-x e to repeat until it reaches the end of the buffer.
I had some good experience with Asus MiniPC P50 - also 8 cores, Ryzen. I noticed it was barely audible while running with a VM active.
As others have already mentioned the Lattice ice40 family is supported by OSS chains through project icestorm [0].
There were some nice boards floating around though you may have to watch out for supply chain issues still plaguing this market. Examples:
- icoboard: has the 8k LUTs chip, comes with soldered PMODs[1], if you get it watch out as you either need a RaspberryPI with GPIOs soldered to program it, or you purchase their USB FTDI interface in addition. See: http://icoboard.org/
- iCEBreaker, comes with the 5k LUTs chip, has the USB-FTDI interface built-in, but you need to solder the PMODs yourself. See: https://www.crowdsupply.com/1bitsquared/icebreaker-fpga#prod...
You are correct, at least for US, for reference see: https://en.m.wikipedia.org/wiki/Commercial_Advertisement_Lou...
Important takeaway from the linked article: "No specific penalties are given"
So there is a regulatory framework and, as the article describes, compliant technical means should be in place for devices sold in the respective market.
The open question is, how will this be applied in practice as well as how will this extend to radio and why not, to online services such as streaming platforms?
I think containment for such organisms could be more challenging beyond the Jurrasic Park movie plot. For example would we also have to account for side effects such as horizontal gene transfer[0]?
[0] https://en.m.wikipedia.org/wiki/Horizontal_gene_transfer
Interested to know if anyone can share what sink devices they use to drive the external display? My intention was to achieve something similar via VNC/nx and use a RaspberryPI ZeroW driving a TV via HDMI input.
It depends. As a counter example think of Scientific Linux [0] which was also an RH clone supported by Fermilab and CERN. It eventually got replaced by this "obscure" distro called CentOS.
One example would be the Gigabyte Brix line. These barebones start at around 70€ and you get a 4W Celeron 2C/2T, USB3, GB Lan, WiFi, VGA and HDMI output. You need to add RAM to the bill but you could easily find a matching 4 GB DDR4 stick for under 15€. You also need storage but thats also needed for the Pi. So you're starting at 85€ with this mini-pc. Still you need to figure out if it matches your application needs, like if you need to interface with hw via GPIOs etc.
Maybe I misunderstood the requirements, I thought that in order to run containers a user has to belong to the lxc/lxd group. Once they belong to this group they can spawn a privileged container, which will indeed be run under root, but this effectively makes the user root too. Is there any other way for a non-root user to be limited to only unprivileged containers or have I misunderstood the requirements?
How do you all manage the security side for LXC containers? As I understand it, any local user allowed to run lxc containers can effectively spin up a root level access container on the host, example: run a privileged container and mount / inside the container? Is there anyway to mitigate this?
Thinking of the Pi0, I assume you would need 2 usb cables and a hub: 1 cable goes to Pi's power usb port, 1 goes to the other usb port for connectivity, then both cables joined through a hub to the phone's usb port.
Since they mentioned proot, that won't require a rooted device, see: https://proot-me.github.io/
I was also able to get a decent Ubuntu distribution including a desktop environment running on a non-rooted device, even got Blender to render the popular BMW demo, though that took a while.
Interesting, the text on those scans is selectable, can anyone share how this is done is it a custom font? It does not seem so as the same letter appears to be rendered differently showing printing/scan artifacts. Maybe some styling?
Can you share what your experience with implementing IPoIB with used gear was? I'm asking mainly because I actually got interested recently with such setups however I got rather discouraged by the driver support.
As an example here is the driver page for Mellanox, now owned by Nvidia, since they are a major Infiniband equipment supplier: https://network.nvidia.com/products/infiniband-drivers/linux...
It seems that some decent support only exists for more recent generations. The older ones like ConnectX-3 or earlier, which typically show up on ebay are either not supported any more or maybe available for older kernel versions and soon to be EOLed.
So do I understand it correctly that to use such adapters one has to actually downgrade to an older kernel version?
Or is there some basic support in the latest Linux kernels for older generations still?