Re: Building FreeBSD on a linux FC11 box.
On Sat, 20 Feb 2010, Patrick Mahan wrote:
>
> Hopefully, this is not too ignorant a question. But has anyone every
> built the FreeBSD sources, both kernel and apps, on a linux platform?
>
> I did a google on 'cross-compile freebsd (linux)' and found (mostly)
> discussions regarding building the linux apps for FreeBSD, but not
> for building a FreeBSD kernel and world. There was a brief discussion
> on the mailing list back in 2005, but the poster never reported if
> he had success or failure. Also, there were discussions about building
> freebsd amd64 on a freebsd i386.
>
> I have done lots of development in linux using cross-compilers (mips
> embedded systems, powerpc, etc). But not with FreeBSD.
>
> I know I'll need to use 'bsdmake' no gnu 'make'. The other worry is
> kernel-toolchain target. I guess I'll just dive in and swim around
> and see what happens.
You might want to ask 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://unethicalblogger.com
pgpub3D3K0Wny.pgp
Description: PGP signature
Re: ntpd hangs under FBSD 8
On Fri, 19 Feb 2010, Peter Steele wrote: > I posted this originally on the -questions list but did not make any headway. > We have an application where the user can change the date/time via a GUI. One > of the options the user has is to specify that the time is to be synced using > ntp. Our coding worked fine under BSD 7 but since we've moved to BSD 8 we've > encountered a problem where the command that we initiate from the GUI: Just out of curiosity, can you attach to the process via gdb and get a backtrace? This smells like a locked pthread_join I hit in my own code a few weeks ago 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
Re: junior tasks wiki page - please add stuff
On Fri, 19 Feb 2010, jhell wrote: > It would be awesome if for some way the PR database could be tied into > this so items in the database could be promoted as junior tasks. Adding > to that, an option in the PR web for someone to be able to vote on certain > PR's that should be promoted and ultimately giving a little more free time > to the PR admin by not having to visually inspect every PR that has not > been categorized for its worth as a junior project, and putting the > community as a whole to work in the voting. Agreed, other projects I've seen that do something along this lines 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 GitHub: http://github.com/rtyler Twitter: http://twitter.com/agentdero Blog: http://unethicalblogger.com pgpcXgCjERJev.pgp Description: PGP signature
Re: Weekend PR smashing
On Fri, 22 Jan 2010, Giorgos Keramidas wrote: > On Sun, 17 Jan 2010 13:30:50 -0800, "R. Tyler Ballance" > 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 the > > weekends. > > Hi there. I just noticed this post in among others in -hackers. If you > don't know about the bugbuster team already, you should check it out. > There's a mailing list at freebsd-bugbusters and an IRC channel at the > EFnet network. Righteo, I stumbled across that shortly after my email to the list, I've been lurking in there since (rtyler). > > Since you are looking for pointers to get you started, the following may > help a bit: > > http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ > http://www.freebsd.org/doc/en_US.ISO8859-1/articles/pr-guidelines/ > http://www.freebsd.org/doc/en_US.ISO8859-1/articles/problem-reports/ > > Finally, it's worth noting that it is not a huge problem if you only have > weekend-time to contribute. We welcome all the help we can get, so please > feel free to jump in and help in any way you can with the existing bugs (or > new ones that you have noticed). I certainly get that impression, one of the things that concerns me is the sheer number of PRs with patches that either have been committed without the PRs being updated, or the patches are simply sitting idly in PRs. The list by the bugbusters waiting for committers to check them out is pretty huge as well: http://people.freebsd.org/~linimon/studies/prs/recommended_prs.html http://people.freebsd.org/~linimon/studies/prs/prs_for_tag_patch.html It's a little difficult to muster up too much motivation to fix issues when the fixes will then sit waiting for committer review for months on end. Without annoying committers, is there any way I can help get patches "through" and into the tree in less than a lunar cycle? ;) Cheers, -R. Tyler Ballance -- Jabber: rty...@jabber.org GitHub: http://github.com/rtyler Twitter: http://twitter.com/agentdero Blog: http://unethicalblogger.com pgpAXeZvmgpyz.pgp Description: PGP signature
Weekend PR smashing
Howdy all, I've recently taken up perusing the PR database looking for small(ish) bugs that will help me: (1) start contributing to FreeBSD again (2) familiarize myself with -CURRENT. Last weekend I knocked off #43337 (to which my patch still remains unaddressed) and started looking for more and more bugs, particularly in the 'bin' category. I've noticed a couple things, and would love a helping hand with: * There's a lot of **old** PRs, some of the userland bugs that are over a decade old I have no idea what to do with (try to reproduce a bug filed against 2.2?) * There's a lot of PRs with patches and a discussion; I don't *think* I can do anything helpful with these Additionally, I feel somewhat overwhelmed, I'm really hunting for tasks anywhere from a few hours to an all-nighter. Some of the things the KDE team does to get people involved I find useful, such as the "bugs howto" for information on triaging and getting started with contributing: http://quality.kde.org/develop/howto/howtobugs.php As well as the "junior jobs" keyword in their bugzilla: https://bugs.kde.org/buglist.cgi?keywords=junior-jobs&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=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 GitHub: http://github.com/rtyler Twitter: http://twitter.com/agentdero Blog: http://unethicalblogger.com pgpE7fenfBmzv.pgp Description: PGP signature
FreeBSD at SXSW
I just thought that I'd throw this out there, I've run into some folks running FreeBSD on various systems here at SXSW in Austin, and would certainly like to coordinate a meetup with any users or hackers as there's some folks here touting OpenSolaris' ZFS, and containers in contrast 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] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Kernel hang on 6.x
On Dec 14, 2006, at 1:05 PM, Brian Dean wrote: Hi, We're experiencing a kernel hang on a 6.x quad processor Sun amd64 based system. We are able to reproduce it fairly reliably, but the environment to do so is not easily replicatable so I cannot provide a simple test case. However, I have been able to build a debug kernel and when the system "hangs", I can break to the debugger prompt. But once there, I'm not sure what to do to isolate where the system is hung up. I have confirmed that the hang occurs in both SMP and uniprocessor mode. Here are some system details: I think you'll need to ship this machine to my house for further umerm, diagnostics, yes, that's it ;) On a more serious topic, can you paste the output from: ddb> show pcpu ddb>allpcpu ddb>traceall ddb>show alllocks ddb>show lockedvnods Just curious as to whether those would show more info, because you're 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://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
natd(8) and NAT-PMP
My internal development network here uses a FreeBSD RELENG_6 machine to act as a NAT gateway for testing of NAT traversal software, am I'm certain that natd(8) supports uPnP, but does it support NAT-PMP? I don't want to have to purchase an Airport base station, as that's the only NAT box I am aware of that supports NAT-PMP to test some code for opening up the port mappings as specified by NAT-PMP's ietf draft. In the case that natd(8) does not support NAT-PMP, has anybody started work on it? Or am I "more than welcome to" start working on a set of patches to add support ;) 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 to "[EMAIL PROTECTED]"
Forcing the kernel-toolchain to jive with my new "port"
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've finally found time to work on my L4::BSD project again, and I'm getting back into the building of the kernel and it's various "friends" alongside it for the new "port" (iguana, which is the minimalistic L4 based OS that will help bridge the kernel subsystems to the appropriate facilities atop L4) and I'm getting the following error when I run: %make TARGET_ARCH=iguana kernel-toolchain cc -O2 -fno-strict-aliasing -pipe -I. -DIN_GCC -DHAVE_CONFIG_H - DPREFIX=\"/usr\" -DCROSS_COMPILE -I/usr/home/tyler/build/obj/iguana/ usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/cc_tools/../ cc_tools -I/usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ cc_tools/../cc_tools -I/usr/home/tyler/perforce/projects/l4bsd/src/ gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc -I/usr/home/tyler/ perforce/projects/l4bsd/src/gnu/usr.bin/cc/cc_tools/../../../../ contrib/gcc/config -DGENERATOR_FILE -I/home/tyler/build/obj/iguana/ usr/home/tyler/perforce/projects/l4bsd/src/tmp/legacy/usr/include -c / usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ cc_tools/../../../../contrib/gcc/genattr.c In file included from /usr/home/tyler/perforce/projects/l4bsd/src/gnu/ usr.bin/cc/cc_tools/../../../../contrib/gcc/genattr.c:27: ./tm.h:4:15: /.h: No such file or directory ./tm.h:10:22: /freebsd.h: No such file or directory In file included from /usr/home/tyler/perforce/projects/l4bsd/src/gnu/ usr.bin/cc/cc_tools/../../../../contrib/gcc/genattr.c:28: /usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ cc_tools/../../../../contrib/gcc/rtl.h:2189: warning: parameter has incomplete type /usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ cc_tools/../../../../contrib/gcc/rtl.h:2189: warning: parameter has incomplete type /usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ cc_tools/../../../../contrib/gcc/rtl.h:2190: warning: parameter has incomplete type /usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ cc_tools/../../../../contrib/gcc/rtl.h:2190: warning: parameter has incomplete type /usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ cc_tools/../../../../contrib/gcc/rtl.h:2209: warning: parameter has incomplete type *** Error code 1 Stop in /usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ cc_tools. *** Error code 1 - --[ snip ]-- I'm wondering, since the kernel would technically be x86-Iguana, would a suitable work around for this be to do the following: % make TARGET_ARCH=i386 kernel-toolchain and then follow that with: % make TARGET_ARCH=iguana buildkernel The toolchain and the accompanying shims to build the kernel from my understanding would be suitable to just build under the stock i386 "convention" and then build the specific iguana kernel once the appropriate toolchain and shims have been built? Please let me know if I'm heading down the wrong rabbit hole here :) Cheers, - -R. Tyler Ballance -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (Darwin) iD8DBQFE7PdOqO6nEJfroRsRAuCeAJ9q3bgjYZK7FXGUTw0oPQNNUXibUACdGdfs nxRXAwqSksQy9r8ASEmH7fw= =HBFg -END PGP SIGNATURE- ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Failing `make buildworld` with today's source
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 freebsd-current: I figured out why this was failing on my machine, I did a clean `make buildworld` which succeeded without a hitch freebsd-hackers: After taking Warner's advice, I am building world with a different target arch, but I cannot 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 -DHAVE_CONFIG_H - DPREFIX=\"/usr\" -DCROSS_COMPILE -I/usr/home/tyler/builds/obj/iguana/ usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/cc_tools/../ cc_tools -I/usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ cc_tools/../cc_tools -I/usr/home/tyler/perforce/projects/l4bsd/src/ gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc -I/usr/home/tyler/ perforce/projects/l4bsd/src/gnu/usr.bin/cc/cc_tools/../../../../ contrib/gcc/config -DGENERATOR_FILE -I/home/tyler/builds/obj/iguana/ usr/home/tyler/perforce/projects/l4bsd/src/tmp/legacy/usr/include -c / usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ cc_tools/../../../../contrib/gcc/gengenrtl.c cc -O2 -fno-strict-aliasing -pipe -I. -DIN_GCC -DHAVE_CONFIG_H - DPREFIX=\"/usr\" -DCROSS_COMPILE -I/usr/home/tyler/builds/obj/iguana/ usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/cc_tools/../ cc_tools -I/usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ cc_tools/../cc_tools -I/usr/home/tyler/perforce/projects/l4bsd/src/ gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc -I/usr/home/tyler/ perforce/projects/l4bsd/src/gnu/usr.bin/cc/cc_tools/../../../../ contrib/gcc/config -DGENERATOR_FILE -I/home/tyler/builds/obj/iguana/ usr/home/tyler/perforce/projects/l4bsd/src/tmp/legacy/usr/include -L/ home/tyler/builds/obj/iguana/usr/home/tyler/perforce/projects/l4bsd/ src/tmp/legacy/usr/lib -o gengenrtl gengenrtl.o errors.o libiberty.a ./gengenrtl > genrtl.c ./gengenrtl -h > genrtl.h cc -O2 -fno-strict-aliasing -pipe -I. -DIN_GCC -DHAVE_CONFIG_H - DPREFIX=\"/usr\" -DCROSS_COMPILE -I/usr/home/tyler/builds/obj/iguana/ usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/cc_tools/../ cc_tools -I/usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ cc_tools/../cc_tools -I/usr/home/tyler/perforce/projects/l4bsd/src/ gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc -I/usr/home/tyler/ perforce/projects/l4bsd/src/gnu/usr.bin/cc/cc_tools/../../../../ contrib/gcc/config -DGENERATOR_FILE -I/home/tyler/builds/obj/iguana/ usr/home/tyler/perforce/projects/l4bsd/src/tmp/legacy/usr/include -c / usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ cc_tools/../../../../contrib/gcc/genattr.c In file included from /usr/home/tyler/perforce/projects/l4bsd/src/gnu/ usr.bin/cc/cc_tools/../../../../contrib/gcc/genattr.c:27: ./tm.h:4:15: /.h: No such file or directory ./tm.h:10:22: /freebsd.h: No such file or directory In file included from /usr/home/tyler/perforce/projects/l4bsd/src/gnu/ usr.bin/cc/cc_tools/../../../../contrib/gcc/genattr.c:28: /usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ cc_tools/../../../../contrib/gcc/rtl.h:2189: warning: parameter has incomplete type /usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ cc_tools/../../../../contrib/gcc/rtl.h:2189: warning: parameter has incomplete type /usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ cc_tools/../../../../contrib/gcc/rtl.h:2190: warning: parameter has incomplete type /usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ cc_tools/../../../../contrib/gcc/rtl.h:2190: warning: parameter has incomplete type /usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ cc_tools/../../../../contrib/gcc/rtl.h:2209: warning: parameter has incomplete type *** Error code 1 Stop in /usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ cc_tools. *** Error code 1 Stop in /usr/home/tyler/perforce/projects/l4bsd/src. *** Error code 1 Stop in /usr/home/tyler/perforce/projects/l4bsd/src. *** Error code 1 Stop in /usr/home/tyler/perforce/projects/l4bsd/src. % ======= On Jul 24, 2006, at 12:31 AM, R. Tyler Ballance wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I recently integrated today's (ok, sunday's) source code into my branch in perforce, and I'm getting these build errors: Anybody seen anything similar? ./gengenrtl > genrtl.c ./gengenrtl -h > genrtl.h cc -O2 -fno-strict-aliasing -pipe -I. -DIN_GCC -DHAVE_CONFIG_H - DPREFIX=\"/usr\" -DCROSS_COMPILE -I/usr/home/tyler/builds/obj/ iguana/usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ cc_tools/../cc_tools -I/usr/home/tyler/perforce/projects/l4bsd/src/ gnu/usr.bin/cc/cc_tools/../cc_tools -I/usr/home/tyler/perforce/ projects/l4bsd/src/gnu
Platform dependent locations (was Re: Building a sandboxed kernel)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Doesn't matter. I often do the following: setenv TARGET arm # this may be iguana for you setenv TARGET_ARCH arm setenv MAKEOBJDIRPREFIX /home/imp/obj cd p4/imp_arm make buildworld make buildenv # from here on out is in a subshell cd ../arm/src/sys/arm/conf config KB920X cd ../compile/KB920X make depend && make You'll notice that I built in a tree that had all the arm patches applied, and got a 'buildenv' there, but then build the kernel out of a different tree. This is a -current p4 tree for both imp_arm and arm, but I do this on a RELENG_6 system. I've done it in the recent past on a 5.3 system too. TARGET is MACHINE and TARGET_ARCH is MACHINE_ARCH. MACHINE is the kernel architecture, while MACHINE_ARCH is the CPU architecture (TARGET_CPU is the specific CPU that we're optimizing for). Chances are excellent we'll have TARGET_ARCH armel and armeb shortly. Right now we have a hack ARM_BIG_ENDIAN used to control big vs little endian, but since MACHINE_ARCH gets encoded into packages, I think we need to move it there so binary packages do the right thing. But that's a WIP in my tree right now... Thanks a lot! Of course, this leads to more questions on my part. Firstly, is there an already outlined guide for porting to new platforms? (Which is essentially what i'm doing for this project: http://opensource.bleepsoft.com/index.php/Main/L4BSD ) Or is this something I'll get to stumble over through trial and error with 'make buildworld; ? I'm finding all sorts of extra places where the FreeBSD build system is expecting platform specific files for example: ===> sys/boot/iguana (cleandir) cd: can't cd to /usr/home/tyler/perforce/projects/l4bsd/src/sys/boot/ 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 PGP SIGNATURE- Version: GnuPG v1.4.3 (Darwin) iD8DBQFEw+TZqO6nEJfroRsRAsWnAJ9xQlqy/DuBmR7Mhyvt4CBKQike4gCfdqzu 7OkESbLqY3i8VkzdleQ5tiU= =8zez -END PGP SIGNATURE- ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Building a sandboxed kernel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Between varying versions of userland tools (like config(8)) and path troubles, I'm wondering what tips anybody has 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? You don't have to use /usr/obj for all your builds: % mkdir -p /home/tyler/obj/iguana % env MAKEOBJDIRPREFIX=/home/tyler/obj/iguana \ make TARGET_ARCH=iguana \ DESTDIR=/home/tyler/iguana \ buildkernel The trick here is to use MAKEOBJDIRPREFIX to change the default object directory prefix from `/usr/obj' to whatever suits your own setup. This doesn't solve the problem of different versions of userland tools required. For example, my machne is RELENG_6, but I'm developing against the -CURRENT branch of code synced up in perforce. Does one necessarily need a -CURRENT userland to develop with the - CURRENT code base? All arguments of being able to test the code that is built are moot since the testing of my code will all occur within a virtualized (Qemu) machine environment. I'm sure the difference in versions between RELENG_6 and CURRENT aren't too great, but what about developing with CURRENT code on RELENG_5? I guess the basic question is, how can I maintain my normal workstation 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 SIGNATURE- ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Machine-dependent code extension?
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
PGP.sig
Description: This is a digitally signed message part
Building a sandboxed kernel
I'm working on a project that relies on me building kernels outside of the standard /usr/src (typically ~/perforce/projects/ ) on my relatively standard 6.1-STABLE workstation. I'm wondering if I'd be best suited by setting up a jail for kernel builds, I'm following this doc: http://people.freebsd.org/~cognet/freebsd_arm.txt loosely because I've created a new "arch folder" in src/sys for the kernel code that I want to build (right now it's unmodified i386 code) Between varying versions of userland tools (like config(8)) and path troubles, I'm wondering what tips anybody has 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 Ballance PGP.sig Description: This is a digitally signed message part
Re: kern/99979: Get Ready for Kernel Module in C++
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Jul 20, 2006, at 1:04 AM, <[EMAIL PROTECTED]> [EMAIL PROTECTED]> wrote: FWIW; I went on to check that Embedded C++ that David Nugent mentioned, and I found this: http://www.caravan.net/ec2plus/ Acording to the Q&A section: "The goal of EC++ is to provide embedded systems programmers with a subset of C++ that is easy for the average C programmer to understand and use. The subset should offer upward compatibility with ISO/ANSI Standard C++ and retain the major advantages of C++. To achieve the goal, several guidelines were established for creating the subset such as avoiding excessive memory consumption (overhead) and removing complex features." ... And also FWIW, I wouldn't object to having support for other languages (Objective C ? ), if someone has/finds modules that could use the features. I've been keeping track on this discussion, and I guess I'll toss my 2 cents in here. Objective-C, while a wonderful smalltalk-ish language (I use it daily), is definitely not nearly as suitable as C+ + for kernel modules, or embedded programming for that matter. The Core Audio framework on Mac OS X is mostly C++ for performance reasons, for example. Objective-C's reliance on message passing is probably as suitable for kernel modules as C# via Mono is, the runtime is a bit too bloated IMHO and because of the inherent design the two languages they just aren't suited (again IMHO) for real time work, or performance dependent functionality. Of course, if anybody has any links to anything performance intensive (audio code is the best example in my book) using either C# or ObjC then I will both be shocked and sickened ;) I really can't think of support for any other languages 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= =XnRr -END PGP SIGNATURE- ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Kernel call stack for dummies.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've started the uphill battle to port FreeBSD's kernel to run "paravirtualized" (<--note the smart sounding vocabulary) on top of the L4/Iguana OS (Iguana is a very barebones OS developed by NICTA: http://www.ertos.nicta.com.au/software/kenge/iguana-project/latest/) On of the first steps is basically porting the lowest of low kernel calls such as those in sys/i386 sys/arm and sys/amd64 for example into sys/iguana to talk to iguana instead of actual hardware. One of the things I need to figure out is the order in which kernel calls are made on boot, so I can go through and reimplement them one by one (in order to spend as little time as possible going back and fixing other problems of mine), as suggested by Ben Leslie at NICTA. Is there a good overview of what's happening directly after boot in terms of the procedure 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- ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Xnu, and 'L4BSD'
All this recent microkernel talk has finally hit another mailing list i'm on ([EMAIL PROTECTED]) regarding a possible "L4BSD" (https:// lists.ira.uni-karlsruhe.de/pipermail/l4ka/2006-May/001603.html) and this has brought up an interesting question for me. L4Linux exists, but it seems to be more of a means for testing out and developing the L4 microkernel, but would there be any practical reason to sandbox the FreeBSD kernel and force it to run as a user- land service on top of the L4::Pistachio kernel? (for example) Would this be an effective place to start in terms of pulling off an in-between kernel much like Darwin's Xnu kernel? I can forsee plausible long term goals that would make such a project worthwhile, such as eventually moving device drivers out of the kernel (FreeBSD's that is) along with other bits and pieces, and eventually morphing it into some middle-ground best-of-both worlds kernel, but if you remove the eventually move into a Xnu-like setup, is there a definite benefit that can be reaped from such a project? Does such a project contain any merit besides the obvious education aspect of it? (And the incessant need to kill time :)) 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
anoncvs.freebsd.org broken?
I was trying to get the most recent RELENG_6 code from one of the AnonCVS servers here in America, so I was using the USA mirrors, and they don't seem to be properly configured anymore... %sudo cvs co -rRELENG_6 -P src cvs [checkout aborted]: cannot write /home/ncvs/CVSROOT/val-tags: 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://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Project in FreeBSD.
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, 2005, at 7:09 AM, Pranav Peshwe wrote: Hello, I am a final year CS student and wish to do a project in the FBSD kernel or networking domains. I am a part of a project group of four and we have the project as a part of syllabus for the final year. Ideas we could think of were : 1) Dynamically Configurable IO schedulers and scheduling policy. - similar to the project mentioned on the SOC page for FBSD. 2) Creating a program which would save the state of the kernel at some instant.Then if the kernel panics,the saved state will be restored. Especially useful for kernel level development which can cause frequent panics. Could anybody please comment on the above ideas. I do not know whether they are already implemented and included in the mainline distro. We would also like to hear about any other ideas related to FBSD. We would be very happy to contribute our bit to the development of FBSD. TIA. Sincere regards, Pranav.J.Peshwe ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers- [EMAIL PROTECTED]" ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pthread functions swallowing stdout, and stderr?
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 Ballance wrote: Howdy, I'm working on my SoC project, where one of the important, yet broken, functions is being called from pthread_once() I have printf()'s before the pthread_once() call to help me debug, and printf()'s after the pthread_once() call, but the function that is called in pthread_once() has printf()'s inside it that never output to stdout :/ Here are some links in case I'm not making sense: http://perforce.freebsd.org/fileViewer.cgi?FSPC=//depot/projects/ soc2005/launchd/liblaunch.c&REV=7 The function that calls pthread_once() is launch_msg() on line 692, the pthread_once() 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 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers- [EMAIL PROTECTED]" ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
pthread functions swallowing stdout, and stderr?
Howdy, I'm working on my SoC project, where one of the important, yet broken, functions is being called from pthread_once() I have printf()'s before the pthread_once() call to help me debug, and printf()'s after the pthread_once() call, but the function that is called in pthread_once() has printf()'s inside it that never output to stdout :/ Here are some links in case I'm not making sense: http://perforce.freebsd.org/fileViewer.cgi?FSPC=//depot/projects/ soc2005/launchd/liblaunch.c&REV=7 The function that calls pthread_once() is launch_msg() on line 692, the pthread_once() 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 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RFC: if_bridge
I'll throw another hme interface in my Sun Ultra 2 some time later today to test it out some more. Do you have any specific "tests" you would want us to run the if_bridge code through? Just simplistic bridging of two networks, or are there any bells and whistles you want me(/us) to setup 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 NetBSD (and OpenBSD). The patch and instructions can be found at: http://people.freebsd.org/~thompsa/ Highlights include: - 802.1d spanning tree support - management of the bridge MAC table - view bridged packets with bpf(4) - good firewall support I am especially interested in people who can test !i386, and users with existing STP networks. I am looking forward to getting your feedback! Andrew ___ freebsd-pf@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-pf To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
