On Wednesday, October 01, 2014 7:48:08 AM Rainer Hurling wrote:
> Am 01.10.2014 um 05:44 schrieb Chuck Burns:
> > On Tuesday, September 30, 2014 8:13:01 AM O. Hartmann wrote:
> >> Hello.
> >>
> >> I just made the last update of the ports yesterday (I use
port
t -usually- works great, I've noticed that
occassionally it loops like that.
kill the script, upgrade the port that is looping.
That usually fixes it.
--
Chuck Burns
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman
On Wednesday, November 27, 2013 11:21:58 AM Andriy Gapon wrote:
> When building ports on head I sometimes see messages like the
following
> during a patch phase:
>
> ===> Applying FreeBSD patches for firefox-25.0_1,1
> No such line 262 in input file, ignoring
> ===> Applying NSS patches
> No su
On 12/7/2012 9:10 PM, Warren Block wrote:
On Fri, 7 Dec 2012, Chuck Burns wrote:
dd if=/dev/zer of=/dev/ada0
^^^ There's your "badblocks" program. Any hard drive made in the last
decade have been self-remapping..
That should be /dev/zero. And this will be very slow, goi
"losing" storage space... IE the
number of total sectors on the drive will begin to shrink.
--
Chuck Burns
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
fine,
just that other OS may not probe/use/access it in exactly the same manner.
--
Chuck Burns
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freeb
-bootstrapped with no need to compile
anything. -but- If you want to use -stable or -current, then you really
should use ports as well...
--
Chuck Burns
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To
On 11/20/2012 11:51 AM, Eitan Adler wrote:
On 20 November 2012 12:47, Chuck Burns wrote:
Nonsense. More options are always preferable to fewer options.
Even when those options must be maintained? Documented? Bug fixed?
The ones who want the old pf can maintain it.. those who want the new
On 11/20/2012 10:52 AM, Aldis Berjoza wrote:
20.11.2012, 18:34, "Chuck Burns" :
On 11/20/2012 10:27 AM, O. Hartmann wrote:
On 11/20/12 11:43, Olivier Smedts wrote:
2012/11/20 Paul Webster :
I am aware this is a much discussed subject since the upgrade of PF, I
believe
want the old one can use it.
Or, another option is a knob USE_NEWPF during buildworld will build the
new pf, otherwise it'd build the old, default one.
This way you can still introduce the change, but default to the old one
for those of us who are too crusty to change. :)
--
C
rcoaster goes up and down* No worries. :)
--
Chuck Burns
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
o "freebsd-current-unsubscr...@freebsd.org"
Quite honestly, the head/current branch is going to have build
failures.. It's the test bed.. Stick with the release system unless you
want cutting edge.. just remember.. cutting edge cuts sometimes...
--
Chuck Burns
_
e a smaller i386 box... 100G or so
free, 512M ram.. just drop me a line..
--
Chuck Burns
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Just remember, if you can't laugh at yourself for dumb misakes, there
will always be som
lans to eventually write a devd SOLID
backend, but they are extremely busy, so any help in that would be most
welcome.. avilla@ can probably elaborate on that.. cross-posting my
reply to the kde@ ML so they can chime in if need be.
--
Chuck Burns
___
still works as it
should... In the meantime, someone should probably write a
devd<->udisks[12] translation daemon.. for things like gnome, kde, xfce,
and virtualbox, which have the udisks linuxisms can actually continue to
work in the future..
I'd do it if I
terest to userland
code
even for such a utility as lsof.
Honestly, if you do not like the way lsof does things, I'm sure patches
are welcome..
--
Chuck Burns
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/fre
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Known issue. KMS prevents console switching, still. KMS is not quite
ready for use, but works fine as long as you stay in Xorg
--
Chuck Burns
___
freebsd-current@f
in recent xorg-server, even for
running without an xorg.conf file. This was not the case for a while,
but with recent xorg-server, hal is NOT NEEDED even for autodetection.
It has been deprecated by the linux folks for a few years now.
--
Chuck Burns
___
be running
FreeBSD on older equipment where polling might still make sense.
Do we throw them under the bus?
--
Chuck Burns
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
fix ports so that one can compile 32bit ports on
FreeBSD amd64. If that's not what you meant, then ok.. but it's still a
good idea for a task. :P
--
Chuck Burns
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mail
ghost.
Then give it some love yourself! No one is
stopping you! :)
--
Chuck Burns
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-curren
ests that fail when libm is compiled using clang.
> I've not investigate those at all. I'd tend to guess that we have a
> wider range of issues there.
>
> This is clearly an area we need more focus on before a switch to clang.
> To a point I would be OK with it delaying the switch to work these
> issues, but as with C99 long double support we can't let the quest for
> perfection delay us indefinitely.
>
> -- Brooks
Also, you probably want to be sure you are running these tests against clang
3.2, not the clang that is in base, since -that- is the version that will be
going live, right?
--
Chuck Burns
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
clang, crash!
http://code.google.com/p/gperftools/issues/detail?id=394
--
Chuck Burns
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
ly trolled.. right?
*shakes head and walks away*
Chuck Burns
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
On 5/12/2012 4:39 PM, Konstantin Belousov wrote:
>
> My own preference is to implement second choice and put the driver
> into dev/drm2.
Is there a way to have an OPTION in the config file build one driver,
and without the OPTION to build the other, but use the same name? If so,
that might be t
On 4/2/2012 10:52 AM, Chris Rees wrote:
This is a known issue with ZFS. Is that your case?
Chris
Yes. Interesting that it happens only with ZFS.
and jb, thanks, I could've sworn I'd hit "Reply to list" - thanks for
forwarding it for me.
Chuck
On 3/25/2012 9:35 PM, Super Bisquit wrote:
I'm a retired 69 year old pregnant male looking for part-time work
during my career break.
I'm not a pregnant male, I just look like it
ouch. :(
Chuck
___
freebsd-current@freebsd.org mailing lis
.1 for .0 versions.
The reason for the padding is to help with sorting, at least until
freebsd 100.0 comes out. :P
Chuck Burns
On 3/20/2012 5:40 AM, Alexander Yerenkow wrote:
IMHO,
32 / 64 = easily parsable and represent integer.
i386/amd64 - wellknown names, but this info about processor bit
On 2/28/2012 4:55 PM, Ade Lovett wrote:
On 2/28/2012 14:11, Alexander Best wrote:
any chance we can have a CFLAGS.gcc and CFLAGS.clang in the future?
that would
make certain things a lot easier. dealing with gcc specific options,
such as
-mpreferred-stack-boundary=2 would simply work by setting
g at straws on the fix you want, but the
error message is pretty clear.. and without the _after line I'm betting
it would boot fine.
--
Chuck Burns
The Southern Libertarian (owner/editor)
http://www.thesouthernlibertarian.com/
___
freebsd-current@fr
y, it would just be
too disruptive otherwise.
My $0.02
Instead of using -F to denote filetypes, why not use colors? -G -- it
shouldnt affect scripts at all, yet still provide the same sort of
feedback. (Tho, I personally use csh's built-in "ls-F" instead of "ls",
and actua
of kernel
OR
(b) new mpd 5.6 (previous version had 5.5).
P.S. Adding net@ and mav@ to CC, original posting with all data is in
current@
If it were me, I would also try with the older 44BSD scheduler, just to
see what happens.
--
Chuck Burns
The Southern Libert
.h:90:2: note: array 'name' declared here
__uint8_t name[1]; /* name bytes, no null */
^
1 warning generated.
just as an aside, the XFS module didn't seem to work when I last
attempted to use it, so it may be worth just removing it?
--
Chuck Burns
The Souther
On Saturday, December 10, 2011 7:35:27 AM Chuck Burns wrote:
> Here is quick, hackish patch to allow your make update to work, it appears
> that the Makefile.inc1 does not include the full path to svn, while it does
> include the full path to cvs and other tools, this makes me think
ars
that the Makefile.inc1 does not include the full path to svn, while it does
include the full path to cvs and other tools, this makes me think that the
user path is ignored (which is a good thing)
--
Chuck Burns
The Southern Libertarian
http://www.thesouthernlibertarian.com/
Ind
I recently source-up'd to 10-current, and began the slow process of rebuilding
all my installed ports, devel/google-perftools fails with an undeclared
"__isthreaded"
The following should be more than enough information.
Thanks,
Chuck Burns
root@freebeast /usr/src
nd GhostBSD uses the gnome 2.32 environment.
If you want something else, feel free to create your own. There is nothing in
the BSD license that prevents you from doing that.
Instead of complaining that SOMEONE ELSE should do something that YOU want
done, why not just do it your
st be built from source, and SHOULD always point to the latest source
code.
If you are using pkg_add -r to install software, on anything but
release versions, you should expect breakage.
If you do not wish to build from source, then you should p
On Tuesday, November 08, 2011 02:12:58 PM Niclas Zeising wrote:
> From my understanding of things, the DEFAULTS kernel configuration file
> is automatically included into the build by config(8). There is no need
> to include it into the generic using the "include" statement. It was
> first added 6
g as "-1"
Also, I am running zfs root, if that makes a difference
--
Chuck Burns
"We have the right as individuals to give away as much of our own money as we
please in charity; but as members of Congress we have no right to appropriate
a dollar of the
no longer technically, current, but
since it isn't released yet, I figure it's close enough)
--
Chuck Burns
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail
42 matches
Mail list logo
