How to: install Waldorf from the Debian netinstall

johnraff · 2014-04-16 14:20:21

Wireless settings lost after install
Using the unofficial "firmware" iso, you can do the Debian netinstall via wireless with no problem, but I found that when logging in to the installed cli Debian system the wireless settings you put into the installer have been deleted from /etc/network/interfaces. (I think a cable connection is OK.)

Two options:
1)

sudo nano /etc/network/interfaces

and add the wireless network id and passphrase needed:

allow-hotplug wlan0
iface wlan0 inet dhcp
	wpa-ssid <network-id>
	wpa-psk  <passphrase>

2)
At end of netinstall, just before rebooting:

Alt+F2
Enter
cd /target/etc/network
cp interfaces interfaces-installer
Ctrl+D
Alt+F1

continue to reboot
login

cd /etc/network
sudo mv interfaces interfaces-orig
sudo mv interfaces-installer interfaces
sudo ifup wlan0

I'm not sure which one to recommend.

Milozzy · 2014-06-18 12:39:41

I'm gonna try the netinstallation this weekend... Thanks Johnraff!

johnraff · 2014-06-19 11:06:36

Good luck Milozzy. Post here if you run into trouble.

alaskan-hippie · 2014-06-19 21:33:11

Hello all,

I contacted johnraff in a pm regarding a question about his script, and he requested the questions be posted here for others to benefit from:

My question:
How does the script pull up the large list of the many dozens of packages to install? In the pkgs-auto/manual/norecs is where I was assuming I'd find these packages listed, but I can't find it anywhere. How does your script generate this list of these packages?

His answer:
the answer is in pkgs-manual: cb-metapackage has a huge list of recommended packages which get pulled in, because apt is configured in Waldorf to install recommends.

Follow up question for john or anyone who knows:
Ones these packages are pulled in with cb-metapackage, are the config files preconfigured for the #! specifications, or do they come with default configs and then the script sets up the proper config files?

alaskan-hippie · 2014-06-20 00:39:22

Also, how complicated would it be to combine all the scripts into one? Is there any thing special that would be required in the script to allow for this?

johnraff · 2014-06-20 11:40:17

alaskan-hippie wrote:

Ones these packages are pulled in with cb-metapackage, are the config files preconfigured for the #! specifications, or do they come with default configs and then the script sets up the proper config files?

If you mean the user config files that set things like fonts, gtk themes tint2 setup and so on, then a set of files comes with the package cb-configs and gets put in /etc/skel . From there copies are put in new users' home directories by the script. In a normal #! install that job is done by slim, the login manager.

johnraff · 2014-06-20 11:43:04

alaskan-hippie wrote:

Also, how complicated would it be to combine all the scripts into one? Is there any thing special that would be required in the script to allow for this?

Originally I had everything in one script and there's nothing stopping you from doing that. I pulled all the various configurations into auxiliary files to make it easier for people to put together their own customized versions.

Milozzy · 2014-06-21 09:42:52

Done! All went exceptionally well!!

Thank you a lot johnraff!!!!

johnraff · 2014-06-24 10:49:56

Great to hear!

Milozzy · 2014-06-25 12:20:24

johnraff wrote:

Great to hear!

You can't even imagine how useful is your work.
As you could know, Waldorf installer doesn't support UEFI installation, while the Wheezy one does.
With the netinstall script I can install in UEFI mode and then obtain my precious #! without pain... I am really greatful

antsunrise · 2014-07-04 00:26:47

Been wanting to try out netinstall. but sucks having wireless. wasn't so hard in virtual machine though. nice guide

antsunrise · 2014-07-28 21:56:28

Trying this now on my new laptop. Hope all goes well. Pretty crazy that debian installer actually detects my wireless. That's a first.

geez. at the point where you choose what to install. no clue how to uncheck them. messed up both times. enough for today on that one

Last edited by antsunrise (2014-07-28 22:18:34)

Menschenkind · 2014-07-28 22:20:41

antsunrise wrote:

geez. at the point where you choose what to install. no clue how to uncheck them. messed up both times. enough for today on that one

Arrow keys to navigate, spacebar to check/uncheck boxes.

antsunrise · 2014-07-28 22:27:11

Menschenkind wrote:

antsunrise wrote:
geez. at the point where you choose what to install. no clue how to uncheck them. messed up both times. enough for today on that one
Arrow keys to navigate, spacebar to check/uncheck boxes.

That was my guess right after. Okay. Back I go.. thanks

johnraff · 2014-08-09 10:26:26

It was there actually:

post#1 wrote:

(Use up/down arrows to move, spacebar to toggle selection.)

smersh2 · 2014-09-16 13:58:19

Very nice script. But it behaves intermittently - one time I have request for password in the second request for input, but sometimes not (only in the end or in post-install script (after Waldorf installed))
Could not figure out why...
Anyway, my main question - Are you going to adjust this script, so it will be available when Jessie/Janice will be released ?

Thank for reply beforehand because it is very important for me - I am having problems with Wheezy/Nvidia card which I assume will be resolved in Jessie

johnraff · 2014-09-18 03:18:03

Hi smersh2 - the "sudo" command keeps its super-user privileges for several minutes after the first time you run it (I forget exactly how many minutes) so you don't have to enter your password over and over every time you use it. This means that if you used sudo just before running the script then it won't need your password at the start. However, during all the downloading and installing of packages it will probably time-out and need your password again to run the sudo commands that come at the end of the script.

I'll think about rewriting the script for Janice when it comes out. How difficult it will be depends on how much is changed in the underlying system. Anyway, it probably won't be for some months yet.

CrunchBang Linux

SEARCH

#51 2014-04-16 14:20:21

Re: How to: install Waldorf from the Debian netinstall

#52 2014-06-18 12:39:41

Re: How to: install Waldorf from the Debian netinstall

#53 2014-06-19 11:06:36

Re: How to: install Waldorf from the Debian netinstall

#54 2014-06-19 21:33:11

Re: How to: install Waldorf from the Debian netinstall

#55 2014-06-20 00:39:22

Re: How to: install Waldorf from the Debian netinstall

#56 2014-06-20 11:40:17

Re: How to: install Waldorf from the Debian netinstall

#57 2014-06-20 11:43:04

Re: How to: install Waldorf from the Debian netinstall

#58 2014-06-21 09:42:52

Re: How to: install Waldorf from the Debian netinstall

#59 2014-06-24 10:49:56

Re: How to: install Waldorf from the Debian netinstall

#60 2014-06-25 12:20:24

Re: How to: install Waldorf from the Debian netinstall

#61 2014-07-04 00:26:47

Re: How to: install Waldorf from the Debian netinstall

#62 2014-07-28 21:56:28

Re: How to: install Waldorf from the Debian netinstall

#63 2014-07-28 22:20:41

Re: How to: install Waldorf from the Debian netinstall

#64 2014-07-28 22:27:11

Re: How to: install Waldorf from the Debian netinstall

#65 2014-08-09 10:26:26

Re: How to: install Waldorf from the Debian netinstall

#66 2014-09-16 13:58:19

Re: How to: install Waldorf from the Debian netinstall

#67 2014-09-18 03:18:03

Re: How to: install Waldorf from the Debian netinstall

Board footer