There are ways to set the Pi up "headless" and then use VNC to export a graphical desktop over a network, but I think most are pretty fiddly and prone to network DHCP changes that require unwanted effort to make it work again. Even so, if you wish to try this with your nephew, see https://learn.sparkfun.com/tutorials/headless-raspberry-pi-setup
This school district in southern #NJ cancelled classes for three days last week, citing "Internet access" and "unauthorized third party". They didn't say whether there was a breach, or malware / ransomware, or even someone cracked their #Wi-Fi. I suspect that they'll continue to be closed-mouthed about what happened.
The other issue is that modern Web applications bloat up memory use. I'm not even sure that 8GB will be enough.
Several years ago, I had a desktop machine with 4GB of RAM. If I opened Chrome with around 8 #JavaScrippled tabs, it could freeze my X11 session or even force reboot the computer in about 8 hours. Even though I'm sure Chrome and Chromium have improved, they are probably still really heavy on RAM usage.
I didn't look at the price / MSRP, but as long as you're sure that OpenSuSE will install and that 8GB will meet your needs, you're probably not going to find anything that is clearly better unless you're almost willing to double the price. I'd say go for it.
Few people know about ad-hoc wifi mode. Ad-hoc #wifi lets devices in range talk to each other without an access point. You just all set your devices to the same network name and password and there you go. Sometimes DHCP and such can be a challenge; more on that in the next item. 3/
She had spent hours on the phone with the national support line over the last few days. It turns out that we have a branch office with IT about 30 minutes commute time from where she works (a lot closer and faster than coming here).
Since I did not get to troubleshoot, we don't know why it was not working before.
Notified IT at that field office to expect a visit.
Assuming they can get #FCC approval, the next iteration should support putting 'Device A' behind the GL-AR750S with the others. The router itself should be capable of connecting to another #Wi-Fi and allowing a device on the network to do the public Wi-Fi's login routine.
I dislike some of their defaults already: 1. Expects an Ethernet connection. To autostart Wi-Fi, you have to edit a couple of files (one to enable #Wi-Fi and disable #Ethernet, one to enter your Wi-Fi logon information). It should accept either connection by default and use a "wifi-config" program to set up the connection. 2. Defaults to hostname 'dietpi' instead of having you name your device as part of setup. 3. Apparently, 'root' and 'dietpi' users exist with same password ('dietpi') ... the change password step of the setup appears to give both accounts the same password. 4. This is common among nearly every GNU+Linux distro these days: I want my systems to use UTC timezone ... but where most distros use a 'locale' setting to set a local timezone, DietPi assumes I'm in London. It chose BST as the timezone.
The good. 1. There doesn't seem to be a lot of unnecessary junk installed. I'm using a 16GB microSD card, so I don't want anything that isn't needed for the chosen task. 2. Uses #Raspian / Raspberry Pi OS and #Debian repos along with its own, so most of what I might want to install is available. 3. DietPi-Survey is disabled by default.
Then I realized what happened. Two routers / #Wi-Fi access points. When The computer connects to the closer of the two, the #WSD port decides the printer is "offline", even though I can view the printer's configuration web page with a browser. Went back to reliable TCP/IP port and multiple jobs flowed out of the print queue.
It's been a few years since I had to replace WSD (Web Services for Devices) port monitors to make printers work. Putting this back in my toolbox.
@geniusmusing I never even knew that some grills are #Wi-Fi capable. If someone wants to track what I'm eating, they can talk to my bank. No need to give them a direct line to the grill.
@geniusmusing The routers at work are centrally managed by another agency, so no experience to recommend by. I know #sonOne is using a #Ubiquiti router with #Wi-Fi, but I don't know specifics.
@guizzy @moonman@shitposter.club I'm sure most of those don't even know they have a #VNC server running or don't even know it is accessible outside their networks. Perhaps they've got VNC as part of a virtualization system or built into some #IoT device they bought.
One of my sons installed VNC on his wife's laptop about 12 years ago, so he could support from another room. Within minutes after installation, he watched someone log in, download some malware, and install it on her computer. While some blame goes to his consumer grade #Wi-Fi router (and possibly him for not setting it up more securely; he's a lot more careful now), it was an important lesson for both of us: even your "private" network may have uninvited visitors, so you should set things up as securely as your users let you get away with.
So, yes, unless you can prevent all non-SSH connections, I'd never allow VNC on my network.