Re: Firmware GR result - what happens next?
On Fri, Oct 14, 2022 at 10:52:01AM +0200, Santiago Ruano Rincón wrote: 5. transitional packages along with a helper package (that fails or success during install) to prompt the user so they add non-free-firmware section when needed. Is there any reason why you are not considering 5.? The danger we're trying to avoid is that a system with a working "something" (say, networking) gets upgraded, user reboots (or machine crashes, or there's a power failure, etc, etc.), the working "something" is now a not-working "something", and fixing it is really hard for the user who has no idea what happened and maybe doesn't have a network or a console or whatever any more. A package that fails during install will prevent the upgrade from completing, but will leave things in an in-between state until some action is taken, the upgrade restarted, and the upgrade manages to finish successfully. What happens if the reboot/crash/powercycle/etc happens during that in-between state? How do you make a firmware helper package that reliably prevents a kernel installation when the kernel doesn't have any dependencies on the firmware package, and also doesn't yank out the old working firmware, etc. I'm sure you can make the install explode, but making it reliably explode at just the right time seems harder. I guess this could all work, but I'm seeing a lot of potential for partial installs/failures with this approach and I suspect this would require transition code in a number of packages' preinsts, not a discrete "helper package".
Re: Firmware GR result - what happens next?
On Sun, Oct 02, 2022 at 08:21:31PM +0100, Steve McIntyre wrote: Plus, as Shengjing Zhu points out: we already expect people to manage the sources.list anyway on upgrades. We also try to avoid silent install problems that might or might not result in a system that doesn't boot properly.
Re: Firmware GR result - what happens next?
On Sun, Oct 02, 2022 at 03:53:00PM +0100, Steve McIntyre wrote: On Sun, Oct 02, 2022 at 04:43:47PM +0200, Michael Biebl wrote: What's the plan for upgraded systems with an existing /etc/apt/sources.list. Will the new n-f-f section added on upgrades automatically(if non-free was enabled before)? So this is the one bit that I don't think we currently have a good answer for. We've never had a specific script to run on upgrades (like Ubuntu do), so this kind of potentially breaking change doesn't really have an obvious place to be fixed. Is there a reason to not continue to make the packages available in non-free? I don't see a reason to force any change on existing systems.
ifupdown/dhcp
[apologies to package aliases getting this twice due to autocomplete fail] I've been trying to make sense of the NEWS item in isc-dhcp-client (that alternatives are needed) in combination with the functionality of ifupdown and what the implications are for debian upgrades generally. isc-dhcp-client as of the last upgrade is telling users to stop using it (the default dhcp client for debian). ifupdown (the traditional tool for managing networking on debian systems) has a Recommends on "isc-dhcp-client | dhcp-client". "dhcp-client" is a virtual package provided by "dhcpcanon" (version 0.8.5, which hasn't been touched in 4 years), "isc-dhcp-client", and "dhcpcd5" (which will trash a working configuration managed by ifupdown if installed, as it will try to take over interfaces currently set, e.g., to manual). This seems suboptimal at best. I believe that ifupdown will attempt to use udhcpd if installed, which should be a mostly-transparent change (except for the potential loss of lease information and any customization of dhclient scripts) but it isn't even on the ifupdown recommends list. ifupdown also (used to?) use pump, but that package went away a long time ago. So what's the path forward, maintaining compatibility and not breaking systems upgrading from current stable? Do we come up with a dhcpcd5 variant that *only* touches interfaces it is directed to touch via /etc/network/interfaces? Do we add udhcpcd to the "dhcp-client" virtual package and/or make it the default for ifupdown? Do we fork isc's dhcp suite and just continue to use dhclient? Revive pump? Something else?
ifupdown/dhcp
I've been trying to make sense of the NEWS item in isc-dhcp-client (that alternatives are needed) in combination with the functionality of ifupdown and what the implications are for debian upgrades generally. isc-dhcp-client as of the last upgrade is telling users to stop using it (the default dhcp client for debian). ifupdown (the traditional tool for managing networking on debian systems) has a Recommends on "isc-dhcp-client | dhcp-client". "dhcp-client" is a virtual package provided by "dhcpcanon" (version 0.8.5, which hasn't been touched in 4 years), "isc-dhcp-client", and "dhcpcd5" (which will trash a working configuration managed by ifupdown if installed, as it will try to take over interfaces currently set, e.g., to manual). This seems suboptimal at best. I believe that ifupdown will attempt to use udhcpd if installed, which should be a mostly-transparent change (except for the potential loss of lease information and any customization of dhclient scripts) but it isn't even on the ifupdown recommends list. ifupdown also (used to?) use pump, but that package went away a long time ago. So what's the path forward, maintaining compatibility and not breaking systems upgrading from current stable? Do we come up with a dhcpcd5 variant that *only* touches interfaces it is directed to touch via /etc/network/interfaces? Do we add udhcpcd to the "dhcp-client" virtual package and/or make it the default for ifupdown? Do we fork isc's dhcp suite and just continue to use dhclient? Revive pump? Something else?
Bug#852323: debian-installer: grub-installer not convert root= entry to UUID
I'd still expect the installer to DTRT with UUIDs in that case, though. I'm more thinking of a non-standard bootup / custom kernel or similar... Maybe I'm missing something here? Fire up a current debian netinst 9.2 iso in a kvm session (no special image or unusual hardware), go through an install. On reboot, look at the defult boot entry in grub, note that on the kernel command line root=/dev/sda1 (or somesuch) not UUID=X. This is very reproducible. In practice this results in an unbootable system for a non-expert user if they install from a USB stick that comes up as sda (so the grub entry is sdb) and they pull the USB stick out to boot into debian. If the kernel command line is manually fixed up, running update-grub after boot will create the expected root=UUID=X kernel command line. This is a regression from jessie, for which the exact same sequence of commands would result in a grub kernel command line with root=UUID=X Mike Stone
Bug#442856: tzsetup-udeb: tzsetup in installer has no UTC option
On Wed, Sep 19, 2007 at 01:09:06AM +0100, Colin Watson wrote: I think this is a weak argument, FWIW, considering how many countries have multiple timezones and so ask the timezone question with not much in the way of apparent ill effects. But: Michael, would an expert-mode question satisfy you? Sure. It's not having any option to select a timezone unrelated to my location that annoys me, not the possibility of having to do something extra. Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#442856: tzsetup-udeb: tzsetup in installer has no UTC option
On Tue, Sep 18, 2007 at 07:44:40PM +0200, you wrote: Up to now, the answer you got is that most of us don't feel an urgent need to work on this issue. The tone I read was that such a change wouldn't be allowed in the interest of user friendliness. If I misread that, I apologize. Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#442856: tzsetup-udeb: tzsetup in installer has no UTC option
On Tue, Sep 18, 2007 at 01:37:10PM -0300, Otavio Salvador wrote: While I agree with you Michael I also believe that majority of users won't need this and who does is experienced enough to change the system setting after the installation finishes. I can't believe that debian is turning into a system where you *have to* reconfigure your time zone after installation because offering too much choice is confusing. Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#442856: tzsetup-udeb: tzsetup in installer has no UTC option
On Tue, Sep 18, 2007 at 06:48:54AM +0200, Christian Perrier wrote: And I bet we can find dozens of such examples where not using the local time is pretty much as bad as using the same time everywhere. Great...but I thought debian was about letting people decide for themselves, not about boxing them into whatever you think is best? Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#442856: tzsetup-udeb: tzsetup in installer has no UTC option
On Mon, Sep 17, 2007 at 05:37:10PM -0400, Joey Hess wrote: Michael Stone wrote: The default debian syslog configuration, for one? IMHO, that's a bug. Well, it's less of a bug than including something as ambiguous as "EST" in a log file. :-P FWIW, I think all timestamps should use iso-8601 format, but even then I'd rather have my important systems using UTC rather than being at the whim of silly congressional DST changes. Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#442856: tzsetup-udeb: tzsetup in installer has no UTC option
On Mon, Sep 17, 2007 at 04:56:59PM -0400, Joey Hess wrote: What log file format does not include the time zone in the log? If timezone is included there is no repeat (ie, 2:30 am EDT != 2:30 am EST). The default debian syslog configuration, for one? I used to use UTC as the default time zone on my servers, but found needing to do the offset math myself to be rather more bother than it was worth. Avoiding time zone math is another excellent reason for global organizations to simply use UTC. Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#442856: tzsetup-udeb: tzsetup in installer has no UTC option
On Mon, Sep 17, 2007 at 06:33:22PM +0200, you wrote: Choosing a timezone has nothign to do with the HW clock being set to UTC so I'll assuml you mean choosing the UTC +00:00 timezone. Correct. The question about the "country or area" which you get as second question in default installs is not a question about the system's locale, it is really a question about the place the system is installed at. Fine. What I'm questioning is the logic that says UTC (*universal*) time shouldn't be an *option* no matter where you are. There are a lot of people who use UTC so that, e.g., their log files don't repeat hours once per year, regardless of where the machine happens to be physically located. Or, if this question is *solely* for time zone choice (and has no other side effects), it would be useful for that to be more clear in the prompt. (If this "has indeed been explained many many times", that would certainly suggest that the purpose of the question isn't clear enough--even your explanation of "it is really a question about the place the system is installed at" isn't true if it is *really* a question about what time zones you want to choose from.) I also don't remember a "go back" option (that is, ISTR that if you select US, you get a choice of a few time zones and no obvious way to do something else, like poke around for an "other" option), but I may be misremembering. Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#442856: tzsetup-udeb: tzsetup in installer has no UTC option
Package: tzsetup-udeb Severity: normal I'm not sure if this is the right package. The problem seems to be that in the etch installer, if you select a locale, e.g., en-US, you only get to choose time zones associated with that locale. It would be nice if every locale had UTC as an option, for those who don't want to keep their systems in local time (or even a way to choose from all available time zones, if their time zone doesn't have anything to do with the language they're choosing). It is, of course, possible to set this after the install is finished, but that's kind of a pain. Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#288475: Debian Sarge installation CD-ROM, built on 20041118
On Mon, Jan 03, 2005 at 11:09:34PM -0800, Steve Langasek wrote: Fileutils 4.1-10 is from woody, not from sarge. The version of fileutils in sarge is a transitional package only. Yes. Installing woody over top of sarge won't work. ISTR that the install cds use[d?] "stable" instead of "sarge" in the sources.list--I don't know why. Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#268434: no usb in 2.6 at install time
On Sat, Aug 28, 2004 at 12:34:49PM -0400, Joey Hess wrote: I tried the current d-i daily built netboot image with 2.6 and a usb keyboard and it worked. The loaded modules included usbkbd and usbhid, plus of course the correctly detected usb controller modules (both uhci-hcd and ehci-hcd in my case). If the installer is not loading the right module for your USB controller, we need lspci and lspci -n output for your system in order to fix it. I can't get that until next week. Is the info from the d-i hardware-summary useful? info: /bin/report-hw: /proc/bus/pci/devices: 00e8 8086265815 ff81 0020uhci_hcd info: /bin/report-hw: /proc/bus/pci/devices: 00e9 80862659 16 ff61 0020uhci_hcd info: /bin/report-hw: /proc/bus/pci/devices: 00ea 8086265a 12 ff41 0020uhci_hcd info: /bin/report-hw: /proc/bus/pci/devices: 00eb 8086265b 17 ff21 0020uhci_hcd Blindly loading all the usb controller modules is not safe, some of them crash some machines. Interesting. I'd expect the kernel driver to abort if couldn't recognize a device. Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#268433: no lvm on raid?
Package: debian-installer Raid partitions are not selectable as lvm pv's in debian-installer. This should be possible. Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#268434: no usb in 2.6 at install time
Package: debian-installer When booting from an rc1 cd on i386 the installer loads usbcore and usbkbd, but not uhci_hcd. This makes it hard to install using a usb keyboard. I'd suggest trying to load uhci_hcd, ohci_hcd, and ehci_hcd during the startup phase. Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#239887: beta3 boots sun e250 but fails to load root
Package: installation-reports Debian-installer-version: 2004-03-15 sparc business card Machine: Sun Enterprise 250 Processor: USparc-II Memory: 250M? Method: CDROM Root device: SCSI Base System Installation Checklist: Initial boot worked:[E] Comments/Problems: silo & kernel loaded fine, gave message about unable to mount root and kernel panic -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: intel e1000 gigabyte
On Mon, Jan 13, 2003 at 11:12:57PM +0100, Fabrice Lorrain (home) wrote: The 1650 comes with 2 Giga nics from Intel. That's right. The 2650 comes with 2 Giga nics from Broadcom (the best driver for those is tigon3 (tg3.o) since the 2.4.19 kernel). oh yeah, the inclusion of tg3 is something else that's nice in the new boot-floppies :) Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: intel e1000 gigabyte
On Sun, Jan 12, 2003 at 04:04:11PM -0600, Adam DiCarlo wrote: Let me know if you need me to test anything on a poweredge 2650. I can't test full install but we can check things are booting and net card is working. I've tested a few full installs on a couple of 2650's. It's one of the platforms I run through when Zomb sends out a call for "somebody please test new bf24". :) Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: intel e1000 gigabyte
On Sun, Jan 12, 2003 at 02:26:21PM -0600, Adam DiCarlo wrote: The PERC3/Di SCSI controller did seem supported, although it may be buggy, according to http://www.domsch.com/linux/> (cf "interrupt fix patch"). The only reference I saw that looked anything like that was in concert with a 2.4.9 kernel. (Ancient history.) The Intel (R) PRO/1000 Gigabit Ethernet Card (e1000) doesn't seem to be mainline kernel source. It is in 2.4.20. IIRC, they were in Zomb's experimental boot floppies. Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#140579: Report: tftpboot install successfull
On Fri, Jan 03, 2003 at 12:45:05PM -0600, Adam DiCarlo wrote: So why does that prevent us from giving an overview of the various options and providing some criteria to help users pick one or the other? It doesn't; that would be very good. I thought I had read that the goal was to eliminate all but one method. Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#140579: Report: tftpboot install successfull
On Thu, Jan 02, 2003 at 08:36:11PM -0600, Adam DiCarlo wrote: Um, no, I'm just talking about netboot options on i386. I understand that. But just like we have a bunch of architectures, we have a bunch of netboot options. You generally don't have a lot of choices about what your hardware supports. Telling someone whose card doesn't support pxe to use pxe because it's better is no more sensible than telling an m68k user to use the i386 boot floppies because i386 is better. Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#140579: Report: tftpboot install successfull
On Thu, Jan 02, 2003 at 04:40:50PM -0600, Adam DiCarlo wrote: overview of the different netboot options and which is best to use... "The one that works." You're asking for something like "review the currently supported architectures and explain which is the best one to use." Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Default disk partition table type?
On Wed, Dec 11, 2002 at 04:59:24PM -0700, Bdale Garbee wrote: No. Any new ia64 installation should use GPT, not FAT-style MSDOS labels. Are those the ones that put stuff at the end of the disk and break on linux with odd number of sectors? Mike Stone msg24757/pgp0.pgp Description: PGP signature
Bug#161999: boot-floppies: 3.0r0 install can end with no /etc/host{s,name}
On Tue, Sep 24, 2002 at 11:34:12AM +0200, Eduard Bloch wrote: >Hrm, even if I told Yann to tell more, I am confused a bit. etc/hosts >should be allways written (forced call in write_common_network()) unless >you have choosen DHCP, DHCP was set up (use_dhcp=1) but the interface >were down while writting the files. > >/etc/hostname may not be written if you did not run "Configure the >network" nor the "Configure hostname" steps successfully. IIRC, you'd need to rerun "configure the network" if dhcp bombs (which isn't intuitive, since at that point you should know that you can't configure the network :) Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Installation with USB floppy
On Fri, Sep 20, 2002 at 08:05:14PM +0200, you wrote: >The problem is: some people told me that there are Cardbus cards that >are driven by the drivers of the equal PCI cards. Including that drivers >into the kernel would make it impossible to load the driver after PCMCIA >start. Cardbus is basically pci, so most of the pc-cards with a cardbus interface shouldn't have seperate drivers. It's handled by the pci hotplug interface, and new cards should be recognized even if the driver is already loaded in the kernel. Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [d-i] debconf, partitioning widget?
On Thu, Jul 25, 2002 at 05:17:42PM +1000, Anthony Towns wrote: > I suppose it was a while ago now, but it's still a bit sad that people > are forgetting this is _exactly_ what we were saying for woody. Of course we didn't actually do that for woody. We changed a whole heck of a lot in b-f, moved to isolinux on the cd's, etc. -- Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: bootfloppy 1.44mb
On Sat, Jun 22, 2002 at 12:38:44PM +0200, johan van zuidam wrote: > Wich programm must I use to burn iso to an floppy instead off a cdrom? You didn't actually try to burn an iso to a floppy did you? There are some floppy images with a .bin extension, but those aren't iso's. -- Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#149698: Dell 2650 & Debian boot
On Wed, Jun 12, 2002 at 11:05:43PM +0200, Stephane Leclerc wrote: > We also need the bcm5700 Gbits Ethernet driver. No more EtherPro100+ inside That's something you'll have to add after installation, or with a custom kernel. (It's not included in the regular kernel source.) > bf2.4 is the only one to boot but do not work with the MegaRAID card. Doesn't work how? Did you load the module? (The megaraid driver is included with the bf2.4 kernel, but as a module rather than compiled in.) -- Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 3.0 (beta) fat32 resize with parted
On Tue, Jun 11, 2002 at 07:20:29PM +0300, Kai Hendry wrote: > is there a way i can drop to shell, extract parted onto the RAM disk and > use it? You can grab a parted rootdisk from ftp://ftp.gnu.org/gnu/parted/bootdisk/ and resize the partition independent of the debian installation. -- Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Installation report on AMD Duron
On Fri, May 31, 2002 at 12:03:39PM -0400, Joey Hess wrote: > Because it would be very confusing in the distro prompt, and woody is > frozen. You've lost me. -- Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Installation report on AMD Duron
On Fri, May 31, 2002 at 10:02:38AM -0600, Jeremiah Merkl wrote: > "woody" should never be a valid setting, in my opinion. Why? "woody" will always be a valid url until it's retired. -- Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Installation report on AMD Duron
On Thu, May 30, 2002 at 08:54:20PM -0400, Joey Hess wrote: > Matt Kraai wrote: > > * base-config sets the default value of apt-setup/distribution > >to the value of SUITE, but > > * its possible values are stable, testing, and unstable, so it > >falls back to the old default, stable. > > > > Joey, is this correct? If so, what (if anything) can be done? > > Yes that's right, and nothing at this time. Why can't "woody" just be a valid setting? -- Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Post-woody
On Mon, May 27, 2002 at 11:14:15PM +0200, Denis Barbier wrote: > On Mon, May 27, 2002 at 11:06:26PM +0200, Denis Barbier wrote: > [...] > > In order to avoid this annoyance, I suggested to only accept i18n-ed > > frontends. > > This suggestion does only make sense for interactive frontends, of course. Not really. Even people doing non-interactive installs might want to enter a name or some such with non-ascii characters. -- Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Severe limitation with flavor "bf2.4" !
On Fri, May 17, 2002 at 10:51:04AM +0200, Raphael Hertzog wrote: > Why didn't you put it as a module ? It's really confusing ... since > other Debian kernels have it as a module. I'd submit that installing things as modules with our system is *far* more confusing. Users seldom know what cryptic module goes with the nic with the completely unrelated name in their system. Having it "just work" is much preferable. We couldn't do this with the old isa devices, but pci detection isn't nearly as error-prone. Of course we still have work to do when you switch from the everything-compiled-in bf kernel to one of the optimized kernels and all your network devices, etc. disappear--but if debian was actually finished what would we do with ourselves? :) -- Mike Stone msg19897/pgp0.pgp Description: PGP signature
Re: b-f 3.0.23
On Tue, May 14, 2002 at 07:41:55PM +0200, Pierre Machard wrote: > if you video card is not recognise by X. For example on my laptop, > the default option in slack make my screen wider. With framebuffer it > feets on the whole screen, not only in a little rectangular area. With my laptop it makes the screen blank. Happens for a lot of people--that's why it isn't the default. -- Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Why is there a prompt for a root shell when the default linux kernel boots?
On Tue, Apr 30, 2002 at 03:23:06PM -0600, Erik Andersen wrote: > It is there as part of the installer to make like easier > for those wishing to do things that the installer does not > support by default. It has nothing whatsoever to do with > cramfs or the kernel. you're just wrong. the 2.4 kernel images have a feature to drop to a prompt at boot time. this will come up at every boot. i question the utility of this feature, because there's not much you can do from this shell, but it's much to late to change at this point. it is worth documenting. -- Mike Stone msg19531/pgp0.pgp Description: PGP signature
Re: Please test this woody cd image
On Fri, Apr 12, 2002 at 04:11:43PM +0200, Eduard Bloch wrote: > Btw, I would suggest this order: > > 1: Multiboot > 3: idepci > 2: bf2.4 > 4: compact > 5 and rest: vanilla > > So people with broken BIOSes have luck with the next CD-ROM. vanilla might be better on the second cd; the people with machines so old they don't multiboot properly also are more likely to isa stuff. -- Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Please test this woody cd image
On Fri, Apr 12, 2002 at 08:38:00AM -0500, Shyamal Prasad wrote: > It failed to boot an IBM Aptiva 2161-C8E desktop with a 1/19/1997 > BIOS. This 166Mhz Pentium box has been my trusty machine for 5 years, > and boots the potato r3 CD and also another woody netinst ISO (the one Well, I guess the question is do we want to support new machines or old machines; it doesn't seem that we can do both. (I'd vote for the former because we need to move forward, and it's not like we're removing the floppy boot option.) -- Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#142481: boot-floppies: tries to mount partition as XFS even after reinitialisation
On Fri, Apr 12, 2002 at 01:08:02AM +0200, Eduard Bloch wrote: > See subject. mke2fs and mkreiserfs do not touch the first 100 bytes of > the partition, but exactly this area (first 4 chars) is used to detect > the XFS filesystem. Yes. Unfortunately XFS is the only (AFAIK) linux filesystem that doesn't support a boot sector at the front of the partition. (For compatability with IRIX, which has a sensible boot loader.) -- Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: aic7896n, phoenix bios, apic
On Thu, Apr 11, 2002 at 07:10:32PM +0200, Eduard Bloch wrote: > I do not care. I included the IO-APIC support in first versions of the > kernel, but this caused problems reports from DELL laptop users. A > possible way would to enable it in kernel and forbid with boot options. > But it is too late to change many things now. Well, it might be a good idea to include it next time around. (Agree that it's too late this time.) The dell laptop problem showed up when you tried to transition certain states (E.g., ac->battery) but that's better than not booting at all. -- Mike Stone msg18679/pgp0.pgp Description: PGP signature
Re: dhcp known problem?
On Thu, Apr 11, 2002 at 12:18:53PM +1000, Herbert Xu wrote: > No it doesn't, the module is on the root disk. hmm. that didn't work for me, I'll try again tomorrow. -- Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dhcp known problem?
On Wed, Apr 10, 2002 at 10:44:36PM +0200, Eduard Bloch wrote: > #include > Michael Stone wrote on Wed Apr 10, 2002 um 03:06:11PM: > > CONFIG_PACKET is not compiled into the compact flavor, which makes net > > installs a bit of a PITA. Is that a known or intentional issue? > > It is compiled as module and loaded from the rootdisk. Works-for-me[tm]. Except that (unlike older versions) you need an extra floppy. -- Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Please test this woody cd image
On Wed, Apr 10, 2002 at 04:45:08PM -0400, Matt Zimmerman wrote: > On Wed, Apr 10, 2002 at 08:33:00PM +0200, Eduard Bloch wrote: > > And sorry, IMHO is idepci the worst kernel-image to be used for CD#1 as > > the only available flavor. > > It seems to work for a large number of users, and that is its only job, is > it not? Well, no. :) idepci is known to fail for people with scsi and new ide hardware, so it's not really the best choice either. There probably is no best choice, but a system with a menu where you can choose a choice is probably better than any arbitrary default. -- Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
dhcp known problem?
CONFIG_PACKET is not compiled into the compact flavor, which makes net installs a bit of a PITA. Is that a known or intentional issue? -- Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
woody floppy test
I tried the floppies with the 5/18 date from http.us, didn't get very far. Unformatted ramblings follow. I used the "compact" floppy set. The top-level floppies didn't have the 3c59x driver compiled in, and I wanted to avoid burning 3 driver floppies. The install process asked me for the driver floppy anyway. ISTR that the potato install asks whether you want to bother with it. DHCP config failed completely. First, dhclient seemed to be looking for /var/dhcp so it could write dhclient.leases. I created that directory, then it returned various errors: expr: not found [: 2: unexpected operator socket: Address family not supported by protocol Make sure to set CONFIG_PACKET=y and CONFIG_FILTER=y in your kernel config -- Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: woody release task needs help: package priorities
On Tue, May 15, 2001 at 04:28:37PM +0200, Tollef Fog Heen wrote: > You are assuming that talkd have buffer overflows, but you have no > proof of it. Of course a reasonably paranoid person would assume that buffer overflows exist and mitigate the risk as appropriate. Unless you can *prove* that the software is secure (proof by assertion or proof by "it hasn't happened yet" aren't) an assumption of security is unwarranted. -- Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: woody release task needs help: package priorities
On Tue, May 15, 2001 at 04:00:09PM +0300, Eray Ozkural (exa) wrote: > I sometimes have the feeling that too much security is breaking many > convenient features. It would be wrong to put in a program with known > vulnerabilities, but except that I don't see why you would want to > remove useful small programs. Because the vast majority of users probably don't care about all the possible features (and many don't even know they exist/are active) are are needlessly exposed to an avoidable security risk. Time and again we've seen programs, even those originally designed as secure alternatives, exploited by holes discovered years after they were first released. The *only* practical way to prevent this is to not run external services unless they're really required. Unless you care to come up with a proof of correctness... Didn't think so. -- Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: woody release task needs help: package priorities
On Mon, May 14, 2001 at 03:16:53PM +0200, Tollef Fog Heen wrote: > IMHO, a system without talk and talkd is too limited. Have it only > listen on loopback, if security is the problem. That's YHO. I obviously disagree. :) I haven't used talk in years, and you could probably find a large number of people who don't even know what it is. Shoul *your personal belief* that a system without talk is a broken system be enough to force make it part of a default debian system? -- Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: woody release task needs help: package priorities
On Sat, May 12, 2001 at 01:08:17PM +0200, Tollef Fog Heen wrote: > | > talk rather obsolete, but debatable > | > talkd not very secure for baseline > > I want those. They are very useful, and afaik, there are no security > problems with talkd. This is about you, it's about the general case; you can install them yourself with no problem. *Any* open port presents an additional risk--what value outweighs that risk in this case, for the general user? -- Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
