Clifford Wolf wrote:

<snip>
ROCK Linux isn't a source based distribution - it is a distribution built
kit. That means it is a toolchain for building binary distributions from
source.
</snip>

Yes, of course. Forgive me, but I'm really struggling in putting precisely
what I mean. My point was not for ROCK itself, but for its target
distributions, but sentences tend to grow in length when one wants to be
correct here... ;-)
So what can an end-user do after installing the dRock CDs in order to get
the latest security patches for his system? As far as I can see there's no
standard end-user tool like SuSE's YaST Online Update or swaret for
Slackware. At first sight this might look logical, as patches are normally
provided by the vendor/distributor, ie by the person or group who built that
particular target.
But as far as I can see noone really provides patches or updates for ROCK
targets, at the moment. Which makes ROCK targets a little less interesting
to end-users than other distros.

But I think this has not to remain that way. The build system creates a
large repository of binaries. What about just throwing together what
everyone had built successfully, and offer it for download from a central
FTP source?
Ok, it won't be quite that easy, and there would be many details to be
determined. But I think, most of the things needed are already there, as
parts of the build system (tool chain). What's missing is just a tool like
apt-get or swaret.

Of course, this is not something of the core requirements for ROCK, as this
is about targets and not ROCK itself. However, wouldn't it be good for ROCK
as a whole, if the targets were more attractive for end-users?

Just a thought...


<snip>
> Creating initrd data:
> -> Create linuxrc binary.
> ./scripts/Build-Target: line 8: diet: command not found
> ./scripts/Build-Target: line 9: diet: command not found
> ./scripts/Build-Target: line 10: diet: command not found
> ./scripts/Build-Target: line 14: diet: command not found
>
/home/alex/ROCK/trunk/build/bootdisk-2.1.0-DEV-x86-bootdisk/ROCK/logs/*.log:
> No such file or directory
> </snip>
>
> Maybe that's because Slack has no mkinitrd, but I don't know.


no. that's because slack doesn't have dietlibc installed. building the
bootdisk still needs a dietlibc on the build host - this is a design bug
which will be solved by the "target finish-hook" which is on our todo list.

yours,

 - clifford

</snip>

Ooops... I guess the error message was *too* obvious this time... It clearly
says what the problem is, and it doesn't mention mkinitrd, at all... Sorry
for the confusion, and thanks for the explanation.

Best wishes

   Alex

-- 
+++ Jetzt WLAN-Router f?r alle DSL-Einsteiger und Wechsler +++
GMX DSL-Powertarife zudem 3 Monate gratis* https://www.gmx.net/dsl

_______________________________________________
rock-user mailing list

https://www.rocklinux.net/mailman/listinfo/rock-user