Re: udeb uninstallability trend: worse (+20/-0)
On Mon, 01 Jan 2018, Don Armstrong wrote: > On Mon, 01 Jan 2018, Cyril Brulebois wrote: > > udeb uninstallability watcher <debian-boot@lists.debian.org> (2018-01-01): > > > Newly-broken packages in testing > > > multipath-udeb amd64 arm64 armel armhf i386 > > > mips mips64el mipsel ppc64el s390x > > > partman-multipathamd64 arm64 armel armhf i386 > > > mips mips64el mipsel ppc64el s390x > > > > I'm wondering how this is possible with an RC bug filed against the > > multipath-udeb udeb (#885556). For some reason, it's listed as found in > > multipath-tools/0.7.4-2 on the BTS side, without a version graph; and > > it isn't listed by tracker or by the old PTS. I'm suspecting there's > > something fishy on the BTS side so britney didn't notice the RC bug > > and let it migrate? > > Yeah, this definitely looks like a BTS mistake. It seems to know that > the right versions are in unstable, but they're not showing up on the > graph. OK. Found the issue. Apparently, packages in the */debian-installer components were being skipped when the BTS was figuring out what was in which distribution. I've fixed that now, and the versions database is being updated with that information. The underlying issue should show up as fixed once the version graph for this bug looks sane. [Probably in another 10-20 minutes.] -- Don Armstrong https://www.donarmstrong.com Every gun that is made, every warship launched, every rocket fired signifies [...] a theft from those who hunger and are not fed, those who are cold and are not clothed. This world in arms is not spending money alone. It is spending the sweat of its laborers, the genius of its scientists, the hopes of its children. [...] This is not a way of life at all in any true sense. Under the cloud of threatening war, it is humanity hanging from a cross of iron. [...] [I]s there no other way the world may live? -- President Dwight D. Eisenhower, April 16, 1953
Re: udeb uninstallability trend: worse (+20/-0)
On Mon, 01 Jan 2018, Cyril Brulebois wrote: > udeb uninstallability watcher <debian-boot@lists.debian.org> (2018-01-01): > > Newly-broken packages in testing > > multipath-udeb amd64 arm64 armel armhf i386 > > mips mips64el mipsel ppc64el s390x > > partman-multipathamd64 arm64 armel armhf i386 > > mips mips64el mipsel ppc64el s390x > > I'm wondering how this is possible with an RC bug filed against the > multipath-udeb udeb (#885556). For some reason, it's listed as found in > multipath-tools/0.7.4-2 on the BTS side, without a version graph; and > it isn't listed by tracker or by the old PTS. I'm suspecting there's > something fishy on the BTS side so britney didn't notice the RC bug > and let it migrate? Yeah, this definitely looks like a BTS mistake. It seems to know that the right versions are in unstable, but they're not showing up on the graph. I'll try to track this down today and see what is going on there. -- Don Armstrong https://www.donarmstrong.com The terrorist's job is to terrorize the people, to interfere with freedom in such a way that disrupts ordinary life and commerce. With due respect, it is clear that the above referenced governmental agencies are aiding the terrorists' objective. -- Gary Fielder in Gary Fielder vs Janet Napolitano et al.
Re: omg! astonishing!
Greetings, This is just something really astonishing, I'm letting you know, you have to take a peek http://opaldentallab.com/resist.php?1FfWRg0ND Sent from my iPhone, Don Armstrong - The content of the pages of this website is for your general information and use only. It is subject to change without notice. This website uses cookies to monitor browsing preferences. If you do allow cookies to be used, the following personal information may be stored by us for use by third parties.
Re: jessie won't install/boot on a Dell Poweredge R815
On Wed, 22 Jun 2016, Jeffrey Mark Siskind wrote: > and attempted > >mdadm /dev/md0 --add /dev/sda1 >mdadm /dev/md0 --add /dev/sdb1 >mdadm /dev/md0 --add /dev/sdc1 >mdadm /dev/md0 --add /dev/sdd1 >mdadm /dev/md0 --add /dev/sde1 >mdadm /dev/md0 --add /dev/sdf1 > > but these all failed. This is the wrong command; it should be mdadm --assemble /dev/md0 /dev/sd[abcdef]1; And that should only be done if the md0 device doesn't show up in the initrd when you cat /proc/mdstat. What's happened is that the raid1 device now has 12 drives instead of 6, which basically isn't going to work at all. You should be able to just directly reinstall jessie on this machine; I'd also zero out the superblocks on the devices in /dev/md0, and then assuming that the syncing has proceeded enough, you should be able to install grub with an appropriate rootdelay and get it to boot. (Again, in theory.) -- Don Armstrong https://www.donarmstrong.com The computer allows you to make mistakes faster than any other invention, with the possible exception of handguns and tequila -- Mitch Ratcliffe
Re: jessie won't install/boot on a Dell Poweredge R815
On Tue, 21 Jun 2016, Jeffrey Mark Siskind wrote: > http://upplysingaoflun.ecn.purdue.edu/~qobi/20160619_140357.jpg Are you certain that there isn't a PERC H700 in this machine? [Sort of odd that mpt2sas is triggering a state error in your screenshot if there actually isn't one.] > I don't believe that I have any add-in cards. The machine was > purchased straight from Dell. It has six SATA disks and 4 gigabit > ethernet ports. It has four 12-core AMD CPUs and 128GB RAM. The output > of lspci on an indentical machin purchased at the same time that is > still running wheezy is enclosed below. OK. This: > 00:11.0 SATA controller: Advanced Micro Devices [AMD] nee ATI > SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode] makes me think that the SATA controller is in IDE/Legacy mode instead of AHCI. In theory, this shouldn't matter, but it's possible that this is also a problem. I'd try switching it in the bios and see what happens. >What does the kernel output while it is detecting the disks and >partitions? Remove the quiet option from the kernel command line by editing it in grub. > Do all of the drives show up properly? echo /dev/sd*; should give you an idea of what is there in the initramfs. >When the boot fails, can you read from the underlying block >devices? more /dev/sda; should work, I believe. > I don't know what one can do in at the initramfs command prompt. If you give > me some commands, I will try them out and post the output. > >Does specifying delay=20 or similar result in a successful boot? > I will try this. This should actually be rootdelay=20; sorry. > I will try to get this info. It will require me to redo the exercise > of a fresh jessie install from USB. I'll have to take and post screen > pictures because I have no way to capture the console output. I believe the R815 still has a serial port; you can just plug in a serial cable and append an appropriate serial tty option to the kernel command line to get output as text. > But again note, that I do not believe that there are any disk hardware > errors. And I do not believe that there are any data errors in the > layout of the ext3 file system, the layout of the md0 raid array, or > the partition tables. The reason is that after the failed jessie > install, I reinstall a fressh wheezy from USB. I don't repartition. > And I don't rebuild md1 and don't rebuild /aux. But I do rebuild md0 > and / as part of the fresh install. And it works. Yes; it's possible that a change in one of the drivers between the wheezy and jessie kernels is exposing a firmware bug (or there's a bug in the kernel itself) which is causing this issue. What I'm trying to do is get enough information so that the error is obvious. -- Don Armstrong https://www.donarmstrong.com What I can't stand is the feeling that my brain is leaving me for someone more interesting.
Re: jessie won't install/boot on a Dell Poweredge R815
On Tue, 21 Jun 2016, Jeffrey Mark Siskind wrote: > Please note that all of the above systems have / as md0 RAID1. The fresh > install of jessie was successfull on all but the R815s. > >> Then it fails to reboot and goes into the initramfs. I have a > picture of >> the screen if anybody wishes. > >Yes please. Also please use the 'rescue' boot option which enables >more verbose logging to the screen. > > Thanks for your help. > > Here is a screen picture. Could you upload this to an image paste site or send it along (or use a serial console to get it as text?) > I conjecture that the jessie kernel has difficulty accessing the MD > array on disk. The same problem occurs when I attempt a direct fresh > install of jessie with the installer. Which add-in card are you using on the R815s? What does the kernel output while it is detecting the disks and partitions? Do all of the drives show up properly? Are the blocksizes correct for the partitions? When the boot fails, can you read from the underlying block devices? Do the block devices get detected after the boot fails? Does specifying delay=20 or similar result in a successful boot? > Here is what happens that is strange. When I do a fresh install of jessie, one > of the first things that the installer does is probe for hardware to try to > find the ISO. I have done this about 10 times. Sometimes (about 3 or 4) it > succeeds in finding the ISO. Sometimes (the rest) it comes up with a red > screen and claims that it can't find the ISO. In all cases, I am booting the > installer from the same USB dongle with the same data on it. I made the dongle > as follows: > ># cd /tmp ># wget > http://ftp.nl.debian.org/debian/dists/jessie/main/installer-amd64/current/images/hd-media/boot.img.gz ># wget > http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/8.5.0+nonfree/amd64/iso-cd/firmware-8.5.0-amd64-netinst.iso ># zcat boot.img.gz >/dev/sdf ># mount /dev/sdf /mnt ># cp firmware-8.5.0-amd64-netinst.iso /mnt/. You can actually just cat firmware-8.5.0-amd64-netinst.iso > /dev/sdf; > Every time so far, md1 has all 6 components. But md0 has only some of > the components, sometimes 5/6, sometimes 4/6, and sometimes 1/6. And > every time it is a different set of components. Even though, just a > few minutes earlier, I was running wheezy and md0 had all 6 > components. I do > > mdadm /dev/md0 --add > > but it refuses. I forget the error. The error would be useful to know. Most likely one or more of them dropped out of the array for some reason and you're booting off of one which has a lower event count and it won't assemble. But it could be any number of things. The output of mdadm --examine /dev/sd[abcdef]1; when md0 fails to assemble would also be useful. -- Don Armstrong https://www.donarmstrong.com S: Make me a sandwich B: What? Make it yourself. S: sudo make me a sandwich B: Okay. -- xkcd http://xkcd.com/c149.html
Re: remove me from this list
On Wed, 07 Jan 2015, Cindy-Sue Causey wrote: *PLEASE* help *ALL* those named there by clicking that report as sp*m button at the top right of that page. Just one person clicking it is enough; the spam has to be manually reviewed by someone with a spam review account. [Once they've done that, it'll disappear.] -- Don Armstrong http://www.donarmstrong.com I leave the show floor, but not before a pack of caffeinated Jolt gum is thrust at me by a hyperactive girl screaming, Chew more! Do more! The American will to consume more and produce more personified in a stick of gum. I grab it. -- Chad Dickerson -- 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/20150108070321.gt29...@teltox.donarmstrong.com
Re: debootstrap and cdebootstrap vs systemd
On Thu, 06 Nov 2014, Simon Richter wrote: I've run into a bit of a problem building a root filesystem for an ARM system where the kernel shipped by the vendor is 2.6 based. As systemd does not work there, I tried installing a sysvinit based system using --include and --exclude to (c)debootstrap. This sounds like #668001. Try applying the patch there, and see if that works. -- Don Armstrong http://www.donarmstrong.com Let the victors, when they come, When the forts of folly fall Find thy body by the wall! -- Matthew Arnold -- 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/20141107000217.gn24...@rzlab.ucr.edu
Re: Need known bug list for Debian Linux
On Mon, 20 Oct 2014, Priyadarshini, Chethana (GE Healthcare) wrote: I am Chethana and am writing from Wipro GE Healthcare Private Limited. We are using the software product 'Debian Linux' version 5.0 on one of our embedded medical device. We have been using the software and the medical device is in the market from past 6 years. We are performing a SOUP(Software of Unknown Pedigree) anomaly for the purpose of audit. With regard to this we need to check if the 3rd party software which we are using in our product has any known defects and its impact on our product. Hence can you please send me the known defect list such that we can analyze it and see if it has any impact on our medical device. All of the bugs which are known can be accessed using http://bugs.debian.org. The precise search that you will have to perform depends greatly on the software versions from Debian which you actually have installed on your device. But briefly, for each of the packages installed, you can check for a search like: http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=foo;version=sourceversion;archive=both and then exclude bugs which are fixed or absent in the version that you searched for. All of that said, Debian 5.0 (Lenny) has been EOLed for well over three years now, and likely has known remote root exploits. -- Don Armstrong http://www.donarmstrong.com [I]t's true that some of the most terrible things in the world are done by people who think, genuinely think, that they're doing it for the best, especially if there is some god involved. -- Terry Pratchett _Snuff_ p185 -- 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/20141020152126.gt28...@teltox.donarmstrong.com
Re: Bug#761450: Please add a d-i.debian.org pseudo package
On Sun, 14 Sep 2014, Cyril Brulebois wrote: d-i.debian.org -- Issues regarding the d-i.debian.org service and general Debian Installer tasks. The pseudopackage has now been added. -- Don Armstrong http://www.donarmstrong.com It was a very familiar voice. [...] It was a voice you could have used to open a bottle of whine. -- Terry Pratchett _The Last Continent_ p270 -- 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/20140918000101.gz8...@teltox.donarmstrong.com
Please add a d-i.debian.org pseudo package
Control: submitter -1 Cyril Brulebois k...@debian.org Control: tag -1 moreinfo On Sat, 13 Sep 2014, Cyril Brulebois wrote: Cyril Brulebois k...@debian.org (2014-09-07): Hi folks, I'm wondering whether it would make sense to ask ow...@bugs.debian.org for a d-i.debian.org pseudo package which could be used to track bugs/proposed changes for d-i's infrastructure. This includes but is not limited to: the various scripts generating reports on d-i.debian.org, scripts used to manage i18n/l10n bits, or various cross-package tasks. Dear owner, could you please introduce a d-i.debian.org pseudo package with debian-boot@lists.debian.org as its maintainer? I can; can you provide the text for this psuedopackage's description, as well as an example of a few bugs which will be filed there? [The latter is mainly so that I know that the psuedopackage will be used; they don't have to yet be filed in the BTS... a few links to messages on -boot which are bugs which would have been filed is good enough.] -- Don Armstrong http://www.donarmstrong.com Some pirates achieved immortality by great deeds of cruelty or daring-do. Some achieved immortality by amassing great wealth. But the captain had long ago decided that he would, on the whole, prefer to achieve immortality by not dying. -- Terry Pratchet _The Color of Magic_ -- 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/20140913213347.gr32...@teltox.donarmstrong.com
Re: Please add a d-i.debian.org pseudo package
On Sun, 14 Sep 2014, Cyril Brulebois wrote: Looking at the existing descriptions[1], I'd go for something like: d-i.debian.org -- Issues regarding the d-i.debian.org service and general Debian Installer tasks. Cool. Sure, things like this would have been tracked there: http://anonscm.debian.org/viewvc/d-i/trunk/scripts/testing-summary/gen-summary?r1=69167r2=69316 https://lists.debian.org/debian-boot/2014/09/msg00406.html Awesome; this is exactly what I wanted to see. I'll create this package shortly. -- Don Armstrong http://www.donarmstrong.com First you take a drink, then the drink takes a drink, then the drink takes you. -- F. Scott Fitzgerald -- 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/20140913223349.ga8...@teltox.donarmstrong.com
Re: Reverting to GNOME for jessie's default desktop
On Thu, 07 Aug 2014, Jordi Mallach wrote: Well, it's roughly that time. :) So I'd like to plainly request GNOME is reinstated as the default desktop environment for a number of reasons. One of the reasons put forward for switching to Xfce was size on the installation images; could you (and/or debian-cd) address this? Specifically: 1) Would you want the default CD/DVD image to use a GNOME even if GNOME was unable to fit on a single image? 2) Would the GNOME team consider a less-complete DE for cases where image size is a restriction? -- Don Armstrong http://www.donarmstrong.com First you take a drink, then the drink takes a drink, then the drink takes you. -- F. Scott Fitzgerald -- 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/20140807222926.gn2...@rzlab.ucr.edu
Re: Bug#699808: tech-ctte: syslinux vs the wheezy release
On Tue, 05 Feb 2013, Julien Cristau wrote: - the latest of these uploads breaks the installer, making it impossible to build and upload the planned wheezy release candidate, since build-dependencies are fetched from unstable - when asked to revert this change, the syslinux maintainer refused, and said disagreements should be referred to the technical committee Assuming that the patch for #699742[0] fixes this issue with DI RC releases being installed, is there still an outstanding issue for the CTTE? [I can understand a bit of wariness of having d-i built with a version of syslinux that isn't being distributed in wheezy, but I think that might need to be discussed and a technical solution fleshed out elsewhere, and probably isn't ripe for a CTTE decision.] Don Armstrong 0: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699742#30 1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699742#40 -- [Panama, 1989. The U.S. government called it Operation Just Cause.] I think they misspelled this. Shouldn't it be Operation Just 'Cause? -- TekPolitik http://slashdot.org/comments.pl?sid=59669cid=5664907 http://www.donarmstrong.com http://rzlab.ucr.edu -- 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/20130206204100.gd17...@rzlab.ucr.edu
Re: Bug#699808: tech-ctte: syslinux vs the wheezy release
On Wed, 06 Feb 2013, Russ Allbery wrote: Don Armstrong d...@debian.org writes: Assuming that the patch for #699742[0] fixes this issue with DI RC releases being installed, is there still an outstanding issue for the CTTE? Earlier in this thread, there had been a couple of reports that fix didn't work. I haven't looked further, though. Yeah, that was for the first incomplete patch. I was referring to the second one. Don Armstrong -- Let us chat together a moment, my friend. There are still several hours until dawn, and I have the whole day to sleep. -- Count Orlock in _Nosferatu (1922)_ http://www.donarmstrong.com http://rzlab.ucr.edu -- 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/2013020624.gf17...@rzlab.ucr.edu
Re: Bug#699808: tech-ctte: syslinux vs the wheezy release
On Wed, 06 Feb 2013, Cyril Brulebois wrote: Daniel Baumann daniel.baum...@progress-technologies.net (05/02/2013): or: * apply the following tested and working patch from #699742 in debian-installer, […] Except that this “tested and working patch” doesn't fix anything. Same issue, as seen by Michael and myself. Is it the intention of the Release Managers not to accept a newer version of syslinux into wheezy? [That is, if the CTTE were to decide to require some fix to d-i, we'd also have to override the RMs?] Don Armstrong -- I now know how retro SCOs OSes are. Riotous, riotous stuff. How they had the ya-yas to declare Linux an infant OS in need of their IP is beyond me. Upcoming features? PAM. files larger than 2 gigs. NFS over TCP. The 80's called, they want their features back. -- Compactable Dave http://www3.sympatico.ca/dcarpeneto/sco.html http://www.donarmstrong.com http://rzlab.ucr.edu -- 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/20130205235509.gm6...@rzlab.ucr.edu
Bug#657904: Wrong versions fixed in bug 657904
This bug (657904) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- 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/1348257060.285750.619.nullmai...@teltox.donarmstrong.com
Bug#672160: Wrong versions fixed in bug 672160
This bug (672160) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- 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/1348257060.118203.578.nullmai...@teltox.donarmstrong.com
Bug#682538: Wrong versions fixed in bug 682538
This bug (682538) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- 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/1348257060.032047.554.nullmai...@teltox.donarmstrong.com
Bug#687212: Wrong versions fixed in bug 687212
This bug (687212) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- 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/1348257060.063719.562.nullmai...@teltox.donarmstrong.com
Re: lilo removal in squeeze (or, please test grub2)
On Sun, 23 May 2010, Stephen Powell wrote: But withdrawing it from the distribution seems like overkill to me, especially since you want to withdraw it from Squeeze and not Squeeze+1. Lilo, as it exists today, works just fine for my purposes. If the maintainer doesn't wish to maintain it for another stable release cycle, and no one steps up to the plate to handle it, it should be removed. It's not like the removal of the package from the next release will cause your working version to be removed, after all... and you can presumably install manually later if you actually want it. Don Armstrong -- He was wrong. Nature abhors dimensional abnormalities, and seals them neatly away so that they don't upset people. Nature, in fact, abhors a lot of things, including vacuums, ships called the Marie Celeste, and the chuck keys for electric drills. -- Terry Pratchet _Pyramids_ p166 http://www.donarmstrong.com http://rzlab.ucr.edu -- 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/20100524030219.gk4...@teltox.donarmstrong.com
Re: unblock request: mdadm 2.6.9-3
On Tue, 14 Jul 2009, martin f krafft wrote: Hm, so the BTS pays attention to changelog stanza order (which is chronological) It's not necessarily chronological. without differentiating between experimental and unstable? Sort of. See http://wiki.debian.org/BugsVersionTracking part two. In short, every single version is a decendant of at most one version, which is the *penultimate* version listed in the changelog. If you're uploading experimental packages, the penultimate version should either be the preceeding experimental upload, or the unstable version which the experimental upload is based on. If you're uploading an unstable version, the experimental uploads should not show up in the changelog unless the unstable version is based upon a version which is in experimental. Don Armstrong -- Information wants to be free to kill again. -- Red Robot http://www.dieselsweeties.com/archive.php?s=1372 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: On installation media and firmware [Re: New section for firmware]
On Tue, 13 Jan 2009, Frans Pop wrote: On Tuesday 13 January 2009, Don Armstrong wrote: Sure it does; it's a set of the initial media which contains the non-free firmware in *addition* to the normal stuff contained on the fully DFSG-free media. [You'd just need this for CD1, the netinst, business card and cd images, and perhaps the m-a DVD.] The only additional user-facing complexity is the additional media and the need for users to be able to differentiate between the media types. I cannot make it more clear than this: the debian-boot and debian-cd teams are against any such solution. That's all fine and good, but why? Don Armstrong -- No matter how many instances of white swans we may have observed, this does not justify the conclusion that all swans are white. -- Sir Karl Popper _Logic of Scientific Discovery_ http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: On installation media and firmware [Re: New section for firmware]
On Sat, 03 Jan 2009, Frans Pop wrote: On Wednesday 24 December 2008, Don Armstrong wrote: It would be nice if you (or someone else) would then explain[1] why having a limited set of d-i images + cd images which contained the non-free firmware necessary for certain hardware to boot would be an intractable solution. From where I sit, the major issues with it would be: The major issue is that it does not solve all use-cases where firmware is needed. It does not solve the problem for netboot installations, nor for hd-media installations. Sure it does; it's a set of the initial media which contains the non-free firmware in *addition* to the normal stuff contained on the fully DFSG-free media. [You'd just need this for CD1, the netinst, business card and cd images, and perhaps the m-a DVD.] The only additional user-facing complexity is the additional media and the need for users to be able to differentiate between the media types. We don't want to have users jump through hoops. Having to burn an additional image just for firmware and having to switch to that image and then switch back to the installation image is IMO a major hoop. Having an additional image just for firmware was not what I suggested. Don Armstrong -- If you have the slightest bit of intellectual integrity you cannot support the government. -- anonymous http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On installation media and firmware [Re: New section for firmware]
Switching from -vote to -boot and -cd. On Wed, 24 Dec 2008, Frans Pop wrote: On Wednesday 24 December 2008, Don Armstrong wrote: 1: -vote really is the wrong list to discuss this on; Cc'ing debian-cd so knowledgeable people there can tell me I'm on crack. Second of all, the analysis for the impact on installations of firmware and why the D-I team would very much prefer to have any firmware included both on official CD images and in other D-I images (such as netboot, floppy and hd-media) has already been done and posted by Joey Hess ages ago and discussed repeatedly, both on the debian-boot list and on d-vote, and I'm quite certain also on d-project and/or d-devel. I don't think there's any argument against having firmware in a limited set of CD images and other d-i media which we distribute like we distribute non-free. Furthermore, the major portion of what I suggested doing has not been discussed recently on -project or -devel TTBOMK. It's a pity that we seem to need to explain this over and over again in random threads. It would be nice if you (or someone else) would then explain[1] why having a limited set of d-i images + cd images which contained the non-free firmware necessary for certain hardware to boot would be an intractable solution. From where I sit, the major issues with it would be: 1. Additional testing required 2. Increase in cdimage mirror utilization 3. Work to actual implement it I submit that the additional testing for #1 will be required when the firmware is placed on the images, regardless of whether we produce images not containing it, so the major burden of testing here seems to be to check that the firmware-related codepaths are only triggered when the firmware is there. #2 should be on the order of a few gigabytes, which is dwarfed by the increase in the size of the installation sets from version to version. [If our mirror operators will have problems with this, we've got far more serious ones.] #3 is what it is. Don Armstrong 1: You dealt with problems with having an entire set duplicated and a set of ancilliary issues, none of which I proposed. -- This message brought to you by weapons of mass destruction related program activities, and the letter G. http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#446838: Current daily builds have kernel 2.6.21 but udebs for 2.6.22
Package: debian-installer Severity: normal The current daily builds (10/15/2007) have the 2.6.21 kernel in vmlinuz and the initrd, but the udebs for 2.6.22. [Probably people are already aware of this, but just in case.] Don Armstrong -- Sentenced to two years hard labor (for sodomy), Oscar Wilde stood handcuffed in driving rain waiting for transport to prison. If this is the way Queen Victoria treats her prisoners, he remarked, she doesn't deserve to have any. http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#446838: Current daily builds have kernel 2.6.21 but udebs for 2.6.22
Package: debian-installer Severity: normal The current daily builds (10/15/2007) have the 2.6.21 kernel in vmlinuz and the initrd, but the udebs for 2.6.22. [Probably people are already aware of this, but just in case.] Don Armstrong -- Sentenced to two years hard labor (for sodomy), Oscar Wilde stood handcuffed in driving rain waiting for transport to prison. If this is the way Queen Victoria treats her prisoners, he remarked, she doesn't deserve to have any. http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] . -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#431145: BTS abuse (was: #431145 FTBFS: debian-installer fails to build on powerpc in sid)]
This bug's state is now set correctly, and the underlying question of whether the bug was actually fixed or not has been resolved. If you must respond to each other about items unrelated to the status of this bug, please do so privately or using other channels, not via the BTS. Don Armstrong -- For a moment, nothing happened. Then, after a second or so, nothing continued to happen. -- Douglas Adams http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug report #325360 (help against Spamming)
On Sat, 16 Sep 2006, Robert Roggenbuck wrote: since a couple of weeks the spam rate at my privat email address increases dramatically. After checking Google for my address ([EMAIL PROTECTED]) the bug report #325360 (http://bugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=325360) is the only page in the net where this address occures. That's merely the only page on the net which google has indexed. It's also present on bugs.debian.org, lists.debian.org, and has been distributed to anyone who reads -bugs-dist, -boot, or is on the PTS of installation-reports. Indeed, see: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=325360 and http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=63995 for the rationale why they aren't obfuscated currently. Don Armstrong -- Unix, MS-DOS, and Windows NT (also known as the Good, the Bad, and the Ugly). -- Matt Welsh http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Woody Installation
On Mon, 09 Sep 2002, Axel Schlicht wrote: NB: lilo typically doesn't just hang. It stops loading itself at very well defined points... it might be usefull to know exactly how far along in this sequence it had gotten. Unless I am mistaken, it probably stoped right after the LI. Somehow Linux doesn't get the order right. My bios shows the scsi drive as 0x80 / c: but thereafter you cant't run lilo. Revese it (ide first) and you won't have any problems. I assume of course, that you have setup the bios offset for the drives correctly. You almost definetly need a disk=/dev/sda bios=0x80 in your lilo.conf. [I happen to be booting right now from a machine with mixed ide/scsi with the scsi loading before the ide drive...] Finally, linux (the kernel) doesn't really have anything to do with the bootloader, other than the fact that the bootloader loads it, and the boot mapper interacts with the disks through it. Don Armstrong -- I never until now realized that the primary job of any emoticon is to say excuse me, that didn't make any sense. ;-P -- Cory Doctorow http://www.donarmstrong.com http://www.anylevel.com http://rzlab.ucr.edu msg22007/pgp0.pgp Description: PGP signature
