Bug#65599: Problem with update-alternatives
Package: base Version: 2.2.15-06-07 In the /etc/alternatives directory, there is a file that says to use the update-alternatives command to change alternative programs. There is a manpage, but no update-alternatives command. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#65606: No installation of LILO to logical partition?
Package: base Version: 2.2.15-06-07 When I installed Debian "potato" I was not allowed to install LILO to a logical partition. It says LILO can't be installed there, but in fact it can. I reconfigured LILO after install to lie in the logical partition ,and it worked. This may or may not work with all sotck Debian bootloaders, but I can boot the logical partition with BootMagic(non-free program) and I think I can use xosl (xosl.org) to boot it also. I think the installer should permit installation of LILO to a logical partition. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#437018: Network shouldn't be used/enforced on non-network installs
Package: debian-installer Version: 20070308 Priority: wishlist During installs from CD-ROM and DVD media, users are still currently prompted to set up the network and download security fixes from the network. However, many (quite possibly most) users who use the full-blown install media (as opposed to the netinstall CD) do not have access to a network connection which is functional during the install and as such have to navigate through these steps and the inevitable errors they produce for no reason at all. It would be GREAT if the network-related steps would be skipped/bypassed on a default install from non-netinstall media. Users then could configure the network at their leisure after the install using the tools they prefer (NetworkManager etc). Could this be considered?
Bug#437013: d-i doesn't properly understand LVM groups with active snapshot volumes
Package: debian-installer Version: 20070308 I recently used d-i to install Debian Etch to a volume that was part of an LVM volume group that contained an active snapshot volume. While the installation proceeded fine, it issued an error message to the effect that something was wrong with the partition table (can't recall the exact message). This should be fixed for future d-i releases...
Bug#437016: d-i inconsistent in definition of GB used
Package: debian-installer Version: 20070308 During an Etch install, the partitioning step is inconsistent about the definition of a gigabyte. For example, when LVM volumes are created, the definition of GB used for specifying their size is (1024*1024*1024) bytes. However, the definition of GB used on the main partitioning screen is a billion (1000*1000*1000) bytes. Thus, a 10.0GB LVM volume will appear confusingly as 10.6 GB on the main partitioning screen. This should be fixed in a future d-i build.
Bug#437018: Network shouldn't be used/enforced on non-network installs
I guess having it look for a network in the background and silently fail would be preferable, in any case. Is this doable? On 8/10/07, Christian Perrier <[EMAIL PROTECTED]> wrote: > > Quoting Tim Hull ([EMAIL PROTECTED]): > > > It would be GREAT if the network-related steps would be skipped/bypassed > on > > a default install from non-netinstall media. Users then could configure > the > > network at their leisure after the install using the tools they prefer > > (NetworkManager etc). Could this be considered? > > Probably not. Having a system with immediate support for security > updates is one of the key features of Debian. Doing this would defeat > that design choice. > > I'm letting other D-I team members give their advice and decide > whether this bug report should be kept or marked "wontfix". > > -- > > > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.6 (GNU/Linux) > > iD8DBQFGu/1r1OXtrMAUPS0RAvwAAJoCbz6zN8M4ZXBWVjIAix7ekHr1gwCgoWOg > dUzSO/6xCpIaWOHTn6NOsxs= > =eJ8o > -END PGP SIGNATURE- > >
Bug#437018: Network shouldn't be used/enforced on non-network installs
>
>
> Of course security updates should be enabled by default, and I do agree
> that it's sensible for the system to _ask_ to try to install security
> updates even if there's no network. But there are cases where security
> updates don't make much sense, and I do think that the current behaviour
> ("there's no working connection to the Internet, but what the heck,
> we'll try anyway, and if it doesn't work, the admin will have to wait
> for the connection to time out an insane number of times") is a bug.
In my circumstance, I've been installing on a system with both an Ethernet
card (supported during the install) and a wi-fi card (supported with
non-free madwifi driver). I currently don't use the ethernet - wi-fi is all
I use. When I go back to school (in about 2 weeks or so), I'll have
Ethernet, but it uses 802.1x authentication so it still will be worthless
for the install.
Furthermore, even if I had networking durring the install, I do NOT like the
idea of downloading updates during the install without prompting - sometimes
I'm using a satellite internet connection with some pretty hefty bandwidth
quotas and would MUCH rather grab these updates during off-peak hours. I
had this cause bandwidth throttling in the past when I was installing Debian
in a VM with network connectivity during the install.
Anyway, it seems like there should be a "would you like to use the network"
question or option in the installation boot menu. As it stands, the current
behavior is quite bad for those who either have no usable network during an
install (which I would have to guess is sizable) and even worse for those
who *do* have networking but which have limited bandwidth that they don't
want sucked up at will.
Tim
Bug#437013: d-i doesn't properly understand LVM groups with active snapshot volumes
The message states: Unable to determine geometry of file/device. You should not use Parted unless you REALLY know what you're doing! The log is attached... On 8/10/07, Otavio Salvador <[EMAIL PROTECTED]> wrote: > > "Tim Hull" <[EMAIL PROTECTED]> writes: > > >Package: debian-installer > >Version: 20070308 > >I recently used d-i to install Debian Etch to a volume that was part > of > >an LVM volume group that contained an active snapshot volume. While > >the installation proceeded fine, it issued an error message to the > >effect that something was wrong with the partition table (can't > recall > >the exact message). This should be fixed for future d-i releases... > > Can you check your installed system on /var/log/installer/ and see if > the error message is avaiable there? In case you find it, you can send > the logfile, bziped, to the bug report. > > -- > O T A V I OS A L V A D O R > - > E-mail: [EMAIL PROTECTED] 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." > partman.bz2 Description: BZip2 compressed data
Bug#437018: closed by Joey Hess <[EMAIL PROTECTED]> (Re: Bug#437018: Network shouldn't be used/enforced on non-network installs)
-- Forwarded message --
> From: Joey Hess <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Date: Wed, 15 Aug 2007 16:13:23 -0400
> Subject: Re: Bug#437018: Network shouldn't be used/enforced on non-network
> installs
> Wouter Verhelst wrote:
> > ("there's no working connection to the Internet, but what the heck,
> > we'll try anyway, and if it doesn't work, the admin will have to wait
> > for the connection to time out an insane number of times")
>
> If there's no network connection *at all*, there is no timeout to wait
> for. Try it yourself:
>
> [EMAIL PROTECTED]:/home/joey>ifdown wlan0
> ...
> [EMAIL PROTECTED]:/home/joey>time apt-get update
> ...
> 0.06user 0.04system 0:00.21elapsed 48%CPU (0avgtext+0avgdata
> 0maxresident)k
> 0inputs+0outputs (0major+3403minor)pagefaults 0swaps
> zsh: exit 100 command time apt-get update
>
> In the edge case where there is a network connection with a default route
> that
> doesn't work, you get to wait for a timeout. We have discussed this
> before,
> and this is a sufficiently uncommon enough case that it's not worth asking
> in every install whether d-i should hit the network[1]. If you're in such
> a
> situation, unplug your network cable, or fix your network before trying to
> install Debian, or run the install in expert mode and tell it not to set
> up a network connection.
I see what you're saying. However, one must still navigate the d-i steps
related to networking in any case, and in my experience I've had to wait for
a DHCP timeout on a disconnected network card. IMHO, it seems logical to add
a "Don't use a network for this install" option as a choice on the screen
which lists the available network cards. If that is selected, the updates
step and all network-related steps would be skipped entirely.
I think that would be the ideal solution - it would make the install much
more friendly to users who don't have networking during the install. This
situation is probably more common than you think, since it includes every
wi-fi-only user as well as anyone who uses authentication methods like
802.11x.
Could this be considered?
Tim
Tim
