On 8/20/2018 7:09 PM, Warner Losh wrote:
On Mon, Aug 20, 2018 at 4:50 PM, Brett
wrote:
Hi Kevin,
Thanks for your help.
Should I be doing "make LOADER_DEFAULT_INTERP=4th buildkernel && make
LOADER_DEFAULT_INTERP=4th installkernel"?
Nope. Kernel has nothing to do with i
Hi Kevin,
Thanks for your help.
Should I be doing "make LOADER_DEFAULT_INTERP=4th buildkernel && make
LOADER_DEFAULT_INTERP=4th installkernel"?
I had also previously tried " make clean all install
WITHOUT_LUA_LOADER=yes" in /usr/src/stand which did not help.
T
is as expected, including /boot/lua/loader.lua.
I re-installed everything in /usr/src/stand (chroot'd on the installer
image, and "cd /usr/src/stand && make clean all install"). This did not
fix the problem.
Does anybody happen to have any ideas?
Thanks,
-Brett
__
Greeting-
So can others duplicate my results, or should I give some kernel dev
access to my console server and my BeagleBone?
-Brett
--
wynk...@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt
917-642-6925
929-272-
Amendment IV
The right of the people to be secure in
. I like to understand the how/why of
things.
I am giving this a try, but it still begs the question that since I
never changed make.conf before and never made any choices about
building or not building kerberos why it broke all of the sudden. What
changed?
I am also going to test Gonzo's s
/usr/src/kerberos5.
*** [includes] Error code 1
Stop in /usr/src/kerberos5.
*** [kerberos5.includes__D] Error code 1
Stop in /usr/src.
*** [_includes] Error code 1
Stop in /usr/src.
*** [buildworld] Error code 1
Stop in /usr/src.
Help!
Thanks!
-Brett
--
wynk...@wynn.com http://prd
On Tue, 1 Jan 2013 10:55:58 -0800
Tim Kientzle wrote:
>
> On Jan 1, 2013, at 8:12 AM, Brett Wynkoop wrote:
> > Greeting-
> >
> > The driver is working much better than the driver currently in
> > head. I have maintained an ssh connection to the BeagleBone for
>
tly in head. I
have maintained an ssh connection to the BeagleBone for more than 24
hours!
Thanks so much Tim!
-Brett
--
wynk...@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt
917-642-6924
718-717-5435
___
freebsd-current@freebsd.o
power I will save!
-Brett
--
wynk...@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt
917-642-6924
718-717-5435
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe
On Sat, 10 Nov 2012 23:34:24 +1100
Peter Jeremy wrote:
> On 2012-Nov-10 09:16:32 +1100, Brett wrote:
> >Just an observation: a few years ago when I got sick of Linux's
> >"headlong rush" development model, I subscribed to various BSD
> >mailing lists to see w
U power saving modes).
I've only briefly used DragonflyBSD but plan to get it cranking again on one of
my machines soon. The release version I tried before seemed pretty solid and
gave good (desktop) performance.
Its interesting to look at the relative strengths a
>>> No offence, but how many times did you break the build? Could you please
>>> compile your code before committing next time? Thanks a lot!
>> Just an observation: a few years ago when I got sick of Linux's "headlong
>> rush" development model, I subscribed >>to various BSD mailing lists to s
> Message: 11
> Date: Fri, 9 Nov 2012 23:34:58 +0800
> From: Doug Brewer
> To: Adrian Chadd
> Cc: a...@freebsd.org, FreeBSD Tinderbox ,
> curr...@freebsd.org
> Subject: Re: [head tinderbox] failure on arm/arm
> Message-ID:
>
> Content-Type: text/plain; charset=ISO-8859-1
>
> No offe
> > those roff sources have been very naughty and will be removed from the
> > tree by the end of the year.
> ...
> > Should people feel strongly about them, we might be able to move them
> > over to the doc repository.
>
> This does not seem a "RFC" -- this sounds more like you or a cabal
> alrea
rrent?
Thanks,
Brett.
___
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"
Will port also be MFCed to 9-RELENG and 9.1-RELEASE? Do not want to
have to go to -CURRENT to get latest OpenSSL.
--Brett Glass
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send
Just tried to build a new kernel in 9.0-BETA3 with the IPFIREWALL
option, and found that the build halts with a compiler error. The
error occurs at netinet/ipfw/ip_fw_pfil.c, line 185, where the
compiler complains that the variable "len" is used before
intialization. Problem occurs on both i386
han
just an LF as in UNIX). If you'd like, I can try to come up to speed on
the code and help to debug, but I do not use X and so have no experience
with its default terminal emulator; I'd have to study that as well.
--Brett Glass
At 06:25 AM 10/7/2011, Ed Schouten wrote:
* Ed Schoute
ry, but the one in 9.0-BETA2 and 9.0-BETA3 does NOT work well with
the "xterm" termcap entry. Many artifacts. You almost can't edit. I
have had to log in via SSH and use vt100 rather than using the console.
--Brett Glass
__
mmer backported from Dragonfly.
--Brett
___
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"
of /usr over to the read-only administrative partition.
The only cleanup task that would remain would be to make sure that
no ports were configured to place their logs, pid files, etc. in
directories such as /usr/local/etc. (Most already do not.)
--Brett
__
it on.
4) The installer still used the old syntax for Internet addresses
in /etc/rc.conf instead of the newer one (e.g. ifconfig_fxp0="inet
192.168.1.1 netmask 255.255.255.0" instead of ipv4_addrs_fxp0="192.168.1.1/24")
For the most part, tho
* To: Cyberpunk <[EMAIL PROTECTED]>
* Subject: Re: its a joke
* From: Bill Fumerola <[EMAIL PROTECTED]>
* Date: Tue, 9 Dec 1997 19:47:26 -0500 (EST)
* cc: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
* In-Reply-To: <[EMAIL PROTECTED]>
* Sender: [EMAIL PROTECTED]
On Tue, 9 De
On Thu, 01 Feb 2001 19:02:36 PST, "Matthew Jacob" wrote:
>
>Isn't it early for april fool's?
Well c'mon, Matt. Given the lack of interesting
content (geez, it wasn't even a Good Spoof), do
you really think the perps are smart enough to
know the difference
Jordan:
I can probably help you out. 612.664.3078.
Brett
On Fri, 01 Dec 2000 12:56:32 PST, "Jordan Hubbard" wrote:
>> Not sure if this the right place to complain or not, but
current.freebsd.org
>> does not appear to be on the net. traceroutes to both
current.f
auth 6df833c4 unsubscribe freebsd-current [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
o get the
support for yet (hence I can't cvsup to 4.0 like most ppl have suggested,
but thanks for the responses anyway!!).
See Ya!
--
Brett White <[EMAIL PROTECTED]>
How many Tux could the Daemon Chuck slay if the Daemon Chuck could slay Tux?
To Unsubscribe: send mail to [EMAIL
Has anyone tried using the 4.0-19991012-CURRENT snapshot? I
need to confirm that this snapshot is a "good one" before I
update my 3.3R installation to it in a last ditch effort to
compile USB modem support into the kernel.
Thanks,
--
Brett White <[EMAIL PROTECTED]>
Duty P
on the FreeBSD machines and then you'll have to
probably add a configure argument like:
--with_kde_includes= /some/dir/where/kde/includes/are
Dig through the knewmail configure script at the top and look for an
option like this.
Brett
****
Hi,
> The latex installed by the teTex port complained about not being able to
> find default settings, or some such.
Did you run texconfig? I'm having no trouble at all on my -current
machine; well I guess it's a -STABLE machine now b
3.0 days) on my home machine and teTeX works fine there.
Brett
******
Brett Taylorbr...@peloton.physics.montana.edu
http://peloton.physics.montana.edu/brett/
"love isn't someplace that we fall, it's somethin
31 matches
Mail list logo
