Please use Reply all so that others can see your messages, too. (I hope your message to me wasn't meant to be private.)
On 24. 4. 2015 13:42, Rainer Schuetz wrote: >> I'm only guessing that the update process deleted some files and failed to >> replace them with new versions. Some information about that could be hidden >> in /var/log/pacman.log. > > I should’ve paid more attention to these things earlier. I installed a new > msys2 updated properly and the compared with winmerge - more than 100 files > were different. Copying everything from the new install into the old one > didn’t solve the issue so I am reinstalling. > > > I have a strong suspicion what went wrong. I have a sort of hacky ssh server > running (following > https://ghc.haskell.org/trac/ghc/wiki/Building/Windows/SSHD). I think the > fact it’s running blocks files from being accessible. So updates fail - > maybe, it’s that. Although I didn’t notice any feedback pointing to failed > update actions. Did you try to stop the SSH daemon after updating (and before manually re-writing files)? If I'm not mistaken, any new processes will fail to start, as long as there are old processes running. Maybe the problem could've been solved simply by restarting the daemon? >> Are you able to run bash or pacman from cmd? > > Kind of, but the path-mapping doesn’t work, so I had to use dos-paths. See below. > I already deleted everything because my system somehow got in this dirty > state. So I can’t follow this up any more, sorry... That's okay. > But out of (strong :)) interest: Is there a way to get into a msys shell from > the command line only - and without using a bat file? I am asking because I > would love to access msys2 via ssh. For now I helped myself by using two > sshd, one for the general Windows system and one for msys2. I’d much prefer > to enter the system via the general Windows ssh server and enter msys2 > through the command line. I can handle managing the paths and other settings > controlled via /etc/profile As long as you set MSYSTEM and call `bash --login -i`, you should be fine without having to fiddle with paths manually. > but I am not sure how activate the “msys-specific” functionality like path > mapping (c:\msys->/ etc). I don’t quite get at which stage that happens when > I read the open shell script batch file... I'm not sure what's the problem here. The virtualized filesytem is compiled into the runtime and there's no switch for enabling or disabling it AFAIK. Every(*) program in /usr/bin should understand what `/` means. *) Not actually every one; there's a few exceptions. > Thanks for any help > .r. -- David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________ Msys2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/msys2-users
