So, what I have read and seen

[Seu Aba]

Is that the lot of you have treated a homeless man with disrespect simply
because he was open and honest about what goes on in his life.
I have also read about his ideas and they make perfect sense to me. Aiding
and assisting the blind while standing up for others is not a bad thing.
The reaction he received from most of you borders on harassment which is
illegal in a lot of places.
He did not ask any of you for anything and refused both money and help to
prove his honesty.
Not only that, but, you allow someone known for being rude to convince you
that the man did wrong without bothering to gather any other information.
If you are not aware of the rudeness and social manipulation of deRaadt,
you need to rethink things through. More than one person left OpenBSD
because of his lack of respect.
It also seems that David Wolfskill - one of the info@freebsd members, had
treated this homeless man with disrespect.

There is something seriously wrong with all of you to treat such a person
with disdain and disrespect.

Don't say shit.

This man received news that his mother was raped and beat and some of you
make jokes about that situation.

What in the fuck is wrong with you people?

What if that happened to your mother
or sister
or wife
or daughter?
How would you handle the situation?

Don't say a fucking thing.

All of you owe that man an apology.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Fwd: 11.0: head/lib/libsysdecode/Makefile for . . ./libsoft/usr/include uses CPP when XCPP needed? [Makefile.libcompat issue]

[Mark Millard]

The below forwards an example of a possibly more general issue not necessarily 
limited to arm context of the example: in a cross compile context the host CPP 
is in use via Makefile.libcompat not involving "${XCPP}" and so various macro 
checks for the target context fail to work.

[The below and the material leading up to it was originally posted to 
freebsd-arm.]

===
Mark Millard
markmi at dsl-only.net

On 2016-Apr-4, at 2:02 PM, Mark Millard  wrote:

As a fix for

>> --- all_subdir_lib/libsysdecode ---
>> In file included from :17:
>> In file included from 
>> /usr/obj/clang/arm.armv6/usr/src/libsoft/usr/include/dev/nvme/nvme.h:36:
>> In file included from 
>> /usr/obj/clang/arm.armv6/usr/src/libsoft/usr/include/sys/param.h:135:
>> In file included from 
>> /usr/obj/clang/arm.armv6/usr/src/libsoft/usr/include/machine/param.h:49:
>> /usr/obj/clang/arm.armv6/usr/src/libsoft/usr/include/machine/acle-compat.h:182:4:
>>  error: Unable to determine architecture version.
>> #  error Unable to determine architecture version.
>>  ^

I tested building an amd64 -> arm cross-build based on

> # svnlite diff Makefile.libcompat
> Index: Makefile.libcompat
> ===
> --- Makefile.libcompat(revision 297514)
> +++ Makefile.libcompat(working copy)
> @@ -90,6 +90,7 @@
>   DTRACE="${LIB$COMPATDTRACE:U${DTRACE}}"
>  LIBCOMPATWMAKEFLAGS+= CC="${XCC} ${LIBCOMPATCFLAGS}" \
>   CXX="${XCXX} ${LIBCOMPATCFLAGS} ${LIBCOMPATCXXFLAGS}" \
> + CPP="${XCPP}" \
>   DESTDIR=${LIBCOMPATTMP} \
>   -DNO_CPU_CFLAGS \
>   MK_CTF=no \

and it completed without getting an "error:". So this addition to 
Makefile.libcompat may be one option for a fix.

===
Mark Millard
markmi at dsl-only.net


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Packaging the FreeBSD base system with pkg(8)

[John Baldwin]

On Tuesday, April 05, 2016 12:22:49 PM Gary Jennejohn wrote:
> On Tue, 5 Apr 2016 10:22:04 +0100
> David Chisnall  wrote:
> 
> > On 5 Apr 2016, at 10:07, Gergely Czuczy  wrote:
> > > 
> > > Also, quite often entries from the base system are changed
> > > manually, think of root's/toor's password.  Are such cases
> > > going to be dealt with properly between upgrades, including
> > > self-built-and-packaged base systems?  Currently it can be a
> > > PITA with mergemaster to handle things like master.passwd
> > > properly between upgrades, automation so far wasn't famous on
> > > doing it properly. 
> > 
> > Mergemaster uses a 2-way merge.  It has the version that you
> > have installed and the version that's being proposed for
> > installation.  Etcupdate and pkg perform a 3-way merge.  It has
> > the pristine version, the version that you have made changes
> > to, and the new version.  If you have changed an entry and so
> > has the package, then you will get a conflict that you have to
> > resolve manually.  If you have added lines and so has the
> > upstream version, then that should cleanly apply.  Similarly,
> > if you and upstream have both modified different lines, then
> > there should be no problem.
> > 
> 
> Will there be an option not to merge?  I never update /etc when
> I do installworld because what I have works for me and I see no
> need to make any changes to a working system.

Some parts of /etc (like /etc/rc.d) aren't really config files and need to
be updated.  You wouldn't have working wireless after a 10 -> 11 upgrade if
you didn't update /etc/rc.d (and some helper scripts those use like
/etc/rc.subr and /etc/network.subr).  The files in /etc that are config
files rarely change in FreeBSD in my experience compared with the
"non-config" files like /etc/rc.d/*.  I rarely encounter conflicts when using
etcupdate personally, but both etcupdate and mergemaster can be configured to
ignore individual files (or globs of files).

-- 
John Baldwin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Packaging the FreeBSD base system with pkg(8)

[Gary Jennejohn]

On Tue, 5 Apr 2016 13:42:48 -0400 (EDT)
Benjamin Kaduk  wrote:

> On Tue, 5 Apr 2016, Gary Jennejohn wrote:
> 
> > Will there be an option not to merge?  I never update /etc when
> > I do installworld because what I have works for me and I see no
> > need to make any changes to a working system.  
> 
> And you expect your system to continue working after a new system user is
> added?
> 

Yes, because these are mentioned in UPDATING and I add them by hand.

-- 
Gary Jennejohn
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Jenkins build is still unstable: FreeBSD_HEAD #164

[jenkins-admin]

See 

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Jenkins build is still unstable: FreeBSD_HEAD #163

[jenkins-admin]

See 

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"