Re: Status of HFS support on FreeBSD
Hello Sreenath; Thank you for your interest in the HFS+ port. Around 2004-2005 there was an initial port done but the developer behind it lost interest and no one picked it up. Apparently the Apple code was very clean and a lot stuff just worked. Since then the Apple driver has advanced a lot though. My recommendation is to take a look at the webarchive link referred by in the wiki: https://wiki.freebsd.org/HFS Start from the newest XNU sources but take a look at the previous code for reference. Do try to keep some version control system (github, bitbucket, google code, etc) so that the effort can be picked up if you later lose interest. Note that this project is not tagged GSoC as it may take more dedication than just a Summer, however if we see there is interest, that the project is well planned, and even that some coding has started we would be likely to find a mentor. Pedro. ___ 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: Porting patch(1) from NetBSD to FreeBSD (was Re: FreeBSD in Google Code-In 2012? You can help too!)
Hello Hiren; On 10/27/2012 16:48, hiren panchasara wrote: + Sean, who has been helping me. On Sat, Oct 27, 2012 at 2:31 PM, Chris Rees cr...@freebsd.org mailto:cr...@freebsd.org wrote: On 27 October 2012 22:17, hiren panchasara hiren.panchas...@gmail.com mailto:hiren.panchas...@gmail.com wrote: [removing the CC list] On Wed, Oct 24, 2012 at 3:36 PM, Pedro Giffuni p...@freebsd.org mailto:p...@freebsd.org wrote: (cc'ing -ports and cutting most of the rest) From: Eitan Adler . On 24 October 2012 13:24, Fernando Apesteguía wrote: Also related to that, what about writing a section about redports[1] in the porter's handbook[2]? This is a good documentation task... but we need more *coding* tasks as well. We do need to port and test patch (1) from NetBSD or DragonFly to replace GNU patch, and this shouldn't be difficult. Hi Pedro / List, I am not part of google summer of code but I've tried to port patch(1) from NetBSD into FreeBSD head. I hope that is okay. Patching was trivial and It _seems_ to be working fine. I would appreciate any ideas around how to test the changes and how to proceed further. Have you a patch :)? You're right, there shouldn't have been many changes needed. Will prepare a patch and post here as soon as I get a chance :-) This is great news Hiren, Thanks! The stress test for this utility is the ports tree but before that we have to know what will change. What needs to be done is: 1- Compare the options between our old patch and the new BSD patch. 2- Document this in FreeBSD's wiki. 3- Prepare a port for testing. Unfortunately I will be very busy for more than a month and I can't help much but I am sure some other committer will love to follow on this. Thanks for taking the initiative, that's what FreeBSD needs! Pedro. ___ 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: Porting patch(1) from NetBSD to FreeBSD (was Re: FreeBSD in Google Code-In 2012? You can help too!)
Hi; On 10/27/2012 22:08, hiren panchasara wrote: On Sat, Oct 27, 2012 at 3:35 PM, Pedro Giffuni p...@freebsd.org mailto:p...@freebsd.org wrote: Hello Hiren; On 10/27/2012 16:48, hiren panchasara wrote: ... This is great news Hiren, Thanks! The stress test for this utility is the ports tree but before that we have to know what will change. Thanks Pedro! I will have a lot of questions as I am a newbie here. :-) What needs to be done is: 1- Compare the options between our old patch and the new BSD patch. Will do. 2- Document this in FreeBSD's wiki. I think this needs to be done when we are done deciding on diffs and how the changes look, right? Also, I do not think I have write access to the wiki. Well, I am hoping that we don't have to do any hacking on patch to be acceptable but having a table like this would be nice: http://wiki.freebsd.org/SOC2010BenFiedler This is mandatory though, just planning ahead. http://wiki.freebsd.org/SOC2010BenFiedler 3- Prepare a port for testing. Does this need to be a port? I thought this would live in /src/usr.bin/patch. Also, I believe this will co-exist with current gnu patch(1). Is that a right assumption? We like to be safe and having it in the ports tree makes it easier to test it on all FreeBSD versions and platforms before it finds it's way into the base system. I know this sounds like a long tedious process but we have a reputation to take care of ;). Creating a new port of this is really easy though; you can probably start with the bsd sort port as a template and check porter's handbook if there is any doubt. Let us know if you need to a place to put of the tarball. Pedro. ___ 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: FreeBSD in Google Code-In 2012? You can help too!
(cc'ing -ports and cutting most of the rest) From: Eitan Adler . On 24 October 2012 13:24, Fernando Apesteguía wrote: Also related to that, what about writing a section about redports[1] in the porter's handbook[2]? This is a good documentation task... but we need more *coding* tasks as well. We do need to port and test patch (1) from NetBSD or DragonFly to replace GNU patch, and this shouldn't be difficult. I would guess there are other interesting possibilities in the ports tree and new ports count as coding: http://wiki.freebsd.org/WantedPorts So i guess we need porting mentors. Pedro. ___ 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: libdwarf
Hello guys; We are not using the dwarfstd library because it is copyleft and SGI basically seems to have abandoned it for good. The Elftoolchain guys have taken over the development started by John Birrell and are the official maintainers of the BSD version: http://sourceforge.net/apps/trac/elftoolchain/ cheers, Pedro. ___ 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
Interest in a Summer of Code in Space?
Hello; This year the European Space Agency will have it's second Summer of Code in Space: http://sophia.estec.esa.int/socis2012/ This may be a good opportunity to get FreeBSD in yet-another interesting field, plus one of our projects in the Ideas Page seems to be ideal to get some funding from them: http://wiki.freebsd.org/IdeasPage#SCPS.2C_Space_Communication_Protocol_Standards Just thought I would share this in case someone is interested :). Cheers, Pedro. ___ 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: [gsoc2012] Port NetBSD's UDF implementation
Hi YongCon; The project would be very interesting for us. I am pretty sure you will not have problems finding a mentor. That said, let me point out an old thread: http://lists.freebsd.org/pipermail/freebsd-stable/2008-May/042565.html I think the biggest problem is that you will have to get acquainted with FreeBSD's Virtual Memory which is different from NetBSD's. In that same thread you will find some comments by Matt Dillon (no idea how up to date those are). It will not be an easy task but people find such challenges very rewarding. Pedro. ___ 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: NTFS GSoC Project Idea
Hello Efstratios ; In general, I agree with Gleb that you should start from the Apple Darwin port instead of spending time on the current FreeBSD driver. Please note that last year someone attempted to bring in smbfs from Darwin with your same strategy and failed: http://lists.freebsd.org/pipermail/soc-status/2011-June/000340.html Making it MPsafe may look relatively easy but it will take valuable time. In the case of ext2fs, for example, I am convinced it was only done in time because the ext2fs code is based on UFS1. Also the lack of write support has made the current NTFS driver undesirable and for a while, even before the MP-unsafe axing was defined, the driver was being considered for deprecation. Quite honestly I think we want the Darwin driver. If it serves as further encouragement, when I asked Yar about his HFS port he said everything he took from Darwin basically compiled. cheers, Pedro. ___ 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
