On Fri, 20 Apr 2001, David Douthitt wrote:
> Not a bad idea; however, there are a few things that come to mind:
>
> * How do you create a VFAT diskette under Windows? Some may laugh; I
> for one am not sure how....
Beats me. I think it's a simple matter of formatting under Windows. I'll
give it a shot tonight.
> * What about DOS diskettes? 1.44M preformatted diskettes?
Require a reformat assuming that they aren't already VFAT formatted. Even
for the average Windows user formatting a disk isn't difficult.
> * What of mkfs.msdos? Does it understand VFAT?
Yep. 'mkdosfs -F 32 /dev/fd0[uXXXX]' does the trick.
> > Why not change the package format? It's possible to work with deb and rpm
> > pacakges in shell-script using nothing more than dd, gzip, cat, and tar.
>
> So I've heard; however, RPM files have not worked that way in my
> experience - they require rpm2cpio to get anything decent out. Also,
> last time I started untarring (more recent) DEB files there was always
> an error or warning about a particular file - it may have been called
> '-' or something.
I'm also against moving away from text-and-script-controlled tarballs.
About the only thing that might compel me to want to do so is the ability
to add apt-get for LRP, with a package repository on Sourceforge to allow
people to auto-update - and even then, I might need some arm-twisting.
"Keep It Simple, 'cause they're Stupid" my History teacher always used to
say.
> > and I think we could
> > have minimal dependancy checking (for library existance/version, kernel rev,
> > etc) without too much bloat to the packaging scripts...
>
> How to check for library version? You could use:
>
> LIBC=$(ls -1 /lib/libc-*)
> LIBC=${LIBC%%.so}
> LIBC=${LIBC##*/libc-}
>
> ...but then you are relying on the name to be correct. Is it?
I don't know about you, but I didn't do anything to the names when I put
together my 2.1.3 modules. On LRP 2.9.8, I get the following:
Veil# ls -1 /lib/libc-*
/lib/libc-2.0.7.so
At that point it's simply a matter of a naming convention. Anyone who's
making images that mess with the libs should be aware that libc NEEDS to
be named that for packages to work correctly.
> For the kernel, you'd probably be best with
>
> KERNEL=$(uname -r)
> KERNEL=${KERNEL%%-*}
>
> ...this assumes that uname -r works; does it?
It does:
Veil# uname -r
2.2.18
Veil#
--
George Metz
Commercial Routing Engineer
[EMAIL PROTECTED]
"We know what deterrence was with 'mutually assured destruction' during
the Cold War. But what is deterrence in information warfare?" -- Brigadier
General Douglas Richardson, USAF, Commander - Space Warfare Center
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel
