From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Duncan Greatwood Newsgroups: gmane.emacs.bugs Subject: bug#72450: 29.1; Tramp Failed to Parse OS Name and Version for Windows 11 Date: Sun, 4 Aug 2024 20:39:19 -0700 Message-ID: References: <86y15cucg3.fsf@gnu.org> <87frrkk7ze.fsf@gmx.de> <867ccwsl77.fsf@gnu.org> <87bk28k1yy.fsf@gmx.de> <8634nksh16.fsf@gnu.org> <877ccwk142.fsf@gmx.de> <861q34sgb3.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000c72282061ee76c2b" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="7419"; mail-complaints-to="usenet@ciao.gmane.io" Cc: dgbulk@gmail.com, Michael Albinus , 72450@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Aug 05 05:42:15 2024 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1saobt-0001mx-So for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 05 Aug 2024 05:42:14 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1saobV-0003JM-I7; Sun, 04 Aug 2024 23:41:49 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1saobS-0003JA-6l for bug-gnu-emacs@gnu.org; Sun, 04 Aug 2024 23:41:47 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1saobM-0003QM-GL for bug-gnu-emacs@gnu.org; Sun, 04 Aug 2024 23:41:45 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debbugs.gnu.org; s=debbugs-gnu-org; h=Date:From:In-Reply-To:References:MIME-Version:To:Subject; bh=KhVxzA51jsHa76Q1bsttBlzIYZDdMt3G6Hhj1F0/MmM=; b=MxvFKKPeROQBT78PTL/S+o5PdqvUoYXkRFI/B6AaToIBPoDR9i0ExJi7tlQWcdTOCttcN2geRvrnZazckB84PioB2yojCeEQRz8quuTDdOfRc60Mu432OOWRFNPKabdaQ2AsZlsAYHqexUTysW6QdIoPLdpYwoOCUH4hl29fTB0Ob7s+5pCO9gOr0qRXKFa+Ugkc/NjDdmiN10qyBGFb8O8dDHkMDBAPQVUHB/mUNHgGxDes8lSku96oM01amtCIWAC2m7CXmntYVlTuiB6AoTdVikD2iglbdUH0K30ShyM9fEmC/HNg8bwgIJgGexugAN4nhuyGK2axpZRy1fRDyA==; Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1saobh-0007rG-W5 for bug-gnu-emacs@gnu.org; Sun, 04 Aug 2024 23:42:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Duncan Greatwood Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 05 Aug 2024 03:42:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 72450 X-GNU-PR-Package: emacs Original-Received: via spool by 72450-submit@debbugs.gnu.org id=B72450.172282926630017 (code B ref 72450); Mon, 05 Aug 2024 03:42:01 +0000 Original-Received: (at 72450) by debbugs.gnu.org; 5 Aug 2024 03:41:06 +0000 Original-Received: from localhost ([127.0.0.1]:57673 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1saoan-0007o4-7a for submit@debbugs.gnu.org; Sun, 04 Aug 2024 23:41:06 -0400 Original-Received: from mail-lf1-f52.google.com ([209.85.167.52]:60772) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1saoak-0007nB-VG for 72450@debbugs.gnu.org; Sun, 04 Aug 2024 23:41:04 -0400 Original-Received: by mail-lf1-f52.google.com with SMTP id 2adb3069b0e04-52fc4388a64so15911116e87.1 for <72450@debbugs.gnu.org>; Sun, 04 Aug 2024 20:40:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1722829174; x=1723433974; darn=debbugs.gnu.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=KhVxzA51jsHa76Q1bsttBlzIYZDdMt3G6Hhj1F0/MmM=; b=QX5npaCQBT0c1cNtLxXiUkOuVYxhQDp7aph3rzp2+VSSDdPqNrSSBVbF2g9nAL7Mt5 EJYZlj6VRHJJhlCis+H6g5Zd+lE0VIG7j63wlpjy6O6f6KB09xf1EdRdjBgXkZp81Mnh MgP/4mrlM7Et1lJ09mbHFySBWfX1TqoXhsQKnWyIlnucK2WnmvqSijHxKVKiLLzSc6Ei la28SLdbnkjm3qYFodh7iXogyHzRm1aYFv7VZs/aT94ObEc2PTvZILBiV0CGw7pvHIo5 Lhbj/heoOaQ8suT4AE5X31Tg5hp1242NCxShamrzchRyV7/JHB1nY4bsm0qc/f4xnQ8U qlCQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722829174; x=1723433974; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=KhVxzA51jsHa76Q1bsttBlzIYZDdMt3G6Hhj1F0/MmM=; b=WU8tu+2ZKzlCK33Vg/vxL0x7NGFnu5BOiKXNLSH3IKrUjHLzSQllLUXuNsYfdakNSr l7JSockQzRM4tmSWv9j9gzLQVCiPTRB0kswFMtETsn8ljCuvmlwPk2TUAbDuOtstJ3MY cRxF+lnF6eUgJvkJSyy6nMas54lBz3Rh7BHWwPxG5MOsPjWOWMPaBZFrwQDGisbKOPoI 8ef7NllqVUcA7Li4sc9CB5/6WEUPdmbw71Z5XkZbHGQ5wDcwM305amo5RuGvpvK7k6y5 Du8eHGKOgM8jWd0rD0FX/+qY0LDexNbk2p605FQsjCPytq0qevQsZ2hmfvxCiW34tXY9 Q3AA== X-Forwarded-Encrypted: i=1; AJvYcCVQUPbp5NrNGKGnR5XJbli40t2efWsMCC6pbmq2R5bh2bC+5w8OqZPd9ylWSP0egWgweRKZ/w==@debbugs.gnu.org X-Gm-Message-State: AOJu0YzEPfYzlPdSzA5czZFFd0xUXZ2TnAsLVR4h/Cka7qkNSKmve9V9 mzbQK6jYv6vzcGM5FHrRSDV63Q5FVOwvc94XEAgleMoAcGrP6ZSwc/weDDhu X-Google-Smtp-Source: AGHT+IE1SjAI4wjXsKTFJ/GWHzUQ63iUngMSGmfoXm0cPkZwBj00eRZfFZGisFnnLIH84ZVt3IXQfg== X-Received: by 2002:a05:6512:1111:b0:52f:c13f:23d2 with SMTP id 2adb3069b0e04-530bb38101dmr7168658e87.25.1722829173553; Sun, 04 Aug 2024 20:39:33 -0700 (PDT) Original-Received: from mail-lf1-f44.google.com (mail-lf1-f44.google.com. [209.85.167.44]) by smtp.gmail.com with ESMTPSA id 2adb3069b0e04-530bba29f6asm980061e87.120.2024.08.04.20.39.31 for <72450@debbugs.gnu.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 04 Aug 2024 20:39:32 -0700 (PDT) Original-Received: by mail-lf1-f44.google.com with SMTP id 2adb3069b0e04-52efc89dbedso11933297e87.3 for <72450@debbugs.gnu.org>; Sun, 04 Aug 2024 20:39:31 -0700 (PDT) X-Forwarded-Encrypted: i=1; AJvYcCX+XchzO551h1Ifu5yLpbEILDUX0wKlGCslbUIZkiOaFE3v2BomVESuF3m8Tr9A8PBHEo3bqw==@debbugs.gnu.org X-Received: by 2002:a05:6512:2209:b0:52e:9670:e40b with SMTP id 2adb3069b0e04-530bb39b7bfmr7217043e87.39.1722829171522; Sun, 04 Aug 2024 20:39:31 -0700 (PDT) In-Reply-To: <861q34sgb3.fsf@gnu.org> X-Gmail-Original-Message-ID: X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:289782 Archived-At: --000000000000c72282061ee76c2b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Michael and Eli - Thanks for your comments so far. I am not conscious of having installed any "special" MSYS(2) components, nor have I consciously installed WSL. However, I have enabled Developer Mode in Windows settings, which may have caused the installation of this "sh". In any case, regarding the versions of "sh" and "uname": sh-5.2$ sh --version GNU bash, version 5.2.26(1)-release (x86_64-pc-msys) Copyright (C) 2022 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software; you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. sh-5.2$ sh-5.2$ uname --version uname (GNU coreutils) 8.32 Copyright (C) 2020 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later < https://gnu.org/licenses/gpl.html>. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Written by David MacKenzie. sh-5.2$ If I may, the extra characters in the emacs error message might not come from the uname on windows - that uname seems to work OK on the windows side at least - it could be a misparsing in emacs (or even an mistake gathering the error message, I suppose). Regarding using SMB, it is not super convenient in that i) the target windows machine is not directly accessible right now, it is accessible via an intervening ssh proxy; and ii) SMB seems pretty retro to me in 2024, but maybe that's just me. However, for my personal purposes I could probably figure out how to do SMB (e.g. something like https://unix.stackexchange.com/questions/38099/have-samba-proxy-for-another= -server, or by setting up a VPN, or...). For additional background, Windows is running as a KVM/QEMU VM on an Ubuntu machine; the Ubuntu machine is acting as the ssh proxy, the Windows VM is directly accessible solely from the Ubuntu machine; this is a common network configuration with VMs of course. >From an emacs perspective, it seems a shame not to be able to use ssh, given that modern Windows commonly supports ssh and provides a bash shell. Depending on your own available bandwidth etc. of course. BTW, emacs seems to be taking some time before finally producing an error message. If there is a way to log what is happening in emacs - what tramp is trying, what happens, etc., I'd be happy to. Or LMK how I could help otherwise. Best -DG On Sun, Aug 4, 2024 at 4:01=E2=80=AFAM Eli Zaretskii wrote: > > From: Michael Albinus > > Cc: dgbulk@gmail.com, 72450@debbugs.gnu.org > > Date: Sun, 04 Aug 2024 12:56:29 +0200 > > > > Eli Zaretskii writes: > > > > > So I guess accessing Windows via ssh is not really supported, and the > > > OP should be advised to use "smb" instead? > > > > It's preferable, yes. But I would wait for his comment, before we close > > this bug. > > Sure, I didn't mean to suggest that we close this bug right away. > --=20 NOTICE: This email and its attachments may contain privileged and=20 confidential information, only for the viewing and use of the intended=20 recipient. If you are not the intended recipient, you are hereby notified= =20 that any disclosure, copying, distribution, acting upon, or use of the=20 information contained in this email and its attachments is strictly=20 prohibited and that this email and its attachments must be immediately=20 returned to the sender and deleted from your system. If you received this= =20 email erroneously, please notify the sender immediately.=C2=A0 Xage Securit= y,=20 Inc. and its affiliates will never request personal information (e.g.,=20 passwords, Social Security numbers) via email.=C2=A0 Report suspicious emai= ls to=20 security-alerts@xage.com --000000000000c72282061ee76c2b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Michael and Eli -

Thanks for your co= mments so far.

I am not conscious of having=C2=A0i= nstalled any "special" MSYS(2) components,=C2=A0nor have I consci= ously installed=C2=A0WSL. However, I have enabled Developer Mode in Windows= settings, which may have caused the installation of this "sh".

In any case, regarding the versions of "sh&quo= t; and "uname":
sh-5.2$ sh --version
GNU bash, version 5= .2.26(1)-release (x86_64-pc-msys)
Copyright (C) 2022 Free Softwar= e Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <= ;http://gnu.org/licenses/gpl.h= tml>

This is free software; you are free = to change and redistribute it.
There is NO WARRANTY, to the exten= t permitted by law.
sh-5.2$
sh-5.2$ uname --version
uname (GNU coreutils) 8.32
Copyright (C) 2020 Free Softwar= e Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <= ;https://gnu.org/licenses/gpl= .html>.
This is free software: you are free to change and = redistribute it.
There is NO WARRANTY, to the extent permitted by= law.

Written by David MacKenzie.
sh-5= .2$

If I may, the extra characters in the = emacs error message might not come from the uname on windows - that uname s= eems to work OK on the windows side at least - it could be a misparsing in = emacs (or even an mistake gathering the error message, I suppose).=C2=A0
Regarding using SMB, it is not super convenient in that i)= the target windows machine is not directly accessible right now, it is acc= essible via an intervening ssh proxy; and ii) SMB seems pretty retro to me = in 2024, but maybe that's just me. However, for my personal purposes I = could probably figure out how to do SMB (e.g. something like=C2=A0https://unix.stackexchange.com/questions/38099/have-samba-prox= y-for-another-server, or by setting up a VPN, or...). For additional ba= ckground, Windows is running as a KVM/QEMU VM on an Ubuntu machine; the Ubu= ntu machine is acting as the ssh proxy, the Windows VM is directly accessib= le solely from the Ubuntu machine; this is a common network configuration w= ith VMs of course.

From an emacs perspective, it s= eems a shame not to be able to use ssh, given that modern Windows commonly = supports ssh and provides a bash shell. Depending on your own available ban= dwidth etc. of course.

BTW, emacs seems to be taki= ng some time before finally producing an error message. If there is a way t= o log what is happening in emacs - what tramp is trying, what happens, etc.= , I'd be happy to. Or LMK how I could help otherwise.

Best
-DG





On Sun, Aug 4, 2024 at 4:01=E2=80=AFAM Eli Zaretskii <<= a href=3D"mailto:eliz@gnu.org" target=3D"_blank">eliz@gnu.org> wrote= :
> From: Mic= hael Albinus <michael.albinus@gmx.de>
> Cc: dgbulk@gmail= .com,=C2=A0 = 72450@debbugs.gnu.org
> Date: Sun, 04 Aug 2024 12:56:29 +0200
>
> Eli Zaretskii <el= iz@gnu.org> writes:
>
> > So I guess accessing Windows via ssh is not really supported, and= the
> > OP should be advised to use "smb" instead?
>
> It's preferable, yes. But I would wait for his comment, before we = close
> this bug.

Sure, I didn't mean to suggest that we close this bug right away.

NOTICE: This email and its attachmen= ts may contain privileged and confidential information, only for the viewin= g and use of the intended recipient. If you are not the intended recipient,= you are hereby notified that any disclosure, copying, distribution, acting= upon, or use of the information contained in this email and its attachment= s is strictly prohibited and that this email and its attachments must be im= mediately returned to the sender and deleted from your system. If you recei= ved this email erroneously, please notify the sender immediately.=C2=A0 Xag= e Security, Inc. and its affiliates will never request personal information= (e.g., passwords, Social Security numbers) via email.=C2=A0 Report suspici= ous emails to security= -alerts@xage.com
--000000000000c72282061ee76c2b--