K.-P. Kirchdörfer wrote:
Charles;
I may have found another small problem:
firewall# lrpkg -i squid-2.lrp
Installing squid-2 ... cat: /var/lib/lrpkg//boot.fstype: No such file or
directory
Done.
I was told:
It could be a bug (from the lrpkg script):
echo "$fn=-t `cat $lrpkgpath/boot.fstype` $d">>
Charles;
I may have found another small problem:
firewall# lrpkg -i squid-2.lrp
Installing squid-2 ... cat: /var/lib/lrpkg//boot.fstype: No such file or
directory
Done.
I was told:
It could be a bug (from the lrpkg script):
echo "$fn=-t `cat $lrpkgpath/boot.fstype` $d">>"$lrpkgpath/backdisk"
Charles
At 13:19 06.05.2004, Charles Steinkuehler wrote:
Erich Titl wrote:
No offense intended, I just felt that, if you go to the trouble of naming
root.blk.mk explicitly after the type of device it builds, it would be
logical to name the one that builds the character device nodes
accordingly
Erich Titl wrote:
No offense intended, I just felt that, if you go to the trouble of naming root.blk.mk explicitly after the type of device it builds, it would be logical to name the one that builds the character device nodes accordingly, e.g. root.chr.mk.
None taken. The root.blk.mk name was jus
Charles
At 17:26 05.05.2004 -0500, Charles Steinkuehler wrote:
>Erich Titl wrote:
>
>>Charles
>>I looked at the new linuxrc, nice, modular, easier to maintain.
>>At 22:14 05.05.2004, Charles Steinkuehler wrote:
>>
>>>- /dev/null in root.dev.mk (should be in root.blk.mk even though it's not a b
