On Wed, 20 Jun 2012 06:57:59 +0200, Michael R. Wayne
wrote:
Google is littered with messages from people who have 6.3 systems
and can no longer upgrade ports. It appears that a recent change
requires the version of make from 6.4.
While it would be ideal if freebsd.org would build a 6.4 make
Ronald Klop wrote:
Do you have a problem yourself or did you just found some messages on
google?
I presume you are running 6.3 yourself. Why don't you upgrade the OS to
6.4 or 7+, but you do upgrade the ports on an unsupported OS?
It is a little mind boggling. Unless required I wouldn't even re
20.06.2012 16:17, Mike Pumford пишет:
> Ronald Klop wrote:
>
>> Do you have a problem yourself or did you just found some messages on
>> google?
>> I presume you are running 6.3 yourself. Why don't you upgrade the OS to
>> 6.4 or 7+, but you do upgrade the ports on an unsupported OS?
>>
> It is a
Hi,
i just cvsup standard 8.2, that pulled me 8.2-p4 into the source tree.
when i made:
make buildkernel KERNCONF=SAMI
i got this:
cc -c -x assembler-with-cpp -DLOCORE -O2 -frename-registers -pipe
-fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmi
hi all,
i have two partitions: ada0p3.eli and ada1p3.eli
on bootprocess i must type a passphrase for ada0p3 and have ada0p3.eli.
next i type the passphrase for ada1p3 and i become: wrong key
when the bootprocess is finish and i login and type geli attach -k
/path to keyfile /dev/ada1p3 and i ty
I'm resending this email as I got no response the first time.
After over 3 years of uptime, I decided to upgrade one of my SUN boxes to
9-stable. However the new kernel didn't boot because of geom integrity check
issues. This I understand as I remember I had to use some weird tricks in the
pas
On Tue, Jun 19, 2012 at 9:45 PM, Dewayne Geraghty
wrote:
> Hi Olav,
> It seems that you're doing the same as I would, in that you start from a
> fresh base.
>
> I'd stay with csup, it is reliable and avoids the modula2 installation.
>
> Over the last 5 years, I have experienced the same weirdness
On 20.06.2012 19:14, Ruben de Groot wrote:
> Timecounters tick every 1.000 msec
> ada0 at ata2 bus 0 scbus0 target 0 lun 0
> ada0: ATA-7 device
> ada0: 66.700MB/s transfers (UDMA4, PIO 8192bytes)
> ada0: 152627MB (312581808 512 byte sectors: 16H 63S/T 16383C)
> ada0: Previously was known as ad0
>
On 20 jun 2012, at 18:34, Andrey V. Elsukov wrote:
> On 20.06.2012 19:14, Ruben de Groot wrote:
>> Timecounters tick every 1.000 msec
>> ada0 at ata2 bus 0 scbus0 target 0 lun 0
>> ada0: ATA-7 device
>> ada0: 66.700MB/s transfers (UDMA4, PIO 8192bytes)
>> ada0: 152627MB (312581808 512 byte secto
joerg_surmann wrote:
> i have two partitions: ada0p3.eli and ada1p3.eli
> on bootprocess i must type a passphrase for ada0p3 and have ada0p3.eli.
> next i type the passphrase for ada1p3 and i become: wrong key
> when the bootprocess is finish and i login and type geli attach -k
> /path to keyf
On Wed, Jun 20, 2012 at 10:26:02AM +0200, Ronald Klop wrote:
> On Wed, 20 Jun 2012 06:57:59 +0200, Michael R. Wayne
> wrote:
>
> >Google is littered with messages from people who have 6.3 systems
> >and can no longer upgrade ports. It appears that a recent change
> >requires the version of make
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/20/12 11:56, Michael R. Wayne wrote:
> On Wed, Jun 20, 2012 at 10:26:02AM +0200, Ronald Klop wrote:
>> On Wed, 20 Jun 2012 06:57:59 +0200, Michael R. Wayne
>> wrote:
>>
>>> Google is littered with messages from people who have 6.3
>>> system
On 2012-Jun-20 14:56:18 -0400, "Michael R. Wayne" wrote:
>Have the problem myself. There are ports with security vulnerabilities
So, you're happy to have vulnerabilities is the base system but not in
your ports?
>and the recent change broke make for ports.
Older releases generally require speci
13 matches
Mail list logo
