dCore Import Debian Packages to Mountable SCE extensions > General dCore Talk
Wifi.sh quirk?
Jason W:
Thank you PDP-8 for your testing and feedback. I will look into the udev files to perhaps see that wlan0 is used for the first wireless interface instead of other names.
PDP-8:
Note that I modified the original message to make the boot parameter a plural with an "s":
--- Code: ---net.ifnames=0
--- End code ---
Jason W:
I have been reading up on the predictable device names thing, and at least for now I like the idea about using net.ifnames=0 as a default boot parameter rather than editing udev files. I like to create extra data files or use starting scripts to modify existing ones when that is the only way. The boot code is simpler and more reliable as file contents in packages can change with new versions and can make package startup scripts or data.tar.gz incorrect with an update in the Debian repo.
PDP-8:
Well, this got me thinking - always dangerous. :)
Politics aside, I wonder if not using wifi.sh at all and using a more systemd/udev aware network manager would be the way to go with dCore and the debian/ubuntu repos.
Or, perhaps tracking a more classic distribution, like Devuan would reduce the dev workload and be more suitable for busybox init, wifi.sh etc etc. Apparently the "ascii" / aka stretch version of Devuan is close to being declared stable. I'm here for testing if that seems interesting.
Don't get me wrong - it may seem like I'm just trying to grab all the low-hanging fruit with dCore, but it's only because I find that TinyCore and dCore complement each other perfectly. Alike, yet different. :) I can't keep my hands off either one!
Jason W:
wifi.sh is good for including in dCorePlus or as available in the wireless extension, it is small and allows folks to get on the network. Just like in standard Tinycore. wifi.sh fits into the Tinycore/dCore concept as the default small way to get online with wireless.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version