barebox - barebox master repository

	Commit message (Collapse)	Author	Age	Files	Lines
*	defaultenv-2 ifup: create network up state file for dhcp	Sascha Hauer	2012-06-30	1	-2/+5
\| \| \| \| \| \| \| \|	We store the 'up' status of a network device in /tmp/network/$interface. Create this file for dhcp aswell to prevent doing dhcp requests each time ifup is called. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
*	defaultenv-2: remove global.tftp.path	Sascha Hauer	2012-06-30	4	-9/+7
\| \| \| \| \| \| \| \| \| \|	This variable is set in /env/init/general and then used in /env/boot/* which is a bit confusing. Also it does not necessarily have to be a tftp path (could be nfs aswell). Use a local variable in the scripts using it instead to make the meaning a bit more clear. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
*	defaultenv-2: mount tftp server specified in $eth0.serverip	Sascha Hauer	2012-06-30	2	-9/+4
\| \| \| \| \| \| \| \| \|	This is always the tftp server specified in /env/network/eth0, this could be either the one returned from a dhcp request or a manually specified one, but in the end it's always the right one. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
*	defaultenv-2 ifup: Always overwrite eth0.serverip	Sascha Hauer	2012-06-30	1	-1/+6
\| \| \| \| \| \| \| \| \|	if serverip is specified, also overwrite eth0.serverip in dhcp case. This makes it possible to specify a different serverip when the dhcp server returns the wrong ip (because the DHCP might be a DSL router which does not provide tftp). Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
*	defaultenv-2: automount script: run mount only when ifup succeeds	Sascha Hauer	2012-05-23	1	-4/+4
\| \| \| \|	Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
*	Add next generation default environment template	Sascha Hauer	2012-05-18	31	-0/+538
	This adds a new environment template which aims to be more flexible and configurable. Instead of having mainly two scripts (a config script and a boot script) this template uses initscripts which control the startup behaviour and configuration. Also we have boot scripts in /env/boot which configure a single boot configuration. Additional boot entries can be added by board specific entries or during runtime by copying and editing a template entry. Some more helpers handle for example network interfaces which can now be brought up with 'ifup'. We use the automount feature to configure mountpoints together with the commands to bring up the devices behind these mountpoints. Optionally menu support is available which hides many details behind a nice looking interface. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>