network setup discussion [was Re: microcore_v3.2rc1]

[maro]

Not a bug but merely a question that popped up: For TC users that can't use DHCP we have 'network' (which I've now called a GUI "wrapper" twice within the last 24h in some postings). What do we have on offer for the MC users (or the TC users without a running X server)?

Do we trust that they are aware of the three commands they need to execute (i.e. "ifconfig ... up", "route add ..." and "echo ... > /etc/resolv.conf")? Should this maybe be put somewhere on the FAQ page, or would it make sense to have a minimal script?

Such a script could prompt the user for at least the desired IP address and then offer default values for the remaining parameters (whilst allowing to overwrite these defaults). In the end a (temporary) script could be created that the user could re-use if the setup has proven to work (e.g. by moving to '/opt', inclusion in the backup and call from '/opt/bootlocal.sh').

Well, just a thought ...

[gerald_clark]

I don't see "average" users using MicroCore.
Do people advanced enough to customize a MicroCore system into something useful need
a script to setup a static IP?

[maro]

gerald_clark: That was exactly what I asked myself and then forgot to write down in the post.

I tend to agree that MC users probably have the ability to figure it out themselves. But I was more guided by the thought that in some cases (e.g. 'ab' vs. 'appbrowser') such a script is included. I'm certainly not suggesting that there is an urgent need, merely a possible "nice to have".

[Lee]

Hmm...

I use microcore exclusively although, I confess, I virtually always run a GUI (core elements + jwm + wbar) on top of it and until recently I would have been a little iffy setting up the network by hand.

I always use a static IP address but I used to always set it up by running netcardconfig (now "network") from the control panel until I needed to learn how to do it the under script control (to boot different physical hosts w/different static IPs from the same media, w/o user intervention).

So yeah, a cli version of netcardconfig would be "nice to have", but probably not a "need" for many users..

I'm not sure it was a great idea to change the name from "netcardconfig" to "network", though.


Edit - 2013-12-04: I finally got around to writing such a script.  I'll post it in the programming and scripting area shortly.  Lee