Frans Pop wrote:
So after today's changes it will leave /media/cdrom instead of /cdrom.
Guess we should remove that dir again in finish_install.d for hd_media
installs? We'd need to keep an indicator that the dir was created by
base-installer and not by partman.
I don't think it
On Friday 12 March 2010, Joey Hess wrote:
I don't think it particularly matters if there's a stray /media/cdrom.
I could always plug in a usb cd drive.
OK. Let's give it a try as it is now then. I will uploaded base-installer
and apt-setup to start with.
Colin,
At the risk of invoking your
On Wednesday 10 March 2010, maximilian attems wrote:
applications that still rely on a toplevel /cdrom
are likely very buggy and should be kicked.
nuke etch compatibility link.
Except that D-I itself still uses it :-/
We'll need to change that first...
--
To UNSUBSCRIBE, email to
tag 573252 pending
thanks
On Thursday 11 March 2010, Frans Pop wrote:
On Wednesday 10 March 2010, maximilian attems wrote:
applications that still rely on a toplevel /cdrom
are likely very buggy and should be kicked.
nuke etch compatibility link.
Except that D-I itself still uses it
On Thu, Mar 11, 2010 at 06:09:07PM +0100, Frans Pop wrote:
On Thursday 11 March 2010, Frans Pop wrote:
On Wednesday 10 March 2010, maximilian attems wrote:
applications that still rely on a toplevel /cdrom
are likely very buggy and should be kicked.
nuke etch compatibility link.
On Thursday 11 March 2010, you wrote:
/cdrom was only obsoleted in etch by a combination of prayer and wishful
thinking. apt-cdrom still relied on it until very recently, when
Michael Vogt did some work on it.
Hmm. It could be that back then only the automatic unmounting was fixed.
I'll
On Thursday 11 March 2010, Colin Watson wrote:
If you don't bind-mount /target/cdrom in base-installer, how do you
ensure that we use the same CD for base installation as was used to boot
the installer?
You cannot ensure that even if you do bind mount it as the BIOS' idea of
what is the first
On Thursday 11 March 2010, Frans Pop wrote:
No, we no longer bind mount /target/cdrom. We used to bind mount it
permanently, but that was changed with the reintroduction of multi-cd
support. Instead we always leave it up to apt-cdrom to mount/umount the
CD as (and only as long as) needed.
Oh,
On Thursday 11 March 2010, you wrote:
On Thursday 11 March 2010, Frans Pop wrote:
No, we no longer bind mount /target/cdrom. We used to bind mount it
permanently, but that was changed with the reintroduction of multi-cd
support. Instead we always leave it up to apt-cdrom to mount/umount
On Thursday 11 March 2010, Frans Pop wrote:
On Thursday 11 March 2010, you wrote:
On Thursday 11 March 2010, Frans Pop wrote:
No, we no longer bind mount /target/cdrom. We used to bind mount it
permanently, but that was changed with the reintroduction of
multi-cd support. Instead we
On Thu, 11 Mar 2010, Frans Pop wrote:
On Wednesday 10 March 2010, maximilian attems wrote:
applications that still rely on a toplevel /cdrom
are likely very buggy and should be kicked.
nuke etch compatibility link.
Except that D-I itself still uses it :-/
We'll need to change that
I installed the alpha from usb stick, onto a system with no cdrom drive,
and a /cdrom directory (not symlink) was left behind. I have not worked
out which component is responsible.
--
see shy jo
signature.asc
Description: Digital signature
On Friday 12 March 2010, Joey Hess wrote:
I installed the alpha from usb stick, onto a system with no cdrom drive,
and a /cdrom directory (not symlink) was left behind. I have not worked
out which component is responsible.
/var/lib/dpkg/info/base-files.preinst has:
if [ -d /cdrom ]; then
On Friday 12 March 2010, Frans Pop wrote:
On Friday 12 March 2010, Joey Hess wrote:
I installed the alpha from usb stick, onto a system with no cdrom
drive, and a /cdrom directory (not symlink) was left behind. I have
not worked out which component is responsible.
On Friday 12 March 2010, Joey Hess wrote:
I installed the alpha from usb stick, onto a system with no cdrom drive,
and a /cdrom directory (not symlink) was left behind. I have not worked
out which component is responsible.
Duh. I looked at the code earlier today. It's base-installer of course
On Friday 12 March 2010, Frans Pop wrote:
On Friday 12 March 2010, Joey Hess wrote:
I installed the alpha from usb stick, onto a system with no cdrom
drive, and a /cdrom directory (not symlink) was left behind. I have
not worked out which component is responsible.
So after today's changes
Package: partman-target
Version: 65
Severity: wishlist
Tags: patch
applications that still rely on a toplevel /cdrom
are likely very buggy and should be kicked.
nuke etch compatibility link.
diff --git
a/packages/partman/partman-target/finish.d/fstab_removable_media_entries
17 matches
Mail list logo
