(I would add this to the Wiki page 
http://wiki.debian.org/Sarge2EtchUpgrade but someone made it immutable...)

#1.
Just noticed that /etc/network/interfaces is set up differently on new installs;
it uses udev/hotplug now by default, while it didn't before.

On old installs it looks like this:
------------
# The first network card - this entry was created during the Debian installation
auto eth0
iface eth0 inet dhcp
---------

While on new installs it looks like this:
----------
# This is a list of hotpluggable network interfaces.
# They will be activated automatically by the hotplug subsystem.
mapping eth0
        script grep
        map eth0

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp
------------

#2. 
Also noticed that on my old system /etc/network/run is a symlink to 
/dev/shm/network.  This was set up in the past by ifupdown.

Yet earlier installations will have it as a symlink to /etc/network.

However, new installations make it a directory.  I'm not entirely sure
why, but it's probably some interaction between udev and initscripts.postinst
and whatnot.

In any case, all of this is obsolete (!) and it probably ought to be a link to 
/lib/init/rw, which is a tmpfs mounted very early for purposes like this!  But 
that's another matter....

#3.
On new installs, the contents of /etc/default/rcS have changed.  It appears 
that this file didn't always belong to a package, or something, because it 
doesn't trigger the expected notice from dpkg for upgraded configuration files.
Notably DELAYLOGIN has changed value (from yes to no) and EDITMOTD has become 
obsolete.

-----
Some of this might actually be fixable by packages, while some of it should 
simply be noted in the release notes.  In any case, this stuff shouldn't remain
undocumented as it is now.

-- 
Nathanael Nerode  <[EMAIL PROTECTED]>

"It's just a goddamned piece of paper."
-- President Bush, referring to the US Constitution
http://www.capitolhillblue.com/artman/publish/article_7779.shtml


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to