Re: updating kernel-wedge
On Thursday 26 March 2009, Kenshi Muto wrote: > Frans Pop wrote: > > On Wednesday 25 March 2009, Otavio Salvador wrote: > > > Your patch looks great but to solve the conflict, please add a > > > led-modules (any better suggestion?), and make both depends on it. > > > To make it buildable. > > > > How big is it? What are the dependencies? > > If it is small enough (which seems likely, why not add it to core or > > something? > > Well, led-class.ko is 10049 bytes and make core-modules.udeb size > from 5590 bytes to 7820 bytes. If it is acceptable, I'll commit > my changeset. That makes it not the smallest module, but it's not all that large either. The cost of adding another udeb will probably be higher (especially if it only contains a single module) and I expect quite a few udebs will end up depending on it with future kernel versions. Of course we should not make core into some general dumping ground, but IMHO this one does fit its purpose fairly well (ensure availability of relatively small, low-level, common modules to avoid explosion of the number of udebs and overly complicated dependencies). If it can be included in an existing udeb other than core which would mean it does not get included in (most) initrds while still solving the conflict and not be totally random and silly, then that might be preferred. But otherwise I think core is the best option here. Cheers, FJP -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: updating kernel-wedge
Hi, At 25 Mar 09 19:01:07 GMT, Frans Pop wrote: > On Wednesday 25 March 2009, Otavio Salvador wrote: > > Your patch looks great but to solve the conflict, please add a > > led-modules (any better suggestion?), and make both depends on it. To > > make it buildable. > > How big is it? What are the dependencies? > If it is small enough (which seems likely, why not add it to core or > something? Well, led-class.ko is 10049 bytes and make core-modules.udeb size from 5590 bytes to 7820 bytes. If it is acceptable, I'll commit my changeset. Thanks, -- Kenshi Muto km...@debian.org -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: d-i lab
Otavio: > If someone else wants to take it, I'll be available to help to understand > digress and like. If noone shows insterest, I prefer to do that then > lose d-i lab. Note that we've *already* lost the lab. You can't look at the lab report and get any useful info about whether d-i is working. However, if you or someone else would like to resuscitate the lab, that's fine. I think it would make sense to start with the emulated system tests, since control of the "hydra" server can easily be transferred from me. Also, there are several architectures that are not yet tested, but should be usable in qemu now, including arm. I doubt it's worth the expense of shipping the rack of physical test machines to a different continent, and I don't think it's really possible to do useful testing with them entirely remotely. So I'd like to go ahead with taking that portion of it down. -- see shy jo signature.asc Description: Digital signature
Bug#521224: console-setup: [INTL:pt] Updated Portuguese translation for debconf messages
Package: console-setup Version: 1.30 Tags: l10n, patch Severity: wishlist Updated Portuguese translation for console-setup's debconf messages. Translator: Pedro Ribeiro Feel free to use it. For translation updates please contact 'Last Translator' or the Portuguese Translation Team . -- Best regards, Miguel Figueiredo "Traduz" - Portuguese Translation Team http://www.DebianPT.org # Portuguese translation for console-setup debconf messages. # Copyright (C) 2007-2009 Pedro Ribeiro # This file is distributed under the same license as the console-setup package. # Pedro Ribeiro , 2009 # msgid "" msgstr "" "Project-Id-Version: console-setup 1.30\n" "Report-Msgid-Bugs-To: console-se...@packages.debian.org\n" "POT-Creation-Date: 2009-03-19 18:29+0100\n" "PO-Revision-Date: 2009-03-20 12:00+\n" "Last-Translator: Pedro Ribeiro \n" "Language-Team: Portuguese \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" #. Type: text #. Description #. Main menu item. Please keep below 55 columns #: ../console-setup.templates:2001 msgid "Configure the keyboard" msgstr "Configure o teclado" #. Type: select #. Choices #: ../console-setup.templates:3001 msgid ". Arabic" msgstr ". Árabe" #. Type: select #. Choices #: ../console-setup.templates:3001 msgid "# Armenian" msgstr "# Arménio" #. Type: select #. Choices #: ../console-setup.templates:3001 msgid "# Cyrillic - KOI8-R and KOI8-U" msgstr "# Cirílico - KOI8-R e KOI8-U" #. Type: select #. Choices #: ../console-setup.templates:3001 msgid "# Cyrillic - non-Slavic languages" msgstr "# Cirílico - línguas não eslavas" #. Type: select #. Choices #: ../console-setup.templates:3001 msgid "# Cyrillic - Slavic languages (also Bosnian and Serbian Latin)" msgstr "# Cirílico - Línguas eslavas (também Bósnio e Sérvio Latino)" #. Type: select #. Choices #: ../console-setup.templates:3001 msgid ". Ethiopic" msgstr ". Etíope" #. Type: select #. Choices #: ../console-setup.templates:3001 msgid "# Georgian" msgstr "# Georgiano" #. Type: select #. Choices #: ../console-setup.templates:3001 msgid "# Greek" msgstr "# Grego" #. Type: select #. Choices #: ../console-setup.templates:3001 msgid "# Hebrew" msgstr "# Hebraico" #. Type: select #. Choices #: ../console-setup.templates:3001 msgid "# Lao" msgstr "# Lao" #. Type: select #. Choices #: ../console-setup.templates:3001 msgid "# Latin1 and Latin5 - western Europe and Turkic languages" msgstr "# Latin1 e Latin5 - línguas da Europa ocidental e turcas" #. Type: select #. Choices #: ../console-setup.templates:3001 msgid "# Latin2 - central Europe and Romanian" msgstr "# Latin2 - Europa central e Romeno" #. Type: select #. Choices #: ../console-setup.templates:3001 msgid "# Latin3 and Latin8 - Chichewa; Esperanto; Irish; Maltese and Welsh" msgstr "# Latin3 e Latin8 - Chichewa; Esperanto: Irlandês; Maltês e Galês" #. Type: select #. Choices #: ../console-setup.templates:3001 msgid "# Latin7 - Lithuanian; Latvian; Maori and Marshallese" msgstr "# Latin7 - Lituano; Letão; Maori e Marshallês" #. Type: select #. Choices #: ../console-setup.templates:3001 msgid ". Latin - Vietnamese" msgstr ". Latin - Vietnamita" #. Type: select #. Choices #: ../console-setup.templates:3001 msgid "# Thai" msgstr "# Tailandês" #. Type: select #. Choices #: ../console-setup.templates:3001 msgid ". Combined - Latin; Slavic Cyrillic; Hebrew; basic Arabic" msgstr ". Combinado - Latino; Cirílico Eslavo; Hebraico; Árabe básico" #. Type: select #. Choices #: ../console-setup.templates:3001 msgid ". Combined - Latin; Slavic Cyrillic; Greek" msgstr ". Combinado - Latino; Cirílico Eslavo; Grego" #. Type: select #. Choices #: ../console-setup.templates:3001 msgid ". Combined - Latin; Slavic and non-Slavic Cyrillic" msgstr ". Combinado - Latino; Cirílico Eslavo e não Eslavo" #. Type: select #. Description #: ../console-setup.templates:3002 msgid "Character set to support:" msgstr "Conjunto de caracteres a suportar:" #. Type: select #. Description #: ../console-setup.templates:3002 #| msgid "Set of characters that should be supported by the console font:" msgid "" "Please choose the character set that should be supported by the console font." msgstr "" "Escolha, por favor, o conjunto de caracteres que deve ser suportado pelo tipo " "de letra da consola:" #. Type: select #. Description #: ../console-setup.templates:3002 msgid "" "If you don't use a framebuffer, the choices that start with \".\" will " "reduce the number of available colors on the console." msgstr "" "Se não usar framebuffer as opções que começam com \".\" irão reduzir o " "número de cores disponíveis para a consola." #. Type: select #. Description #: ../console-setup.templates:4001 msgid "Keyboard model:" msgstr "Modelo de teclado:" #. Type: select #. Description #: ../console-setup.templates:5001 msgid "Origin of the keyboard:" msgstr "Origem do teclado:" #. Type: select #. Description #: ../console-setup.templates:6001 msgid "Keyboar
Bug#520711: installation-reports: The squeeze netinst doesn't find archive
On Mar 25, 2009, at 7:37 AM, Otavio Salvador wrote: On Wed, Mar 25, 2009 at 3:09 AM, Christian Perrier wrote: Quoting Otavio Salvador (ota...@ossystems.com.br): On Tue, Mar 24, 2009 at 6:02 PM, Rick Thomas wrote: When I switch to the -F2 console and try to do a "wget", I get a segmentation fault. Please take a look on the syslog of the installer and if possible attach it to this bug report (please, gzip it). Isn't the wget segfault mentioned by Rick enough to explain the problem? I was interested to check if we had any kernel trace on syslog or something like that. Two thoughts: 1) Is there some debugging parameter you'd like me to set so that it gives more information? I have a spare machine I can use for testing this, so I can give good turnaround on test-cases. 2) Since this bug renders the install CDs (certainly "buisnesscard", and for most practical purposes "netinst") completely unusable for their intended purpose, can we raise the severity of this bug to (e.g.) "Serious"? Thanks! Rick -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: updating kernel-wedge
On Wednesday 25 March 2009, Otavio Salvador wrote: > Your patch looks great but to solve the conflict, please add a > led-modules (any better suggestion?), and make both depends on it. To > make it buildable. How big is it? What are the dependencies? If it is small enough (which seems likely, why not add it to core or something? -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#521122: console-setup: fails to install: "eval: line 2125: unexpected EOF while looking for matching `"'"
On Wed, 2009-03-25 at 20:09 +0200, Anton Zinoviev wrote: > On Wed, Mar 25, 2009 at 03:07:33AM +0100, Julien Cristau wrote: > > > > Thanks, the problem was the space in the XkbOptions value which my > > script didn't handle. The attached patch fixes that. > > It is not only your script - the parsing of console-setup doesn't allow > spaces between options so this will require a patch too. It should be easy to remove the spaces directly from the awk script, if you want to avoid touching other parts of console-setup for that. Let me know if I should prepare an updated patch. Cheers, Julien -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#521122: console-setup: fails to install: "eval: line 2125: unexpected EOF while looking for matching `"'"
On Wed, Mar 25, 2009 at 03:07:33AM +0100, Julien Cristau wrote: > > Thanks, the problem was the space in the XkbOptions value which my > script didn't handle. The attached patch fixes that. It is not only your script - the parsing of console-setup doesn't allow spaces between options so this will require a patch too. Anton Zinoviev -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: d-i lab
Otavio Salvador wrote: > On Wed, Mar 25, 2009 at 3:12 AM, Christian Perrier wrote: >> Quoting Otavio Salvador (ota...@ossystems.com.br): >>> On Tue, Mar 24, 2009 at 10:42 PM, Joey Hess wrote: I'm sure it will suprise no one when I say that the "d-i lab" automatic test stuff I used to do is broken and rotting[1]. I don't think there's any point in keeping it going in its current state, so I plan to turn it off. >>> I'd like to try to take the maintainence of it over if you accept it. >>> >>> I belive it is quite useful and I used it here at company and then >>> I can try to make it work again. I won't be able to do that until began >>> of April but if it is not a hurry to you, I can do that. >> >> Couldn't this be a good idea to propose to someone *else* who would >> like to contribute to D-I ? > > If someone else wants to take it, I'll be available to help to understand > digress and like. If noone shows insterest, I prefer to do that then > lose d-i lab. > >> Thus, it would save *your* time to work on release management..:-) >> >> (ref: last team meeting...) > > Yes, that would be nice but someone needs to show interest on it. I would be happy to help out, though would prefer a team effort, what do you think? Cheers Luk -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#521196: debootstrap does not support https transport
Package: debootstrap Version: 1.0.12 debootstrap does not support https transport although it probably could. When you attempt to debootstrap using a mirror served over https, debootstrap will fail complaining about the url being an unknown location. This is due to debootstrap specifically looking for "http:// " in the url. This bug was originally reported in launchpad at https://bugs.edge.launchpad.net/ubuntu/+source/debootstrap/+bug/348528 Cheers, -- Cody A.W. Somerville Software Systems Release Engineer Foundations Team Custom Engineering Solutions Group Canonical OEM Services Phone: +1-781-850-2087 Cell: +1-506-471-8402 Email: cody.somervi...@canonical.com
Re: updating kernel-wedge
Kenshi Muto writes: [...] > I noticed ath[59]k drivers conflicted with sdhci in mmc-modules to want > to use led-class. [...] Your patch looks great but to solve the conflict, please add a led-modules (any better suggestion?), and make both depends on it. To make it buildable. Doing it, we can commit it into d-i svn. -- O T A V I OS A L V A D O R - E-mail: ota...@debian.org UIN: 5906116 GNU/Linux User: 239058 GPG ID: 49A5F855 Home Page: http://otavio.ossystems.com.br - "Microsoft sells you Windows ... Linux gives you the whole house." -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: updating kernel-wedge
Hi, At 23 Mar 09 14:53:21 GMT, Otavio Salvador wrote: > On Mon, Mar 23, 2009 at 10:33 AM, Kenshi Muto wrote: > >> * Otavio Salvador [2009-03-21 17:02]: > >> > This is the first proposal of patches to update our kernel to > >> > 2.6.29. I belive we'll still have changes to do on this set of patches > >> > before really commiting it but it would be nice if porters could take > >> > a look at them and propose patches for any remaining issues. > >> > >> These changes look good to me. I suggest you commit them to SVN. > > > > From my experience when I built 2.6.28 kernel d-i, I'd like to ask to add: > > Mind to prepare a patch for it? OK, here it is. I noticed ath[59]k drivers conflicted with sdhci in mmc-modules to want to use led-class. Index: debian/changelog === --- debian/changelog(revision 57983) +++ debian/changelog(working copy) @@ -16,6 +16,12 @@ * ide-modules: Include ide-gd_mod (for ATA/ATAPI disks and floppy; ide-disk got renamed.) + [ Kenshi Muto ] + * nic-extra-modules: make eepro100 optional. + add jme, enic, be2net, myri10ge, sc92031. + * nic-wireless-modules: add ath9k, iwlagn. + * nic-usb-modules: add rtl8187. + -- Otavio Salvador Mon, 23 Mar 2009 04:26:31 -0300 kernel-wedge (2.53) unstable; urgency=low Index: modules/nic-wireless-modules === --- modules/nic-wireless-modules(revision 57983) +++ modules/nic-wireless-modules(working copy) @@ -28,3 +28,5 @@ # Crypto modules needed for ieee80211 WEP support ecb ? arc4 ? +ath9k ? +iwlagn ? Index: modules/nic-extra-modules === --- modules/nic-extra-modules (revision 57983) +++ modules/nic-extra-modules (working copy) @@ -11,7 +11,7 @@ dmfe e2100 ? eepro ? -eepro100 +eepro100 ? enc28j60 forcedeth hamachi @@ -98,3 +98,8 @@ atl1e ? r6040 sfc +jme ? +enic ? +be2net ? +myri10ge ? +sc92031 ? Index: modules/nic-usb-modules === --- modules/nic-usb-modules (revision 57983) +++ modules/nic-usb-modules (working copy) @@ -12,3 +12,4 @@ zd1211rw ? rndis_wlan ? rtl8180 ? +rtl8187 ? -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: close
Processing commands for cont...@bugs.debian.org: > tags 516082 upstream Bug#516082: supermicro blade server B7DC3, failed to detect raidset on LSI 1068E SAS/SATA There were no tags set. Tags added: upstream > close 516082 Bug#516082: supermicro blade server B7DC3, failed to detect raidset on LSI 1068E SAS/SATA 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Ronny Aasen > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: d-i installation on embedded devices (was Re: [pkg-fso-maint] MTD Installation)
Hey there! On Wed, Mar 25, 2009 at 12:00 PM, Luca Capello wrote: >> 2009/3/25 Joachim Breitner : Maybe some other thread discusses this already, but why don't you use d-i for installation? >>> >>> Simplicity. We wanted to get started as fast as possible. But given the >>> ever increasing complexity of install.sh, this should be the goal, yet. >>> Could porting d-i to GTA02 (and GTA01 but I don't have one of those) be worth doing as a GSoC project? > > For anyone working on/for the pkg-fso, thanks to Arne Anka [1] I can > borrow/offer a GTA01 (if needed the full development kit, i.e. with a > debug board as well). Since I was in contact with people interested to > sell their GTA01, I can also find more than one device, if needed. This > is *only* for Debian-related work, in any field (e.g. X11, ALSA, GPS, > etc.) and not only for d-i. Cool, a d-i knowledgable person (willing to mentor) could borrow a handset then. >>> Quite possible – please raise that idea on the pkg-fso-maint list. Some >>> others have expressed interested in trying to port d-i to the FreeRunner >>> (Steffen Moeller, IIRC). He’s subscribed to the list. > > I am interested as well, and this is one of the first item in my pkg-fso > ToDo list, it seems that other stuff (kernel, bug fixing and so on) is > keeping me away from it. I am not speaking to deaf ears then, good. :-) >>> Do you know any d-i knowledgeable person that has a FreeRunner and would >>> be able to mentor this project? >> >> @debian-boot: Anyone up for this? > > NB, I have no knowledge at all WRT how the GSoC work, but I am not sure > we can still change the different projects we submitted. Any proposal is accepted and then ranked on after proposal deadlines. No projects are written in stone until after the proposal deadline. (Proposal deadline is 3 April IIRC.) > In any case, I think that the MTD project should still have an higher > priority, because: > > - its use is wider (e.g. for NAS devices) > > - it involves more people (not only the pkg-fso crew), thus it is > probably easier to have advices I agree with both points, just an idea I had (as a backup proposal) if mentoring becomes a problem with the MTD project. And I would really like to work on d-i for Openmoko phones as well of course. > - ATM no official Debian kernel can be used on the FreeRunner and I > really do not have ETA about when one will be available (Openmoko > has now switched to 2.6.29 and the last time I checked for IIRC 2.6.26 > they had something like more than 100 patches) This would be a deal breaker... >> I have a FreeRunner myself. >> >> Without having done any research at all yet, I think >> that similar infrastructure to how Debian Installer is >> booted and installed on NAS devices could be used. >> The bootstrapping part seems very similar to the >> GSoC project I did last year, since the FreeRunner >> uses U-Boot as well. (Of course it would have to be >> made to work with the Qi bootloader as well which >> widens the scope.) > > Disclaimer: everything below is my personal opinion. > > I think we clearly need to have a plan, divided into two phases: > > 1) installation into the microSD > > a. booting d-i on the FR, which is an easy task given that we must > use the pkg-fso kernel package [2]. > > b. starting the graphical installer with a virtual keyboard, since > there is no physical keyboard, thus the textual installer cannot > be used. And/or accept SSH connections to the installer. As is done for NAS devices. > After my talk at last FOSDEM'09 [3], I talked with Jeremy Bobbio about > that: from a quick view he had at d-i, this should not be so > difficult either, given that d-i already uses the framebuffer. > > c. installing everything on the microSD, which means that d-i should > not use the microSD at all, thus it should probably be run from a > ramdisk. It should be possible to write d-i kernel and ramdisk to MTD flash and boot from that, not touching the microSD. > d. deafening some tasks for tasksel and then installing everything. > > e. modifying the boot loader. > > On this point, I am a strong opponent of Qi [4] (the now default > bootloader used by Openmoko), because it lacks at least one very > important feature U-Boot has: a menu. This is why I think that > any effort should firstly target U-Boot and then Qi, which AFAIK > is ATM available only for the Openmoko. I agree with this opinion. > 2) installation into the MTD > > Given that everything above will be already done, we will have only > two showstopper: > > a. MTD support in d-i. > > This is also why I consider implementing MTD in d-i of an higher > priority than adapting d-i to the FR. > > b. disk space. > > The FR (GTA02) has 256MB of flash memory, while the 1973 (GTA01) > only 64MB [5]. In both case, there is no way we can fit a normal > Debian system on it,
d-i installation on embedded devices (was Re: [pkg-fso-maint] MTD Installation)
Hi there! On Wed, 25 Mar 2009 11:45:09 +0100, Per Andersson wrote: > (Cc:ing debian-boot.) Done, but please keep the pkg-fso-maint@ mailing list cc:ed as well, TIA. Doing so, there is no need to cc: me. I also cc:ed the debian-embedded@ mailing list, people from there should be interested as well. I changed the title to something more appropriate. > 2009/3/25 Joachim Breitner : >>> Maybe some other thread discusses this already, >>> but why don't you use d-i for installation? >> >> Simplicity. We wanted to get started as fast as possible. But given the >> ever increasing complexity of install.sh, this should be the goal, yet. >> >>> Could porting d-i to GTA02 (and GTA01 but I don't >>> have one of those) be worth doing as a GSoC project? For anyone working on/for the pkg-fso, thanks to Arne Anka [1] I can borrow/offer a GTA01 (if needed the full development kit, i.e. with a debug board as well). Since I was in contact with people interested to sell their GTA01, I can also find more than one device, if needed. This is *only* for Debian-related work, in any field (e.g. X11, ALSA, GPS, etc.) and not only for d-i. >> Quite possible – please raise that idea on the pkg-fso-maint list. Some >> others have expressed interested in trying to port d-i to the FreeRunner >> (Steffen Moeller, IIRC). He’s subscribed to the list. I am interested as well, and this is one of the first item in my pkg-fso ToDo list, it seems that other stuff (kernel, bug fixing and so on) is keeping me away from it. >> Do you know any d-i knowledgeable person that has a FreeRunner and would >> be able to mentor this project? > > @debian-boot: Anyone up for this? NB, I have no knowledge at all WRT how the GSoC work, but I am not sure we can still change the different projects we submitted. In any case, I think that the MTD project should still have an higher priority, because: - its use is wider (e.g. for NAS devices) - it involves more people (not only the pkg-fso crew), thus it is probably easier to have advices - ATM no official Debian kernel can be used on the FreeRunner and I really do not have ETA about when one will be available (Openmoko has now switched to 2.6.29 and the last time I checked for IIRC 2.6.26 they had something like more than 100 patches) > I have a FreeRunner myself. > > Without having done any research at all yet, I think > that similar infrastructure to how Debian Installer is > booted and installed on NAS devices could be used. > The bootstrapping part seems very similar to the > GSoC project I did last year, since the FreeRunner > uses U-Boot as well. (Of course it would have to be > made to work with the Qi bootloader as well which > widens the scope.) Disclaimer: everything below is my personal opinion. I think we clearly need to have a plan, divided into two phases: 1) installation into the microSD a. booting d-i on the FR, which is an easy task given that we must use the pkg-fso kernel package [2]. b. starting the graphical installer with a virtual keyboard, since there is no physical keyboard, thus the textual installer cannot be used. After my talk at last FOSDEM'09 [3], I talked with Jeremy Bobbio about that: from a quick view he had at d-i, this should not be so difficult either, given that d-i already uses the framebuffer. c. installing everything on the microSD, which means that d-i should not use the microSD at all, thus it should probably be run from a ramdisk. d. deafening some tasks for tasksel and then installing everything. e. modifying the boot loader. On this point, I am a strong opponent of Qi [4] (the now default bootloader used by Openmoko), because it lacks at least one very important feature U-Boot has: a menu. This is why I think that any effort should firstly target U-Boot and then Qi, which AFAIK is ATM available only for the Openmoko. 2) installation into the MTD Given that everything above will be already done, we will have only two showstopper: a. MTD support in d-i. This is also why I consider implementing MTD in d-i of an higher priority than adapting d-i to the FR. b. disk space. The FR (GTA02) has 256MB of flash memory, while the 1973 (GTA01) only 64MB [5]. In both case, there is no way we can fit a normal Debian system on it, especially considering that we should target the FreeSmartphone.Org initiative [6], which ATM relies on Python. The solution in this case is EmDebian. Given the above, if it was not clear yet, I have a clear vision of what everything should move. Not that this vision is the correct one, but I think it makes sense. Obviously, I am available to discuss it: I am not looking for glory, on the contrary I would like that we progress by small and well-defined steps :-) Thx, bye, Gismo / Luca Footnotes: [1] http://lists.linuxtogo.org/pipermail/smartphones-userland/2009-Febr
Bug#520711: installation-reports: The squeeze netinst doesn't find archive
On Wed, Mar 25, 2009 at 3:09 AM, Christian Perrier wrote: > Quoting Otavio Salvador (ota...@ossystems.com.br): >> On Tue, Mar 24, 2009 at 6:02 PM, Rick Thomas wrote: >> > When I switch to the -F2 console and try to do a "wget", I get a >> > segmentation fault. >> >> Please take a look on the syslog of the installer and if possible >> attach it to this >> bug report (please, gzip it). > > > Isn't the wget segfault mentioned by Rick enough to explain the > problem? I was interested to check if we had any kernel trace on syslog or something like that. -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: d-i lab
On Wed, Mar 25, 2009 at 3:12 AM, Christian Perrier wrote: > Quoting Otavio Salvador (ota...@ossystems.com.br): >> On Tue, Mar 24, 2009 at 10:42 PM, Joey Hess wrote: >> > I'm sure it will suprise no one when I say that the "d-i lab" automatic >> > test stuff I used to do is broken and rotting[1]. I don't think there's >> > any point in keeping it going in its current state, so I plan to turn it >> > off. >> >> I'd like to try to take the maintainence of it over if you accept it. >> >> I belive it is quite useful and I used it here at company and then >> I can try to make it work again. I won't be able to do that until began >> of April but if it is not a hurry to you, I can do that. > > > Couldn't this be a good idea to propose to someone *else* who would > like to contribute to D-I ? If someone else wants to take it, I'll be available to help to understand digress and like. If noone shows insterest, I prefer to do that then lose d-i lab. > Thus, it would save *your* time to work on release management..:-) > > (ref: last team meeting...) Yes, that would be nice but someone needs to show interest on it. -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: [pkg-fso-maint] MTD Installation
(Cc:ing debian-boot.) 2009/3/25 Joachim Breitner : >> Maybe some other thread discusses this already, >> but why don't you use d-i for installation? > > Simplicity. We wanted to get started as fast as possible. But given the > ever increasing complexity of install.sh, this should be the goal, yet. > >> Could porting d-i to GTA02 (and GTA01 but I don't >> have one of those) be worth doing as a GSoC project? > > Quite possible – please raise that idea on the pkg-fso-maint list. Some > others have expressed interested in trying to port d-i to the FreeRunner > (Steffen Moeller, IIRC). He’s subscribed to the list. > > Do you know any d-i knowledgeable person that has a FreeRunner and would > be able to mentor this project? @debian-boot: Anyone up for this? I have a FreeRunner myself. Without having done any research at all yet, I think that similar infrastructure to how Debian Installer is booted and installed on NAS devices could be used. The bootstrapping part seems very similar to the GSoC project I did last year, since the FreeRunner uses U-Boot as well. (Of course it would have to be made to work with the Qi bootloader as well which widens the scope.) Also adding a task in tasksel "Phone" or something would be in scope of this project I suppose. Best regards, Per > Greetings, > Joachim > -- > Joachim "nomeata" Breitner > Debian Developer > nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C > JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata > > ___ > pkg-fso-maint mailing list > pkg-fso-ma...@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/pkg-fso-maint > > -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#520934: console-setup: [INTL:fi] Updated Finnish translation of the debconf templates
Quoting Esko Arajärvi (e...@iki.fi): > Right. I committed the new version to SVN (rev. 57973) and therefore close > this bug. Strictly speaking, it would be better to add the relevant "Closes:" entry in debian/changelog when committing...but as the maintainer uploaded console-setup in the meantime, it's better leaving it this way now... signature.asc Description: Digital signature
Bug#520711: installation-reports: The squeeze netinst doesn't find archive
Quoting Otavio Salvador (ota...@ossystems.com.br): > On Tue, Mar 24, 2009 at 6:02 PM, Rick Thomas wrote: > > When I switch to the -F2 console and try to do a "wget", I get a > > segmentation fault. > > Please take a look on the syslog of the installer and if possible > attach it to this > bug report (please, gzip it). Isn't the wget segfault mentioned by Rick enough to explain the problem? signature.asc Description: Digital signature
Re: d-i lab
Quoting Otavio Salvador (ota...@ossystems.com.br): > On Tue, Mar 24, 2009 at 10:42 PM, Joey Hess wrote: > > I'm sure it will suprise no one when I say that the "d-i lab" automatic > > test stuff I used to do is broken and rotting[1]. I don't think there's > > any point in keeping it going in its current state, so I plan to turn it > > off. > > I'd like to try to take the maintainence of it over if you accept it. > > I belive it is quite useful and I used it here at company and then > I can try to make it work again. I won't be able to do that until began > of April but if it is not a hurry to you, I can do that. Couldn't this be a good idea to propose to someone *else* who would like to contribute to D-I ? Thus, it would save *your* time to work on release management..:-) (ref: last team meeting...) signature.asc Description: Digital signature
