> (Now that the hurly-burly of the of the UK election is over, I've got
> time to play again....)
>
> I was pleased to find that the standard techniques I used for
> installing earlier versions of win4lin under slackware worked OK for
> v3.0.
>
> As I recollect:-
>
> I broke out of the installer after the download,
> rescued the rpm from /var/win4lin/installer_tmp,
> converted it with rpm2tgz to .tgz format
> ran /opt/win4lin/remove_rpm.sh
> ran pkgtool to remove the old package,
> ran pkgtool to install the new one
> ran /opt/win4lin/postinst_rpm.sh
>
> and all was well
>
> any comments from other slack users, or Mike?
>
> Bob Hall
>
>
> --
> robert w hall
> _______________________________________________
> Win4Lin-users mailing list
> [EMAIL PROTECTED]
> https://lists.netraverse.com/mailman/listinfo/win4lin-users
Well.. I'm the one created the slackpacks for win4lin 2.x and I installed
3.0 using the installer stright off and it worked just fine so no need to
use rpm2tgz or such tool as far as I can tell..
Altho it wouldn't hurt if netraverse could add a few checks in the installed
to detect BSD 4.4 init and the create rc.Win4Lin in /etc/rc.d and add
something like:
if [ -f /etc/rc.d/rc.Win4Lin ]; then
. /etc/rc.d/rc.Win4Lin
fi
This should go into rc.local I guess.. just an idea for systems that use
BSD4.4 init.
But all in all win4lin 3.x is working fine.. just a few programs that
behaves wierd but the important ones work just great.
Olle - XMMS Staff
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
