Re: [Genext2fs-devel] "configure" of CVS checkout fails, missing "install-sh"
Brought to you by:
bestouff
From: Robert P. J. D. <rp...@mi...> - 2005-01-04 10:31:09
|
On Tue, 4 Jan 2005, Xavier Bestel wrote: > Le lundi 03 janvier 2005 =E0 16:17 -0500, Robert P. J. Day a =E9crit : > > there appears to be a new oddity with the latest CVS checkout. > > if i just run the executable with no args whatsoever, i get: > > > > $ ./genext2fs > > number of blocks too low, increasing to 0 > > number of inodes too low, increasing to 12 > > ./genext2fs: too small filesystem > > $ > > > > didn't this used to just give a usage message? > > I don't think so, but perhaps it would be a good idea to do so. hmmm ... i have a "genext2fs" executable currently sitting in my /usr/local/bin, dated dec 10. i can't imagine i could have got it =66rom anywhere other than a CVS checkout at that time and, when i run it, i get: $ /usr/local/bin/genext2fs Usage: /usr/local/bin/genext2fs [options] image Create an ext2 filesystem image from directories/files -x image Use this image as a starting point -d directory Add this directory as source -f file Add nodes (e.g. devices) from this spec file -b blocks Size in blocks -i inodes Number of inodes -r reserved Number of reserved blocks -g path Generate a block map file for this path -e value Fill unallocated blocks with value -z Make files with holes -v Print resulting filesystem structure -h Show this help Example of spec file: drwx /dev crw- 10,190 /dev/lcd brw- 1,0 /dev/ram0 Report bugs to xav...@fr... how odd. rday |