On Tue, 2015-07-28 at 22:17 +0200, Ian FREISLICH wrote:
> David Wolfskill wrote:
> > My experience with SU+J is limited (and negative -- in large part,
> > because I tend heavily on "dump | restore" pipelines to copy file
> > systems, some of which are "live" at the time (danger mitigated by -L
> >
Glen Barber wrote:
> On Tue, Jul 28, 2015 at 10:17:38PM +0200, Ian FREISLICH wrote:
> > I found the actual problem. The mount point for /usr was mode 700
> > even though the root of the mounted filesystem on /usr was mode 755.
> > Did I explain that clearly (quite difficult because two things are
On 29/07/2015 05:48, Jamie Landeg-Jones wrote:
> Gary Palmer wrote:
>
>> As best that I can recall, the permissions of the directory underneath
>> the mount point has been causing problems like this for as long as I've been
>> using FreeBSD, which is over 20 years at this point. It's certainly
>
Gary Palmer wrote:
> As best that I can recall, the permissions of the directory underneath
> the mount point has been causing problems like this for as long as I've been
> using FreeBSD, which is over 20 years at this point. It's certainly
> bit me in the distant past.
I concur. I always make
On Tue, Jul 28, 2015 at 10:17:38PM +0200, Ian FREISLICH wrote:
[trim]
> So, a couple of fscks found some problems, but none causing this.
>
> I found the actual problem. The mount point for /usr was mode 700
> even though the root of the mounted filesystem on /usr was mode 755.
> Did I explain th
On Tue, Jul 28, 2015 at 10:17:38PM +0200, Ian FREISLICH wrote:
> I found the actual problem. The mount point for /usr was mode 700
> even though the root of the mounted filesystem on /usr was mode 755.
> Did I explain that clearly (quite difficult because two things are
> the same thing, although
David Wolfskill wrote:
> My experience with SU+J is limited (and negative -- in large part,
> because I tend heavily on "dump | restore" pipelines to copy file
> systems, some of which are "live" at the time (danger mitigated by -L
> flag for dump).
As an aside, mine has been pretty positive, exce
Glen Barber wrote:
> On Tue, Jul 28, 2015 at 07:31:56PM +, Glen Barber wrote:
> > On Tue, Jul 28, 2015 at 08:16:16PM +0200, Ian FREISLICH wrote:
> > > Hi
> > >=20
> > > I cannot for the life of me figure out why this is so:
> > >=20
> > > As non-root:
> > > [zen] /usr/lib $ file libgcc_s.so
> >
On Tue, Jul 28, 2015 at 07:31:56PM +, Glen Barber wrote:
> On Tue, Jul 28, 2015 at 08:16:16PM +0200, Ian FREISLICH wrote:
> > Hi
> >
> > I cannot for the life of me figure out why this is so:
> >
> > As non-root:
> > [zen] /usr/lib $ file libgcc_s.so
> > libgcc_s.so: broken symbolic link to .
On Tue, Jul 28, 2015 at 08:16:16PM +0200, Ian FREISLICH wrote:
> Hi
>
> I cannot for the life of me figure out why this is so:
>
> As non-root:
> [zen] /usr/lib $ file libgcc_s.so
> libgcc_s.so: broken symbolic link to ../../lib/libgcc_s.so.1
>
> As root:
> [zen] /usr/lib # file libgcc_s.so
> l
Hi
I cannot for the life of me figure out why this is so:
As non-root:
[zen] /usr/lib $ file libgcc_s.so
libgcc_s.so: broken symbolic link to ../../lib/libgcc_s.so.1
As root:
[zen] /usr/lib # file libgcc_s.so
libgcc_s.so: symbolic link to ../../lib/libgcc_s.so.1
Only on one of my machines, all
On Tue, May 22, 2012 2:27 pm, Jeremie Le Hen wrote:
> This is expected I think, as "make buildenv" defines $_SHLIBDIRPREFIX
> which is used to make the toolchain use libraries built during stage 4.2
> of buildworld.
>
> Just run "make installworld" with the correct DESTDIR and your chroot
> will be
Ilya,
On Mon, May 21, 2012 at 01:43:39PM +0200, Ilya Bakulin wrote:
> On Mon, May 21, 2012 12:36 pm, Jeremie Le Hen wrote:
> > Can you provide the exact commands you have used to create your chroot?
> >
> Sure!
>
> 1. The build host is FreeBSD 8.2-RELEASE-p3 amd64
> 2. Directory where project res
On Mon, May 21, 2012 12:36 pm, Jeremie Le Hen wrote:
> Can you provide the exact commands you have used to create your chroot?
>
Sure!
1. The build host is FreeBSD 8.2-RELEASE-p3 amd64
2. Directory where project resides ($PROJROOT):
/home/kibab/repos/freebsd-cap-git
2. FreeBSD-CURRENT sources are
Hi,
On Sun, May 20, 2012 at 07:54:22PM +0200, Ilya Bakulin wrote:
> Hi all,
> I have compiled FreeBSD-CURRENT amd64 (fresh checkout from today, git
> revision 46b12ff6d8ab4f736d155646ae32133083e1da05 -- from official
> FreeBSD github mirror) and installed it in custom location (DESTDIR=
> make
Hi all,
I have compiled FreeBSD-CURRENT amd64 (fresh checkout from today, git
revision 46b12ff6d8ab4f736d155646ae32133083e1da05 -- from official
FreeBSD github mirror) and installed it in custom location (DESTDIR=
make installworld).
After chrooting to installed system and trying to compile an
16 matches
Mail list logo
