Date: Fri, 23 Feb 2001 16:15:18 -0500 From: Russell Cattelan <cattelan@thebarn.com> To: Terry Lambert <tlambert@primenet.com> Cc: Mike Declerck <declerck@sistina.com>, freebsd-fs@FreeBSD.ORG Subject: Re: Porting GFS to FreeBSD Message-ID: <3A96D2E6.7D21753D@thebarn.com> References: <200102230607.XAA09891@usr05.primenet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Terry Lambert wrote: BTW if anybody wants the code from the first time this port was started let me know. I did have it to the point where is was reading the superblock and mounting. Obviously the code is way out of sync but the vfs/vnode interface it there and mostly working. > > Sistina Software Inc is in the process of evaluating the effort to port the > > Global File System from Linux to FreeBSD. Before someone starts harping on > > the GPL let me state that Sistina is willing to have a separate license for > > the *BSD community so if we could put that discussion off to a later time I > > would appreciate it. > > OK, I stole an hour and a half from myself tonight, and hacked on > the src/tools code. > > I have about 20k of patches against the 4.x distribution that's > sitting out there as "4.0", and need an FTP incoming to upload > them too (or I can send a 20K email to someone who cares). > > I did *NOT* start with the CVS sources. > > The patches are to make it compile on FreeBSD 4.1, following > a configure, and using gmake, since the configure doesn't appear > to generate portable Makefiles. Should work on 4.2, will > probably fail for some dumb reason on -current. > > I used the disklabel ioctl() to get the number of 512b sectors > on the device, since it appears from looking at the disk drivers > that spit out the sizes for dmesg, that the in-core label will > have the correct value for this. I also fixed portability issues > in all the files I touched, and there is some room for some > common code that isn't common (I put in #warning for that). > > I tried to stick to the coding style already in the files, but > I am a bad boy when it comes to spacing around parenthesis, a > hard habit to break, so don't be surprised if there's some of > that crept in. > > Let me know if you want the code... and if so, how best to get > it to you. > > -- > > Here is the current status: > > Tools; "OK" means "compiles and appears to run"; special devices > are not present. > > ------------- ------------------------------------------------ > tool status > ------------- ------------------------------------------------ > gclient OK > gfs_expand OK > gfs_jadd OK > gfsconf OK > gserv OK > hexedit OK > initds OK > pinfo OK > assemble OK > mkfs OK (don't remember for sure) > mountgfs NEEDS KERNEL CODE AND AT LEAST A PARTIAL REWRITE > dmep_tools NEEDS CAM CONVERSION > gfs_tool FILE "gfs_debug.h" MISSING FROM DISTRIBUTION > gfsck FILE "gfs_debug.h" MISSING FROM DISTRIBUTION > ptool NEEDS LINUX SPINLOCK CODE EQUIVALENT > test_dmep NEEDS CAM CONVERSION > ucmemexp OK > ------------- ------------------------------------------------ > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-fs" in the body of the message -- Russell Cattelan -- Digital Elves inc. -- Currently on loan to SGI Linux XFS core developer. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A96D2E6.7D21753D>