On Tue, Nov 01, 2005 at 09:31:37AM +1000, Joel Hatton wrote:
> > Ah, that's they key. aliases don't work with dhclient at the moment for
> > most interfaces because the interfaces generate bogus link events when
> > aliases are modified. We hope to fix this, but it's going to take some
> > time.
>
> Ah, that's they key. aliases don't work with dhclient at the moment for
> most interfaces because the interfaces generate bogus link events when
> aliases are modified. We hope to fix this, but it's going to take some
> time.
Ok - thanks. I'm fortunate at the moment that I've stopped using the
On Mon, Oct 31, 2005 at 10:50:38AM +1000, Joel Hatton wrote:
> I said:
> >
> > DHCP configuration - for some reason my machine didn't acquire a
> > default route on boot, but rerunning the dhclient script after
> > boot caused the interface to be set up again successfully. I
> > ha
> I said:
> >
> > DHCP configuration - for some reason my machine didn't acquire a
> > default route on boot, but rerunning the dhclient script after
> > boot caused the interface to be set up again successfully. I
> > haven't looked into this further yet, I'll repost if it is a
>
I said:
>
> DHCP configuration - for some reason my machine didn't acquire a
> default route on boot, but rerunning the dhclient script after
> boot caused the interface to be set up again successfully. I
> haven't looked into this further yet, I'll repost if it is a
>
> Just a few words on that point ... after some use of mergemaster, it
> seems to me that a big part of /etc have to be update blindly for most
> users (things in rc.d, and some other places where there's files that
> haven't to changed or that are system script that most users won't
> modify.)
>
On Oct 27, 2005, at 4:32 PM, Bryan Fullerton wrote:
Yes, this is most annoying. I haven't gotten around to submitting a
ports PR complaining about /etc/rc.d/amavisd -- it's so obvious I
figured it must have been intentional, but I can't figure out how it
makes sense organizationally for a port
On 10/26/05, Patrick Lamaizière <[EMAIL PROTECTED]> wrote:
> Yes but be carefull, by sample amavisd-new uses scripts in /etc/rc.d and not
> in /usr/local/etc/rc.d. "Why the mail server does not work anymore ?"
Yes, this is most annoying. I haven't gotten around to submitting a
ports PR complaining
Le Mercredi 26 Octobre 2005 02:46, Joel Hatton a écrit :
> most files in /etc/rc.d changed, so installing them all with
> mergemaster was laborious - a note in UPDATING similar to that for
> 5.x:
>
> "The simplest solution is an 'rm -rf /etc/rc.d/*' and then
>
On Wed, Oct 26, 2005 at 10:46:43AM +1000, Joel Hatton wrote:
> /etc/usbd.conf has lost the [Device] configuration for the mouse,
> which although doesn't prevent the mouse from working, it did mean
> that I had to add those lines again so that I could turn on '-z
> 4' for th
On Wed, Oct 26, 2005 at 10:46:43AM +1000, Joel Hatton wrote:
> most files in /etc/rc.d changed, so installing them all with
> mergemaster was laborious - a note in UPDATING similar to that for
> 5.x:
>
> "The simplest solution is an 'rm -rf /etc/rc.d/*' and then
>
Hi,
I've just overnight upgraded from 5 stable to 6 on one of my workstations.
As I'm becoming used to expecting, this was a very smooth migration - my
perennial thanks to all of the developers who make this type of operation
almost trivial.
A couple of notes on the extremely few 'gotchas' I expe
12 matches
Mail list logo