Prev: Why do ports tree have two neon ports?
Next: FreeBSD Port: sylpheed-2.7.1_1
From: =?ISO-8859-1?Q?Samuel_Mart=EDn_Moro?= on 18 Mar 2010 05:54
Hi.

I made two patches for ntfsprogs.
(and btw, I don't know: who's the port mainter? who should I give these
patches?)

The first one, in libntfs/device.c, adding the correct defines, to get the
device geometry.
The second one, in ntfsprogs/mkntfs.c, managing character (previously
block)devices.

Also, the second patch correct an infinite loop, when linking to libublio
(and/or its 'bad' use in ntfsprogs):

Indeed, using UBLIO_BLOCK_SIZE 262144 may work while working on the entire
device.
But while working on parts, it may be better to use sector_per_track *
sector_size (or something like that...).
Otherwise, ublio try to read after the end of the drive.


With these patches, mkntfs is correctly working without ublio.
And it quite works with ublio (ask for a chkdsk under windows to make the
end boot, only if partitionning disk, but I guess one can run
UBLIO_BLOCK_SIZE=`expr 63 '*' 255` mkntfs $dev to avoid troubles).

there's still an other problem I did'nt fix yet:
a chkdsk under windows, after formatting with mkntfs, says there's a bad
$UpCase file.
Indeed, a few differences between the two versions...
I'll post the next patch when I'll have time to work on it.



Samuel Martín Moro
{EPITECH.} tek4
CamTrace S.A.S
sorry for my english...
From: Gary Jennejohn on 18 Mar 2010 06:31
On Thu, 18 Mar 2010 10:54:14 +0100
Samuel Mart__n Moro <faust64(a)gmail.com> wrote:

> I made two patches for ntfsprogs.
> (and btw, I don't know: who's the port mainter? who should I give these
> patches?)
>

There isn't a maintainer. The best thing is to file a PR with your
patches attached so they won't get lost in the noise.

---
Gary Jennejohn
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: =?ISO-8859-1?Q?Samuel_Mart=EDn_Moro?= on 18 Mar 2010 07:09
done
thanks

Samuel Martín Moro
{EPITECH.} tek4
CamTrace S.A.S


On Thu, Mar 18, 2010 at 11:31 AM, Gary Jennejohn
<gary.jennejohn(a)freenet.de>wrote:

> On Thu, 18 Mar 2010 10:54:14 +0100
> Samuel Mart__n Moro <faust64(a)gmail.com> wrote:
>
> > I made two patches for ntfsprogs.
> > (and btw, I don't know: who's the port mainter? who should I give these
> > patches?)
> >
>
> There isn't a maintainer. The best thing is to file a PR with your
> patches attached so they won't get lost in the noise.
>
> ---
> Gary Jennejohn
>
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Jan Henrik Sylvester on 18 Mar 2010 10:17
As you are working on ntfsprogs, are you able to use ntfsresize at all?

For me, ntfsresize never worked in ntfsprogs-2.0.0, but it did in
ntfsprogs-1.13.1. We had a discussion about ntfsprogs on
freebsd-questions almost a year ago:

http://lists.freebsd.org/pipermail/freebsd-questions/2009-April/thread.html#196207

I still do not know more than I stated in there:

http://lists.freebsd.org/pipermail/freebsd-questions/2009-April/196252.html

I still would like to create an ports/ntfsprogs1 (back)port to get
ntfsprogs-1.13.1 back. Unfortunately, I have not had time to do this
since then.

Maybe you want to check yourself, if 1.13.1 gives less problems than
2.0.0...

Although ntfsprogs is not maintained anymore, mkntfs and ntfsresize are
still useful -- thus picking the best last release and fixing that on
current FreeBSD may be worse it.

Cheers,
Jan Henrik
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: =?ISO-8859-1?Q?Samuel_Mart=EDn_Moro?= on 18 Mar 2010 13:00
I already tested ntfsprogs1.

I don't remember wich version exactly (found it with portdowngrade), nor
what were its problems.

But, it was for work.
We just wanted to be able to mount/write and format devices with ntfs
partitions.
And we weren't able to.
It might be that I didn't think to try without libublio support (don't
remember, I'm not even sure ublio is used in the first version).

It may be usefull to get back the first version in ports, sure.
But there's not that much things to adapt in the current version.
The problem is that the person who made that port just copied the package
from linux, without porting it.
The modifications I made were very easy to find out, every
C developer should be able to do them quickly, putting some printf.
I don't have FreeBSD at home, I'm just working on it at office. And patching
ArchLinux at home.
I might not be able to finish patching ntfsprogs2 to make it completly work
on FreeBSD.

The good news is that, with my patch to ntfslib, ntfsresize should now be
able to get the geometry of a device.
Maybe that was its only problem, and so it's working again?
I'll give it a try next monday.


Cheers,

Samuel Martín Moro
{EPITECH.} tek4
CamTrace S.A.S

On Thu, Mar 18, 2010 at 3:17 PM, Jan Henrik Sylvester <me(a)janh.de> wrote:

> As you are working on ntfsprogs, are you able to use ntfsresize at all?
>
> For me, ntfsresize never worked in ntfsprogs-2.0.0, but it did in
> ntfsprogs-1.13.1. We had a discussion about ntfsprogs on freebsd-questions
> almost a year ago:
>
>
> http://lists.freebsd.org/pipermail/freebsd-questions/2009-April/thread.html#196207
>
> I still do not know more than I stated in there:
>
> http://lists.freebsd.org/pipermail/freebsd-questions/2009-April/196252.html
>
> I still would like to create an ports/ntfsprogs1 (back)port to get
> ntfsprogs-1.13.1 back. Unfortunately, I have not had time to do this since
> then.
>
> Maybe you want to check yourself, if 1.13.1 gives less problems than
> 2.0.0...
>
> Although ntfsprogs is not maintained anymore, mkntfs and ntfsresize are
> still useful -- thus picking the best last release and fixing that on
> current FreeBSD may be worse it.
>
> Cheers,
> Jan Henrik
>
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

 |  Next  |  Last
Pages: 1 2
Prev: Why do ports tree have two neon ports?
Next: FreeBSD Port: sylpheed-2.7.1_1