Hi,
I noticed that back in April changes had been commited to allow ccache
to build -HEAD world so give it a try again on r256380.
The build process now fails at building libc.so.7 with error
/usr/bin/ld: this linker was not configured to use sysroots
cc: error: linker command failed with exit code
For those of you not aware, the latest version of the root-on-ZFS+GELI
in bsdinstall patch shipped as part of FreeBSD 10.0-BETA1 today. Please
test it and report any issues you have.
There is one known issue (already patched in our repo), where if you do
a GELI pool, the unencrypted /boot pool is
from Juergen Lock:
> If you mean it loads the kernel but then crashes instead of booting it
> then your grub2 version is missing this fix:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699002
> >I used Super Grub2 Disk image on the System Rescue CD written to USB sti
On 2013-10-14 16:53, Olivier Cochard-Labbé wrote:
> On Mon, Oct 14, 2013 at 1:14 AM, Allan Jude wrote:
>> Looking at the process states, connect and rpcreconnect, seem to suggest
>> something involving yp/nis or NFS or some such.
>>
> Oops, yes you've right, I've got an sub-folder on my homedir th
On Mon, Oct 14, 2013 at 1:14 AM, Allan Jude wrote:
> Looking at the process states, connect and rpcreconnect, seem to suggest
> something involving yp/nis or NFS or some such.
>
Oops, yes you've right, I've got an sub-folder on my homedir that was
NFS mounted and the NFS server was poweroff witho
On 10/14/13 10:00, Ian Lepore wrote:
> On Mon, 2013-10-14 at 09:51 -0700, Colin Percival wrote:
>> Yes, it's hard to store state on diskless systems... but I figured
>> that anyone building a diskless system would know to not create a
>> "run firstboot scripts" marker. And not all embedded systems
The first BETA build of the 10.0-RELEASE release cycle is now available
on the FTP servers for the amd64, i386, ia64, powerpc, powerpc64 and
sparc64 architectures.
The image checksums follow at the end of this email.
ISO images and, for architectures that support it, the memory stick images
are a
On Mon, 2013-10-14 at 09:51 -0700, Colin Percival wrote:
> Hi Nick,
>
> On 10/14/13 00:59, Nick Hibma wrote:
> > Sounds useful: We have nanobsd images that configure a hard disk if
> > present, but obviously only need to be run once.
> >
> > However: NanoBSD stores uses a memory disk for /etc an
On 10/14/13 05:07, Hiroki Sato wrote:
> Colin Percival wrote
> in <525b258f.3030...@freebsd.org>:
>
> cp> I've attached a very simple patch which makes /etc/rc:
>
> cp> +if ! [ -e /var/db/firstboot ]; then
> cp> + skip="$skip -s firstboot"
> cp> +fi
>
> At this stage, it is possible that /va
Hi Nick,
On 10/14/13 00:59, Nick Hibma wrote:
> Sounds useful: We have nanobsd images that configure a hard disk if present,
> but obviously only need to be run once.
>
> However: NanoBSD stores uses a memory disk for /etc and stores it's permanent
> scripts in /conf/* (/etc/rc.initdiskless) an
In article <59.81.16944.C6136525@cdptpa-oedge02> you write:
>Sorry for previous typo in From: line, missing right angle bracket at end.
>Then, in a finger error, I resent that message just before finding the error
>and making the needed correction.
>
>from Devin Teske:
>
>> I'm late to the party a
> > Removing src/contrib/bind9 from FreeBSD-10 will get criticised as:
> > "Calls itself a server OS, but no name server out of the box!"
> >
> > Please resist periodic urges to strip src/ towards just a tool set
> > capable of rebuilding itself. Tossing expected tools (even if a
> > port is mor
Allan Jude wrote:
> On 2013-10-13 15:10, Olivier Cochard-Labbé wrote:
> > I've got a frequent problem on my desktop (FreeBSD 10.0-ALPHA5 #8
> > r256200):
> > After few hours I can't acces to one of my folder: A simple "ls" in
> > this folder stucks, and all filesystem information started after
> >
On Mon, 14 Oct 2013, Andriy Gapon wrote:
on 14/10/2013 03:34 Keith White said the following:
I get the following assert failure with a recent current:
panic: solaris assert: dn->dn_datablkshift != 0, file:
/usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/dmu_tx.c,
line
Colin Percival wrote
in <525b258f.3030...@freebsd.org>:
cp> I've attached a very simple patch which makes /etc/rc:
cp> +if ! [ -e /var/db/firstboot ]; then
cp> + skip="$skip -s firstboot"
cp> +fi
At this stage, it is possible that /var/db does not exist because it
is before rc.d/mountcrit
On Mon, Oct 14, 2013 at 10:21 AM, Anton Shterenlikht wrote:
> >From davide.itali...@gmail.com Fri Oct 11 15:39:49 2013
>>
>>If you're not able to get a full dump, a textdump would be enough.
>>In your DDB scripts just remove the 'call doadump' step and you should
>>be done, unless I'm missing some
BTW, I see in dmesg:
Starting ddb.
ddb: sysctl: debug.ddb.scripting.scripts: Invalid argument
/etc/rc: WARNING: failed to start ddb
What is that about?
panic: uma_zfree: Freeing to non free bucket index.
cpuid = 0
KDB: stack backtrace:
db_trace_self(0x9ffc00158380) at db_trace_self+0x40
db
Florent Peterschmitt wrote:
> Le 20/09/2013 10:04, Ian FREISLICH a =E9crit :
> > Hi
> >
> > Is this libstdc++ fallout?
>
> You can try these patchs:
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dports/182110
I am sorry that I did not see your message until today. This fixes
the build. Thank
>From davide.itali...@gmail.com Fri Oct 11 15:39:49 2013
>
>If you're not able to get a full dump, a textdump would be enough.
>In your DDB scripts just remove the 'call doadump' step and you should
>be done, unless I'm missing something.
>Please adjust the script as well to include all the informa
Colin,
Sounds useful: We have nanobsd images that configure a hard disk if present,
but obviously only need to be run once.
However: NanoBSD stores uses a memory disk for /etc and stores it's permanent
scripts in /conf/* (/etc/rc.initdiskless) and/or /cfg (NanoBSD) so I doubt
whether the 'embe
On Mon, Oct 14, 2013 at 3:43 AM, Guido Falsi wrote:
> On 10/13/13 18:40, Joe Nosay wrote:
>
>> Will the pkg upgrade work with applications built from ports and not pkg
>> add $APPLICATION?
>>
>
> I'm not sure What you mean.
>
> the "pkg upgrade" command works only using binary packages, which can
On 10/13/13 18:40, Joe Nosay wrote:
Will the pkg upgrade work with applications built from ports and not pkg
add $APPLICATION?
I'm not sure What you mean.
the "pkg upgrade" command works only using binary packages, which can
come and "official" repository or your own one.
This is going to w
22 matches
Mail list logo
