Re: NTFS GSoC Project Idea

2012-03-26 Thread Efstratios Karatzas
On Tue, Mar 27, 2012 at 12:05 AM, Julian H. Stacey wrote: > Efstratios Karatzas wrote: > > Greetings, > > > > I am a FreeBSD GSoC 2010 student, looking to participate in this years > > GSoC. The project that I wish to work on is the FreeBSD NTFS driver. > > > > I 've already discussed my project

Re: NTFS GSoC Project Idea

2012-03-26 Thread Julian H. Stacey
Efstratios Karatzas wrote: > Greetings, > > I am a FreeBSD GSoC 2010 student, looking to participate in this years > GSoC. The project that I wish to work on is the FreeBSD NTFS driver. > > I 've already discussed my project idea with Attilio@ who suggested that I > forward my proposal to the hac

Re: Active slice, only for a next boot

2012-03-26 Thread Chris Rees
On 26 March 2012 18:10, wrote: > - Original Message - > From: John Baldwin > To: freebsd-hackers@freebsd.org > Cc: rank1see...@gmail.com, hack...@freebsd.org > Date: Mon, 26 Mar 2012 10:18:53 -0400 > Subject: Re: Active slice, only for a next boot > >> On Sunday, March 25, 2012 2:49:17 p

Re: BUG: REL 9.0 - 'boot0cfg' fails with providers of non 512 byte sectorsize

2012-03-26 Thread John Baldwin
On Monday, March 26, 2012 2:02:53 pm rank1see...@gmail.com wrote: > - Original Message - > From: John Baldwin > To: freebsd-hackers@freebsd.org > Cc: rank1see...@gmail.com, hack...@freebsd.org > Date: Mon, 26 Mar 2012 10:17:41 -0400 > Subject: Re: BUG: REL 9.0 - 'boot0cfg' fails with provi

NTFS GSoC Project Idea

2012-03-26 Thread Efstratios Karatzas
Greetings, I am a FreeBSD GSoC 2010 student, looking to participate in this years GSoC. The project that I wish to work on is the FreeBSD NTFS driver. I 've already discussed my project idea with Attilio@ who suggested that I forward my proposal to the hackers mailing list in order to get more fe

Re: Active slice, only for a next boot

2012-03-26 Thread rank1seeker
- Original Message - From: John Baldwin To: freebsd-hackers@freebsd.org Cc: rank1see...@gmail.com, hack...@freebsd.org Date: Mon, 26 Mar 2012 10:18:53 -0400 Subject: Re: Active slice, only for a next boot > On Sunday, March 25, 2012 2:49:17 pm rank1see...@gmail.com wrote: > > After having

Re: BUG: REL 9.0 - 'boot0cfg' fails with providers of non 512 byte sectorsize

2012-03-26 Thread rank1seeker
- Original Message - From: John Baldwin To: freebsd-hackers@freebsd.org Cc: rank1see...@gmail.com, hack...@freebsd.org Date: Mon, 26 Mar 2012 10:17:41 -0400 Subject: Re: BUG: REL 9.0 - 'boot0cfg' fails with providers of non 512 byte sectorsize > On Sunday, March 25, 2012 11:05:06 am rank

__NR_mmap2 in FreeBSD

2012-03-26 Thread Maninya M
I am trying to convert a function written for Linux to FreeBSD. What is the equivalent of the __NR_mmap2 system call in FreeBSD? I keep getting the error because of this exception: warn("Wanted space at address 0x%.8x, mmap2 system call returned 0x%.8x. This could be a problem.",addr,temp_regs.eax

Re: I want to write a 64-bit version of the driver, the MAKEFILE on how to write?

2012-03-26 Thread John Baldwin
On Sunday, March 25, 2012 10:38:17 pm cz li wrote: > I want to write a 64-bit version of the driver, the MAKEFILE on how to > write?I can compile 64-bit version of the driver in the 32 system? > Thank you! Drivers generally use the same makefiles (if you mean a module makefile) for both i386 and

Re: Active slice, only for a next boot

2012-03-26 Thread John Baldwin
On Sunday, March 25, 2012 2:49:17 pm rank1see...@gmail.com wrote: > After having a thought about this issue and also currently looking at a BootEasy boot manager ... > 'boot0cfg' is almost perfect for this task and should/could be "exploited". > > It's '-o noupdate' already does a major task, of

Re: BUG: REL 9.0 - 'boot0cfg' fails with providers of non 512 byte sectorsize

2012-03-26 Thread John Baldwin
On Sunday, March 25, 2012 11:05:06 am rank1see...@gmail.com wrote: > I've created a vnode image (md0) with sectorsizes of 8192 and 4096 > > After installing MBR's bootcode '/boot/boot0', in provider 'md0' I did: > # boot0cfg -o noupdate -m 0xc md0 > boot0cfg: read /dev/md0: Invalid argument > # bo