Hi I ve just made two new ebuilds that compiles OCFS2 and it s tools. Enjoy! Reproducible: Always Steps to Reproduce: Just uncompress the tar.gz to /usr/portage and emerge them. Actual Results: Wow I m running a kernel with ocfs2.
Created attachment 62684 [details] ocfs2-tools
Created attachment 62685 [details] The kernel module
Uhm, didn't the kernel part get accepted into Linus's upstream already? Or am I thinking of something else?
(In reply to comment #3) > Uhm, didn't the kernel part get accepted into Linus's upstream already? Or am I > thinking of something else? It isnt on vanilla kernel, ocfs1 isnt there too.
Created attachment 62761 [details] new ocfs2-tools package Added IUSE gtk2 Added DEPEND from python, pygtk, e2fsprog and readline. Removed RDEPEND. Added the configuration section for /etc/init.d, /etc/default and /etc/ocfs2. New ebuild info on post install.
Created attachment 62763 [details] new kernel module package Removed configuration section from this package, ocfs2-tools handles that. Removed deprecated options on configure. Added RDEPEND on ocfs2-tools.
Created attachment 65494 [details] 1.0.0 version - kernel module This is 1.0.0 release of ocfs2 kernel module. Changes: * Upgraded to 1.0.0 * Added Gentoo copyright notice in ebuild * Added suggestion about generic_drop_inode
Created attachment 65495 [details] 1.0.0 version - userspace tools This is 1.0.0 version of ocfs2 userspace tools. Changes: * Upgraded to 1.0.0 * Added Gentoo copyright notice * Corrected IUSE typo * Corrected DEPEND * Fixed dynamic compilation * Wrote gentoo-style init scripts * Kept /config and /dlm dirs * Wrote INSTALL.GENTOO mini-howto * Lame-fixed python library paths Please test.
(In reply to comment #7) the path to the kernel patch in the ewarn misses the /work/ocfs2-1.0.0/ part. the statement I used to patch the kernel: cat /var/tmp/portage/ocfs2-1.0.0/work/ocfs2-1.0.0/patches/export_generic_drop_inode.patch | patch -p1 Both ocfs2 and ocfs2-tools build fine here (2.6.12-gentoo-r6 i686). Thanks for the ebuild!
(In reply to comment #9) > the path to the kernel patch in the ewarn misses the /work/ocfs2-1.0.0/ part. Quite true, my bad. I also found that upgrading from ocfs2-0.99.* (or from a previous manual install) breaks if /config and /dlm are already present. I'll correct both things, as well as kernel deps and few other tidy-ups, and upload it as 1.0.0-r1 when finished. Is INSTALL.GENTOO clear enough? Any comments from developers?
Created attachment 66023 [details] 1.0.1 version - kernel module
Created attachment 66025 [details] 1.0.1 version - userspace tools Changelog: * Took out BUG from INSTALL.GENTOO about kernel upgrade * Added "unmounts" to stop() of init script (actually, stole it from netmount) * Added check for existing /dlm or /config * Corrected patch path (Thanks to Michael Steinmann)
# lynx -head -dump http://oss.oracle.com/projects/ocfs2/dist/files/source/ocfs2-1.0.1.tar.gz HTTP/1.0 404 Not Found
404 confirmed. Can someone bump the ebuild or provide an alternative location for the files?
(In reply to comment #14) > 404 confirmed. > Can someone bump the ebuild or provide an alternative location for the files? they moved the sources up one level (/v1.0), ocfs2-1.0.1.ebuild: -SRC_URI="http://oss.oracle.com/projects/ocfs2/dist/files/source/${P}.tar.gz" +SRC_URI="http://oss.oracle.com/projects/ocfs2/dist/files/source/v1.0/${P}.tar.gz"
ocfs2-1.2.0 released 2006.02.16
vanilla-kernel-2.6.16 with experimental ocfs2 was released. Please add the ocfs2-tools ebuilds to portage (current version 1.2.0, available from http://oss.oracle.com/projects/ocfs2-tools/dist/files/source/v1.2/ocfs2-tools-1.2.0.tar.gz) Thanks!
Created attachment 82943 [details] 1.2.0 version - userspace tools (sys-fs/ocfs2) New ebuild for ocfs2-tools v1.2.0. Fixes a couple of typos and inconsistencies within the INSTALL.GENTOO file and the ocfs2.init script.
Created attachment 89092 [details, diff] patch from ocfs2-tools-1.2.0 to 1.2.1 patch for 1.2.0 to 1.2.1, some paths have changed.
Could someone attach plain-text versions of the current files so it's easier to review them?
I see sys-fs/ocfs-tools -- is that the same thing as your ocfs2-tools?
(In reply to comment #21) > I see sys-fs/ocfs-tools -- is that the same thing as your ocfs2-tools? Got bored, did the research, no it's not. I do find one feature of ocfs2 crippling, however. From the manual: "Whereas one can add new nodes to the cluster dynamically, any other change, like name, ip address, requires the cluster to be restarted for the changes to take effect." Seriously, who wants to be restarting the whole cluster for changes to a single node.
Created attachment 90203 [details] Plain Text ebuild for 1.2.1 plain text ebuild for ocfs2 version 1.2.1 primary Daniel Frankes ebuild, only version bump to 1.2.1 and some corrected paths
Can we please get ocfs2-tools into Portage? TIA!
Added, thanks for your patience!
