On 03/12/10 02:13, Greg Byshenk wrote:
> I would put in a word for 'mergemaster -F' (or maybe '-iF') in such
> cases.
At this point the -U option is generally a safer bet. The only time this
won't work for you is when upgrading from an older -RELEASE where you've
never run mergemaster previously,
On 03/11/10 20:33, Garrett Cooper wrote:
> I've done a few RELENG_8_0 to STABLE-8 to 9-CURRENT upgrades lately
> and mergemaster was goofing up the contents a bit based on the RCS
> versions. I had to hand-edit a crapload of stuff going from 8 to 9,
> and I still don't trust mergemaster's automatic
On 03/11/10 19:18, Steve Bertrand wrote:
> On 2010.03.11 22:14, Xin LI wrote:
>> Looks like you have a stale configuration. DId you done mergemaster?
>
> Yes. I performed it as such:
>
> # mergemaster -Uia
The -a option is incompatible with -U AND -i (and -F for that matter).
However, it's my m
TB --- 2010-03-13 21:43:38 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-03-13 21:43:38 - starting RELENG_8_0 tinderbox run for amd64/amd64
TB --- 2010-03-13 21:43:38 - cleaning the object tree
TB --- 2010-03-13 21:44:04 - cvsupping the source tree
TB --- 2010-03-13 21:44:04 - /u
Am 03.03.2010 12:06, schrieb Jeremy Chadwick:
> On Wed, Mar 03, 2010 at 09:28:25AM +0100, Harald Schmalzbauer wrote:
>> Alexander Motin schrieb am 03.03.2010 09:18 (localtime):
>>> Harald Schmalzbauer wrote:
Alexander Motin schrieb am 23.02.2010 16:10 (localtime):
> Harald Schmalzbauer wro
On Sat, 13 Mar 2010 09:47:22 -0800
Jeremy Chadwick wrote:
> How do you tune the thresholds for the temperature or fan? If they're
> DIP switches, then chances are SAF-TE or SES-2 aren't involved and it's
> probably just some cheap/generic logic chip that does the work.
There is a switch for the
On Sat, Mar 13, 2010 at 10:57 AM, Svein Skogen (Listmail Account) <
svein-listm...@stillbilde.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 12.03.2010 15:20, Svein Skogen wrote:
> > I'm having trouble getting Amanda (2.6.1p2 from ports) to play nicely
> > with my hardware.
>
On Sat, Mar 13, 2010 at 06:32:59PM +0100, Torfinn Ingolfsen wrote:
> On Sat, 13 Mar 2010 08:38:48 -0800
> Jeremy Chadwick wrote:
>
> > That enclosure also doesn't state if it has a SAF-TE or SES-2 chip on
> > it. It's impossible to tell from the photos since the metallic
> > enclosure cover up t
On Sat, 13 Mar 2010 08:38:48 -0800
Jeremy Chadwick wrote:
> That enclosure also doesn't state if it has a SAF-TE or SES-2 chip on
> it. It's impossible to tell from the photos since the metallic
> enclosure cover up the backplane.
Unfortunately, the "manual" is very brief and lacks such technic
On Sat, Mar 13, 2010 at 02:11:13PM +0100, Torfinn Ingolfsen wrote:
> Update:
> Perhaps the problems I have with this machine[1] are related to the
> MB-455SPF[1] hard drive cage I am using. It has three power connectors,
> which distributes power to all five drives. The documentation doesn't
> say
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12.03.2010 15:20, Svein Skogen wrote:
> I'm having trouble getting Amanda (2.6.1p2 from ports) to play nicely
> with my hardware.
>
> Devices are:
>at scbus0 target 1 lun 0 (sa0,pass0)
>at scbus0 target 1 lun 1 (pass1,ch0)
>
On Fri, Mar 12, 2010 at 02:38:11PM -0800, Pyun YongHyeon wrote:
> It seems the PHY has no BRGPHY_MII_AUXSTS register as it does not
> seem to manufactured by Broadcom. Adding a special case to
> brgphy(4) does not look right. Does ukphy(4) work without problem?
> If so I think you can live with ukp
Update:
Perhaps the problems I have with this machine[1] are related to the
MB-455SPF[1] hard drive cage I am using. It has three power connectors,
which distributes power to all five drives. The documentation doesn't
say more about which ports gives power to which drives, but since it is
always dr
13 matches
Mail list logo
