Imho its not necessary for the average user, adding too much complexity.
For example, I tried to config gpsd to use another port, nothing would work; systemd quietly overrides gpsd's configfile and required additional systemd incantations to change what should have been easy. And the man pages are a mess
And journalctl makes me want to pull my hair out; just let me grep a regular file - discovering namespaces is a nightmare
Personally I think moving away from the hodgepodge of scripts, giving a consistent interface for people to use, extend, etc, is kinda necessary for the average user to have a decent system. It can often be complex to make things simple.
I'm also not sure how systemd could override a config file, because systemd does not write the unit files on a system. Wouldn't that be on the maintainer, distro, or other methods of getting the unit file?
It sets up the network for services, but it's been a minute since so I don't remember the specifics, just that I needed to make a new file in some deep folder to tell it to use a non-standard port.
To me its just more complexity, and not super consistent, which is fine for enterprise, or automation. I'm used to openbsd, regular shell init scripts go in /etc/rc.d, and my logs are in /var/log. Can't get much simpler than that, but i understand its limitations, and Linux is certainly more of a hodgepodge
Edit: found my notes, first was discovering the "gpsd" & "gpsd.socket" namespaces existence, then needing to do "systemd edit --full gpsd.socket" because without "--full" it makes an override file that didn't actually override anything...my note quality declined rapidly after that due to anger
Admittedly its taken me a long time to remember that the file is the last argument to grep, when so many other commands its the first. I'd guess common abuse is due to being easier to type cat x | than to dig up the man page
And also typing cat x to get a quick look at the file, hitting up, then piping that into another command and taking a look, hitting up, piping that result into a third command etc.
Sometimes, I'm wanting to copy text from the terminal, so "cat" is a better option if it's more than one page long or you just want to eyeball a fragment that you're going to type into a command.
It's that way so that you can grep multiple files with a single pattern. It would be odd for the pattern to come after the file arguments. It also allows the files to be optional so that it can grep stdin.
I really love that the source-extension icons are all different, and resemble the files contents - .c indentation, .h mostly linear, .s assembly instructions, ".o" bits
Yeah I'm very lost on what this is supposed to do -- "Summon your site" is quite vague. "see it live", like a demo? or is this actually published somewhere? Is it forever?
Desktop mode doesn't show any more information either
It does raise the question that if it is for developers, what exactly is being developed? Especially if its not representative of hardware that is available or desired; is there some advantage targeting a very particular chipset? This seems to be the only device using it (from what i could find briefly)
Ok, so your wan is 1gig, and your lan 2.5...handy but not much of a perk. Lets just call this an AP, which would clear up many issues people seem to have with it
It'd be handy for me: The fastest WAN pipe I can get is less than a gigabit while my LAN is still gigabit. I can't be the only person with this situation, wherein: If anything, then the 2.5-gig port is overkill.
I don't have any direct interest in the wifi radio that the box includes (I already have Mikrotik APs that I like just fine), except to configure it as a failover station-mode interface to use with a phone hotspot when the DOCSIS connection is on the fritz.
...which doesn't happen often at all, but it's annoying when it does happen. It's nice to be able to work around problems like that with OpenWRT.
Or 1 gig is underkill. My original reply was just pointing out that simply adding a 2.5g switch doesn't make it a 5 port 2.5g router, it makes it a 1 gig router with 2.5 internal, at best
It is indeed a strange choice to include only two interfaces, and then make each of them different speeds.
Realistically, the wireless side is unlikely to saturate a 1-gig pipe. If the 2.5g is used for WAN because the WAN can use that extra speed, then it's very likely that the LAN port becomes saturated. The configuration never really fits.
The best use I can come up with is this: A 2.5-gig managed switch and PoE with a tiny bit of VLAN magic does allow the OpenWrt One to be an access point+router that can be located in a spot that is good for RF propagation, with only 1 wire connected to it for both power and data. In this configuration, it route packets with up to ~1.25g of WAN (or perhaps more, if WAN is asymmetric).
But even though VLANs are fun and I wish more people knew how to use them effectively, that's so corner case that I'd never rationally expect anybody to actually use it that way. :) And it forces WAN traffic to contend with local WLAN traffic for that shared pipe, which introduces fun new ways for networks to slow down.
While glasses certainly sucked (I had a Samsung) I just couldn't stand that most content was essentially a technology demonstration -- throwing objects at the viewer for the sake of it, 4th wall be damned.
The Lion King is an example of good 3d imho, because they used it to improve the storytelling and art -- like adding depth to the water reflection of Simba
I see some kind of illumination from below/behind the display. Being from Gamers Nexus, I'd be shocked if it was manipulated. Maybe just a really steep sidelite
For example, I tried to config gpsd to use another port, nothing would work; systemd quietly overrides gpsd's configfile and required additional systemd incantations to change what should have been easy. And the man pages are a mess
And journalctl makes me want to pull my hair out; just let me grep a regular file - discovering namespaces is a nightmare