Re: [Devil-Linux-discuss] portmap in config?

[Heiko Z. <he...@zu...>]

It's fixed in CVS

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org

> -----Original Message-----
> From: Dominic Raferd [mailto:dl...@ed...]
> Sent: Saturday, September 17, 2011 1:57 AM
> To: dev...@li...
> Subject: Re: [Devil-Linux-discuss] portmap in config?
> 
> On 16/09/11 17:14, Heiko Zuerker wrote:
> > Quoting Dominic Raferd<dl...@ed...>:
> >
> >> I have moved both my machines to DL 1.4.3-2011-09-02 [server edition]
> >> from the previous DL 1.4.3 testing release. In one case I was asked
> >> to go through the normal 'upgrade' process at boot time, in the other I
> wasn't.
> >>
> >> On the machine that did not 'upgrade' I have an [unselected] entry
> >> for 'PORTMAP' in setup (both in the setup program [no explanatory
> >> text at the bottom though] and in /etc/sysconfig/config), on the
> >> machine that did 'upgrade' there is no such entry.
> > Not sure about that. If it's empty, simply remove it. Upgrade-config
> > will create any missing entries automatically.
> >
> >> Re-running save-config maintains these configurations i.e. they stay
> >> different.
> >>
> >> I try to maintain these machines as mirrors so this difference gets
> >> flagged, that's why I noticed it.
> >>
> >> Which is right? Is there a way to force the upgrade script to run (if
> >> it has not run when it should)?
> > Change the file /etc/Devil-release, so it reflects an older version.
> > This will invoke the upgrade-config during the next boot.
> >
> I did that but it still didn't run. So I remade the flash drive, this time
selecting
> Syslinux without serial console, and then it worked okay.
> 
> Originally for this machine I selected 'Syslinux with serial console'
> (just as an experiment, I have never used serial console), and found that
> most of the start-up information never appears on the screen, and
similarly
> the upgrade never appears.
> 
> After this successful upgrade, the /etc/sysconfig/config file was broken
(so
> that setup / services does not run) - the same situation that arose with
my
> other machine, see my Mantis report. I wonder if the new broken line in
this
> file, which I have to remove manually, is meant to relate to portmap?
> 
>
----------------------------------------------------------------------------
--
> BlackBerry&reg; DevCon Americas, Oct. 18-20, San Francisco, CA
> http://p.sf.net/sfu/rim-devcon-copy2
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss