[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [Solved/is it a RC bug?] Re: Configuring both ipv4 and ipv6 with ifupdown



Paul TBBle Hampson wrote:
> On Sat, Jan 13, 2007 at 08:47:31PM -0500, Joey Hess wrote:
> > Paul TBBle Hampson wrote:
> >> The best place for it is prolly /etc/modules, created by
> >> debian-installer during the insatll. Rootskel contains the file, and
> >> hw-detect populates it. (Or so it seems)
> >> 
> >> So I'd put it as a bug against rootskel, so it can be default
> >> installed like 'loop' appears to be...
> 
> > That doesn't seem very appropriate as it would only address the issue on
> > newly installed systems, leaving upgraded systems unfixed.
> 
> I'm not sure you can really do much for newly-installed systems...
> 
> I think the ipv6 addresses in /etc/hosts similarly could only be
> automatically added on new installs.
> 
> I could be wrong about that though.

Yes, which suggests that adding ipv6 to /etc/hosts is not the best
solution to this problem. An alternative, for example, would be to have
ifup make sure it was loaded before upping an inet6 address.

> > (Also, rootskel has nothing at all to do with /etc/modules, and loop is
> > not listed in /etc/modules on newly installed systems.)
> 
> Weird. My recently-built-from-etch-installer-server got the loop module
> in its /etc/modules, and I didn't put it there.

The loop module is added in some cases if you use an encrypted filesystem.

-- 
see shy jo

Attachment: signature.asc
Description: Digital signature


Reply to: