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:
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?
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?
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?
Been wanting to try out netinstall. but sucks having wireless. wasn't so hard in virtual machine though. nice guide
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)
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
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.