Re: RB_NOSYNC -> no device_shutdown ?
on 20/12/2011 16:11 John Baldwin said the following: > On Saturday, December 17, 2011 6:07:51 pm Andriy Gapon wrote: [snip] >> and wonder why RB_NOSYNC is overloaded to mean that no >> MOD_SHUTDOWN/device_shutdown cleanup should be done? > > Presumably most device_shutdown handlers were used for syncing storage when > the module stuff was first added. I'm not sure how you would fix this now > since you can't easily pass the 'arg2' flags down to each handler so that the > appropriate ones could skip their shutdown actions. I see what you are saying. Couple of thoughts: - maybe MOD_EVENT interface could/should be extended to pass another argument along with the event type - maybe various sync-ing stuff should be done in shutdown_post_sync event handlers, or even via a new dedicated event Hmm, it looks like the latter might actually already be the case. And another tangentially related idea: maybe we should inhibit device/module shutdown for the RB_HALT case given that it is a quite special case where the system actually stays up and at least the keyboard is expected to be still operational. -- Andriy Gapon ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: building on FreeBSD 7.3 with Clang
On 2012-01-09 20:38, Lenny Maiorani wrote: Hi. I am trying to build a userspace application on FreeBSD 7.3 with Clang. I have come across 2 problems so far and I am looking for any tips or guidance the community has. My problems are both related to binutils so far: 1. Missing symbols : http://llvm.org/bugs/show_bug.cgi?id=9758 2. crtendS.o problem : http://sourceware.org/bugzilla/show_bug.cgi?id=12887 At this point I need to rebuild my toolchain to get a new crtendS.o. Are there other pitfalls I need to be aware of? It's probably easiest to install the binutils port, and use that for building clang and your application. Otherwise, you can manually apply the patches mentioned in LLVM PR 9758 to your system binutils, and recompile them. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
bsdinstaller
Hi, in this new freebsd installer (bsdinstall) can I have only the ssys extracted? Can I delete all src directories after install, just leaving sys intact? Is it some dependency between the sources? Why the default now its extracting all? Thiago ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: RB_NOSYNC -> no device_shutdown ?
On Tuesday, January 10, 2012 5:23:45 am Andriy Gapon wrote: > on 20/12/2011 16:11 John Baldwin said the following: > > On Saturday, December 17, 2011 6:07:51 pm Andriy Gapon wrote: > [snip] > >> and wonder why RB_NOSYNC is overloaded to mean that no > >> MOD_SHUTDOWN/device_shutdown cleanup should be done? > > > > Presumably most device_shutdown handlers were used for syncing storage when > > the module stuff was first added. I'm not sure how you would fix this now > > since you can't easily pass the 'arg2' flags down to each handler so that > > the > > appropriate ones could skip their shutdown actions. > > I see what you are saying. > Couple of thoughts: > - maybe MOD_EVENT interface could/should be extended to pass another argument > along with the event type > - maybe various sync-ing stuff should be done in shutdown_post_sync event > handlers, or even via a new dedicated event > > Hmm, it looks like the latter might actually already be the case. I almost think the best way (ugh) is to have a global variable similar to boothowto that device_shutdown methods can use to skip behavior if needed. It may only be a fairly small number of devices that need to skip their shutdown routine (or portions thereof) during a nosync shutdown. > And another tangentially related idea: maybe we should inhibit device/module > shutdown for the RB_HALT case given that it is a quite special case where the > system actually stays up and at least the keyboard is expected to be still > operational. I think we still want to do device_shutdown in that case. The mfi(4) driver sends a specific command to note a clean shutdown that then affects how the event log behaves on the next boot, for example. -- John Baldwin ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: bsdinstaller
On Tuesday, January 10, 2012 6:49:55 am Thiago Damas wrote: > Hi, > in this new freebsd installer (bsdinstall) can I have only the ssys > extracted? Can I delete all src directories after install, just > leaving sys intact? > Is it some dependency between the sources? Why the default now its > extracting all? The new installer just builds the src tarball that way. I asked for the same feature, but it didn't make it into 9. Deleting all the extra bits will work for now. If you are up for it, you can look at patching the release build process and bsdinstall to restore this feature. I'm not sure it would be useful to split out all the top-level src directories as the old installer did, but having one tarball for the equivalent of the old 'sbase' + 'ssys' and a second tarball for the rest of the source tree (so you can do 'none', 'kernel-only' or 'full source') would probably be a useful thing to implement. -- John Baldwin ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: building on FreeBSD 7.3 with Clang
On Jan 10, 2012, at 4:44 AM, Dimitry Andric wrote: > On 2012-01-09 20:38, Lenny Maiorani wrote: >> Hi. >> >> I am trying to build a userspace application on FreeBSD 7.3 with Clang. I >> have come across 2 problems so far and I am looking for any tips or guidance >> the community has. >> >> My problems are both related to binutils so far: >> 1. Missing symbols : http://llvm.org/bugs/show_bug.cgi?id=9758 >> 2. crtendS.o problem : >> http://sourceware.org/bugzilla/show_bug.cgi?id=12887 >> >> At this point I need to rebuild my toolchain to get a new crtendS.o. Are >> there other pitfalls I need to be aware of? > > It's probably easiest to install the binutils port, and use that for > building clang and your application. > > Otherwise, you can manually apply the patches mentioned in LLVM PR 9758 > to your system binutils, and recompile them. Hi Dimitry, Do you mean the binutils port from 9.0? I will try that. Thanks for the info, -Lenny ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
