Tweaking preseed.cfg for semi-custom installs
I'm new to Debian (actually ALL *nix) and am doing a series of test installs from DVD on a laptop dedicated to this. The twofold purpose is to learn the ins/outs of Debian and decide just what I want in final installation. I have tweaked http://www.debian.org/releases/squeeze/example-preseed.txt to meet many of my requirements. There are three items I would like to set manually on each install: 1. User name - effectively I'd be using it to remind how I intended to use that test variation -- there may be 3-5 installs present on the hard drive. My assumption is that commenting out d-i passwd/user-fullname string Debian User would accomplish that. 2. Manually partition disk on each install 3. Manually select use of Lilo or Grub as boot loader - YES responsibility for strange errors will be my own ;/ I have no idea on how to accomplish the last two. TIA -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/510d1c91.7030...@cloud85.net
Debian installer build: failed or old builds
Debian installer build overview --- Failed or old builds: * OLD BUILD:armel Jan 28 08:08 buildd@ancina build_iop32x_netboot http://d-i.debian.org/daily-images/armel/daily/build_iop32x_netboot.log * OLD BUILD:armel Jan 28 08:10 buildd@ancina build_iop32x_network-console_glantank http://d-i.debian.org/daily-images/armel/daily/build_iop32x_network-console_glantank.log * OLD BUILD:armel Jan 28 08:13 buildd@ancina build_iop32x_network-console_n2100 http://d-i.debian.org/daily-images/armel/daily/build_iop32x_network-console_n2100.log * OLD BUILD:armel Jan 28 08:16 buildd@ancina build_iop32x_network-console_ss4000e http://d-i.debian.org/daily-images/armel/daily/build_iop32x_network-console_ss4000e.log * OLD BUILD:armel Jan 28 08:18 buildd@ancina build_kirkwood_netboot http://d-i.debian.org/daily-images/armel/daily/build_kirkwood_netboot.log * OLD BUILD:armel Jan 28 08:23 buildd@ancina build_kirkwood_netboot-gtk http://d-i.debian.org/daily-images/armel/daily/build_kirkwood_netboot-gtk.log * OLD BUILD:armel Jan 28 08:25 buildd@ancina build_kirkwood_network-console http://d-i.debian.org/daily-images/armel/daily/build_kirkwood_network-console.log * OLD BUILD:armel Jan 28 08:28 buildd@ancina build_orion5x_network-console http://d-i.debian.org/daily-images/armel/daily/build_orion5x_network-console.log * OLD BUILD:armel Jan 28 08:31 buildd@ancina build_versatile_netboot http://d-i.debian.org/daily-images/armel/daily/build_versatile_netboot.log * OLD BUILD:armel Jan 28 08:33 buildd@ancina build_ads_cf http://d-i.debian.org/daily-images/armel/daily/build_ads_cf.log * FAILED BUILD: amd64 Jan 30 01:17 debian-cd@pettersson sidamd64 http://cdbuilder.debian.org/cdimage-log/sidamd64 Totals: 105 builds (1 failed, 10 old) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1u1nwc-0005sl...@ravel.debian.org
Bug#698322: Include Dvorak Native Brazilian in list of keyboard layouts
Quoting Juliano Cesar (cetapsao...@yahoo.com.br): > Sorry to reply again, but it has the possibility of being included in the DVD > of Debian which is greater? Not really. The problem is not the size of the installation media, but the size and memory constraints of the installer itself. All possible funky keymap variations are available on the installed system *once installed*. It is therefore easy to switch keymaps when the system is installed. signature.asc Description: Digital signature
Failure to build netcfg....
I currently fail to build netcfg with my pbuilder/cowbuilder setup (the one that builds all other packages I build): Running suite(s): inet_mton inet_ptom netcfg_parse_cidr_address netcfg_network_address netcfg_gateway_reachable nc_v6_interface_configured /tmp/buildd/netcfg-1.105/test/mock_paths/test_nc_v6_interface_configured_simple/ip: line 6: cat: command not found 95%: Checks: 22, Failures: 1, Errors: 0 test/test_nc_v6_interface_configured.c:18:F:nc_v6_interface_configured:test_nc_v6_interface_configured_simple:0: Didn't find SLAAC make[1]: *** [test] Error 1 Any idea? "cat: command not found" is indeed interesting, isn't it? -- signature.asc Description: Digital signature
