Cheers,
-R. Tyler Ballance
--
Jabber: rty...@jabber.org
GitHub: http://github.com/rtyler
Twitter: http://twitter.com/agentdero
Blog: http://unethicalblogger.com
pgpkfqopLBnxf.pgp
Description: PGP signature
the Debian GNU/kFreeBSD guys:
http://www.debian.org/ports/kfreebsd-gnu/
I bet they've got a good idea :)
Cheers,
-R. Tyler Ballance
--
Jabber: rty...@jabber.org
GitHub: http://github.com/rtyler
Twitter: http://twitter.com/agentdero
Blog: http
use tags in
bugzilla or $OTHER_ISSUE_TRACKER to denote that a task has is suitable for
tenderfoots.
I thought the PR database had tags, so perhaps it just needs some folks
spending some time tagging PRs?
Cheers,
-R. Tyler Ballance
--
Jabber: rty...@jabber.org
On Fri, 22 Jan 2010, Giorgos Keramidas wrote:
On Sun, 17 Jan 2010 13:30:50 -0800, R. Tyler Ballance ty...@monkeypox.org
wrote:
Are there similar resources I've not stumbled across yet? I would like to
help,
I have but one machine running -CURRENT and sporadic free time over
=ASSIGNEDbug_status=REOPENEDcmdtype=doit
Are there similar resources I've not stumbled across yet? I would like to help,
I have but one machine running -CURRENT and sporadic free time over the
weekends.
Tips? :D
Cheers,
-R. Tyler Ballance
--
Jabber: rty...@jabber.org
to the experimental ZFS support on FreeBSD and jails.
It'd be nice to meet with any hackers in the area that were also too
poor to make it out to AsiaBSDCon ;)
Cheers
R. Tyler Ballance: Lead Mac Developer at bleep. software
contact: [EMAIL PROTECTED] | jabber: [EMAIL PROTECTED
right, that trace is about as informative as new printer paper :)
Cheers
R. Tyler Ballance: Lead Mac Developer at bleep. software
contact: [EMAIL PROTECTED] | jabber: [EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http
;)
Cheers
R. Tyler Ballance: Lead Mac Developer at bleep. software
contact: [EMAIL PROTECTED] | jabber: [EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail
. Tyler Ballance
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (Darwin)
iD8DBQFE7PdOqO6nEJfroRsRAuCeAJ9q3bgjYZK7FXGUTw0oPQNNUXibUACdGdfs
nxRXAwqSksQy9r8ASEmH7fw=
=HBFg
-END PGP SIGNATURE-
___
freebsd-hackers@freebsd.org mailing list
http
track down exactly where this error is
occurring, I'm including a new version of the error transcript in
case it's helpful at all. Any porters seen this before, kmacy? arm
guys? anybody? :P
Cheers,
- -R. Tyler Ballance
===
cc -O2 -fno-strict-aliasing -pipe -I. -DIN_GCC
environment while using a toolset appropriate for
building CURRENT? (Does it even matter really?)
Cheers,
- -R. Tyler Ballance
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (Darwin)
iD8DBQFEw1TuqO6nEJfroRsRArxCAJ44DICg+wi65O6ymBh6BNYY8bE1tACdEPTn
Tpb8/URR87blmlVDrxQV95M=
=SZau
-END PGP
/
iguana
*** Error code 2
The problem I'm having is that I just want to build the kernel
specific to the new platform but will I necessarily have to provide
the proper constructs for the build system to cope with the new
platform in src/sys/ ?
Cheers,
- -R. Tyler Ballance
-BEGIN
to doing non-standard
builds of the kernel (non-standard being not in /usr/src and not the
host arch)
Currently the make command I'm using, which doesn't work, is (/usr/
obj is chmod'd 777):
make TARGET_ARCH=iguana DESTDIR=/home/tyler/iguana buildkernel
Any suggestions?
Cheers,
-R. Tyler
I'm just wondering, the machine-dependent assembly tied into the i386
kernel, that's all named ${FILENAME}., while in the arm/ kernel
machine-dependent code is named ${FILENAME}.S, what's the difference?
Or is there none, just a change in convention?
Cheers,
-R. Tyler Ballance
that would be
good to add, C C++ cover most of what the rest of the world writes
their lower level code in.
Cheers,
- -R. Tyler Ballance
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (Darwin)
iD8DBQFEwN/kqO6nEJfroRsRAjyvAJ9BCvK9jC/GEWfjxFdZBbMK7UQiSgCfYRd7
VF1l80jl6vZhhJqc9dr2l3w
in which functions are called right after the
bootloader finishes it business?
Cheers,
- -R. Tyler Ballance
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (Darwin)
iD8DBQFEdAW/qO6nEJfroRsRAgMUAJ93K5wwRRXljCkgx8SaU0fdgN3l3gCgkuqA
S/BC67a7O1KuQzvnsvZUAvc=
=PQtC
-END PGP SIGNATURE
:))
Cheers,
-R. Tyler Ballance
p.s. I'm not a kernel hacker, but I do aspire to be one eventually,
just so I can stop arguing about the color of the bikeshed :)
PGP.sig
Description: This is a digitally signed message part
:
Permission denied
%
% echo $CVSROOT
[EMAIL PROTECTED]:/home/ncvs
%
Keep in mind, anoncvs1.freebsd.org works perfectly fine.
Ho hum, guess we only get one working USA mirror ;)
Cheers,
-R. Tyler Ballance
___
freebsd-hackers@freebsd.org mailing list
http
If you run out of ideas, or are looking for something else, try
looking at some of the SoC projects that weren't chosen/accepted/etc.
http://www.freebsd.org/projects/summerofcode.html
Im sure you could expand one of these to cover a final CS project.
Cheers,
-R. Tyler Ballance
On Sep 7
() calls launch_client_init() on line 119.
Nothing from within launch_client_init() gets output to the terminal,
while the printfs in launch_msg() before and after the
launch_client_init() call are both output
Any tips? :/
Cheers,
-R. Tyler Ballance
Sorry everybody for the extra crap in your inboxes; I was forgetting
to add -lpthread to the LDFLAGS in the Makefile for the launchctl
client
Shouldn't gcc warn me against this? Oh well, false alarm, thanks reffie!
Cheers,
-R. Tyler Ballance
On Aug 20, 2005, at 3:23 AM, R. Tyler
as well?
Other than that, do you know if the new OPENBSD_3_7 pf code will work
with this patch?
Thanks a lot for working on it! :)
-R. Tyler Ballance
On May 30, 2005, at 6:25 PM, Andrew Thompson wrote:
Hi,
I am looking for testers and code review for if_bridge, the bridge
implementation from
22 matches
Mail list logo
