Bug#767432: main-menu: please give a way to change the frontend
Package: main-menu Severity: normal User: debian-accessibil...@lists.debian.org Usertags: a11y Hello, Depending on the input and output accessibility helpers used by the user, one frontend or the other will be more convenient, it would be useful to be able to change the frontend during installation. More specifically, a typical example is starting the installer with the speech synthesizer (with thus enables the text frontend, way more suited to speech synthesis), but only to start brltty by hand on VT2 with special options needed by the particular braille device to be used, and then one would like to switch the frontend to newt, which is more convenient with a braille device. AIUI, it shouldn't be hard to do, it would be a matter of restarting main-menu with the selected frontend. It could be a mere entry in the main menu, similar to the "change debconf priority". Samuel -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.17.0 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- Samuel sl - display animations aimed to correct users who accidentally enter sl instead of ls. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141030234958.ga18...@type.youpi.perso.aquilenet.fr
Re: Bug#762762: Updating isc-dhcp udeb to dynamically link bind (was: Bug#762762: nmu fixing bind issues)
On 20/10/14 01:09, Michael Gilbert wrote: > The new isc-dhcp is now uploaded. Please let me know how your testing goes. After the upload of bind9/1:9.9.5.dfsg-5, this does seem to be working well now in sid d-i. Thanks. Regards, -- Steven Chamberlain ste...@pyro.eu.org signature.asc Description: OpenPGP digital signature
Bug#767052: D-I : Sheevaplug : could not determine kernel flavour
On Thu, 2014-10-30 at 15:42 +0100, drEagle wrote: > Hi Ian, > > On 28/10/2014 20:38, Ian Campbell wrote: > > On Tue, 2014-10-28 at 04:08 +0100, drEagle wrote: > >> The kernel flavour is not detected. > >> Sheevaplug now use a dtb file and no kernel are installed into the target > >> system. > > > > A dtb shouldn't be necessary for the Sheevaplug, I don't think. Did you > > manually supply one or did something do that for you? I'm not that > > familiar with how a Sheevaplug is set up to boot by default. > > The tests was done using a patched uboot. Patched how? Just to enable the dtb commands? I'm not sure what the factory firmware was like on a sheevaplug, nor how brickable the thing is. If it's safe to update (or the factory one is really broken) then we could recommend an update, ideally to a u-boot shipped by Debian, in which case we should be able to rely on whichever features it has, such as native fdt support instead of appending. > > I think that if you install by booting without an fdt (in "board file" > > mode) then everything should just work. > > This do not work with latest kernel (d-i for jessie), which require a > fdt for sheeva and some others kirkwood as raidsonic or guruplug. Oh, I hadn't realised that some kirkwood platforms had been fully converted over to DTB already in 3.16. I knew it was an *option* for some (e.g. qnap TS-*), but not that it was mandatory on others. > > Alternatively if you want to boot in DTB mode (I don't think there is > > any direct benefit to doing so right now) then you will need to figure > > out an appropriate stanza for the flash-kernel database. Probably this > > will be very similar to the existing non-DTB one, except the Machine > > line should be the contents of /proc/device-tree/model instead > > of /proc/cpuinfo:hardware and you will probably want a DTB-Id line > > naming the correct DTB file. It's possible you might be able to combine > > the DTB and boardfile entires into one (the "Marvell Armada XP GP Board" > > does this) See flash-kernel's README for more information. You can > > experiment with entries in /etc/flash-kernel/db instead of editing the > > main DB. > > Theses tests was done for jessie support. OK, seems like I've misunderstood/misremembered the transition plan for some kirkwood devices. Please can you provide a suitable stanza for an updated flash-kernel db then. > Before jessie, sheevaplugs were support by the debian kernel and the debian > installer. AFAIK they are today as well, or are intended to be. But we do rely on people who have such hardware to test and report issues (so thanks!) and also to help us fix issues by filling in the blanks for that bit of hardware (e.g. db entries). > Debian installer had also a netconsole and a netboot image which give the > choice of the method of installing by ssh. I don't see a sheevaplug netconsole version in Wheezy or Squeeze either. When did Debian used to supply one? > Is sheevaplugs and derivatives support abandonned by debian ? > I hope not. I don't think so, you've just found a potential/probably bug exposed by an upstream kernel change is all. Ian. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1414681291.2064.46.ca...@hellion.org.uk
Bug#767052: D-I : Sheevaplug : could not determine kernel flavour
Hi Ian, On 28/10/2014 20:38, Ian Campbell wrote: > On Tue, 2014-10-28 at 04:08 +0100, drEagle wrote: >> The kernel flavour is not detected. >> Sheevaplug now use a dtb file and no kernel are installed into the target >> system. > > A dtb shouldn't be necessary for the Sheevaplug, I don't think. Did you > manually supply one or did something do that for you? I'm not that > familiar with how a Sheevaplug is set up to boot by default. The tests was done using a patched uboot. > I think that if you install by booting without an fdt (in "board file" > mode) then everything should just work. This do not work with latest kernel (d-i for jessie), which require a fdt for sheeva and some others kirkwood as raidsonic or guruplug. > Alternatively if you want to boot in DTB mode (I don't think there is > any direct benefit to doing so right now) then you will need to figure > out an appropriate stanza for the flash-kernel database. Probably this > will be very similar to the existing non-DTB one, except the Machine > line should be the contents of /proc/device-tree/model instead > of /proc/cpuinfo:hardware and you will probably want a DTB-Id line > naming the correct DTB file. It's possible you might be able to combine > the DTB and boardfile entires into one (the "Marvell Armada XP GP Board" > does this) See flash-kernel's README for more information. You can > experiment with entries in /etc/flash-kernel/db instead of editing the > main DB. Theses tests was done for jessie support. Before jessie, sheevaplugs were support by the debian kernel and the debian installer. Debian installer had also a netconsole and a netboot image which give the choice of the method of installing by ssh. Is sheevaplugs and derivatives support abandonned by debian ? I hope not. Regards, Gérald signature.asc Description: OpenPGP digital signature
Bug#762399: console-setup: WARNING: Unknown X keysym "permille"
Package: console-setup Version: 1.113 Followup-For: Bug #762399 Could this please get fixed before the freeze starts? Thanks! -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/debian-boot
Re: auto installation with url=file:///hd-media/d-i/
Hi Phil, On Donnerstag, 30. Oktober 2014, Philip Hands wrote: > I guess that we could also adopt the same approach for other protocols, > but I avoided that at the time because I thought that someone might like > to have preseed files generated on the fly, on a per client basis, by > specifying something like: url=http://our.magic.presseds.local/ I imagine that could be nice indeed. cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: auto installation with url=file:///hd-media/d-i/
Florian Lohoff writes: > On Tue, Oct 28, 2014 at 02:48:10PM +0100, Cyril Brulebois wrote: >> Hello, >> >> Florian Lohoff (2014-10-28): >> > i'd like to have a USB stick with complete auto installation for this i put >> > my preseed/late_script onto the usb stick - Now the d-i doesnt recognize >> > the url=file:///hd-media instead it tries to extend the url with the >> > domain from network autoconfiguration. >> > >> > Is it possible to use preseeding from the usb stick? >> >> That's covered by the installation guide: >> https://www.debian.org/releases/wheezy/amd64/apbs02.html.en > > After trying around what d-i expects to be in the URL i got it > to work. > > url=file:///hd-media/d-i/jessie/./preseed.cfg > > Its a bit counterintuitive that with a http url the code > automatically prepends with /d-i// which it does > not with a file:// url. Well, that's my fault, probably. The code (IIRC) checks if there are fewer than 3 /'s and if so adds the default path. Of course, with file:/// urls, you've got 3 straight away. Perhaps the check for file URLs should instead say: add the default path iff the url matches ^file:///.*/$ Can anyone think of circumstances where a file:/// URL pointing at a directory, rather than a file, would be a valid thing to do? I guess that we could also adopt the same approach for other protocols, but I avoided that at the time because I thought that someone might like to have preseed files generated on the fly, on a per client basis, by specifying something like: url=http://our.magic.presseds.local/ Cheers, Phil. -- |)| Philip Hands [+44 (0)20 8530 9560] HANDS.COM Ltd. |-| http://www.hands.com/http://ftp.uk.debian.org/ |(| Hugo-Klemm-Strasse 34, 21075 Hamburg,GERMANY pgp4HFA1Af5kc.pgp Description: PGP signature
