public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Hamish McIntyre-Bhatty <hamishmb@live.co.uk>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] python-getdevinfo
Date: Sun, 13 Sep 2020 17:08:57 +0100	[thread overview]
Message-ID: <DB7PR02MB399670F98FF5365B728F6D16E7220@DB7PR02MB3996.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <265cb8a3-d120-d018-d8f3-4961d48675ff@SystematicSw.ab.ca>


[-- Attachment #1.1.1: Type: text/plain, Size: 2689 bytes --]

On 13/09/2020 16:02, Brian Inglis wrote:
> On 2020-09-13 01:39, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>> On 13/09/2020 07:13, Achim Gratz wrote:
>>> Hamish McIntyre-Bhatty via Cygwin-apps writes:
>>>> Hmm, who decides (and how) what counts as a Linux distro?
>>> Something that is capable of and has actually done a license review.
>> Seems fair.
>>>> Either way, could anyone provide some insight as to whether bundling the
>>>> Cygwin DLL would allow Cygwin programs to access the virtual /dev and
>>>> /cygdrive paths? I have this all ready to be released for Windows, so
>>>> one way or another I'll need to make a bundle anyway for convenience.
>>> Yes, all the virtual fs are provided through the Cygwin DLL.
>> Excellent, thank you :)
>>>> It'd be great if it could make it into the official repos but I first
>>>> submitted this ITP around a month ago so I don't have high hopes as of
>>>> this point.
>>> You still haven't explained what it would be useful for.  This
>>> bare-metal stuff isn't something I'd usually consider doing from within
>>> a userland compatibility layer running on Windows.
>> My apologies - I thought I had but that must be a false memory. This
>> module is a device information collector, and in Cygwin's case it makes
>> it easy for users of DDRescue-GUI to find the link between the Windows
>> drive letters and Cygwin paths. It also provides other information such
>> as make and model, but this is limited on Cygwin because some of the
>> more low-level device management utilities don't exist, probably due to
>> bits of missing API as explained to me by Corrina (at least I think it
>> was her). It behaves very similarly on macOS and Linux, except it just
>> needs to inform the user of device details instead of also relating to
>> drive letters/Windows names.
>>
>> This is basically just a dependency for DDRescue-GUI (a GUI I wrote for
>> GNU ddrescue), and I had interest on getting this running easily on
>> Windows, so I thought Cygwin would be the way to go for better
>> compatibility. You can find DDRescue-GUI here:
>> https://www.hamishmb.com/html/downloads.php?program_name=ddrescue-gui
>> and the user guide is available from the nav bar if you want more
>> information about it.
>>
>> Does that answer your question - hopefully I didn't miss the point.
> Package smartmontools has access to some low level disk I/O features when run
> elevated under an admin account.

Yes, I think you (or maybe Corinna) told me this before - getdevinfo
compiles this together with other information to try and get as complete
a picture as possible. That was a useful tip for sure.

Hamish


[-- Attachment #1.1.2: 0x87B761FE07F548D6.asc --]
[-- Type: application/pgp-keys, Size: 3235 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-09-13 16:09 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-17 13:33 Hamish McIntyre-Bhatty
2020-08-17 13:34 ` Hamish McIntyre-Bhatty
2020-08-19  5:53   ` Marco Atzeri
2020-08-19 11:22     ` Hamish McIntyre-Bhatty
2020-08-20  6:01       ` Marco Atzeri
2020-08-21 15:33         ` Hamish McIntyre-Bhatty
2020-08-26  9:35           ` Hamish McIntyre-Bhatty
2020-09-02 15:29             ` Hamish McIntyre-Bhatty
2020-09-02 18:05               ` Marco Atzeri
2020-09-02 20:58                 ` Hamish McIntyre-Bhatty
2020-09-03 13:44                   ` marco atzeri
2020-09-03 14:10                     ` Hamish McIntyre-Bhatty
2020-09-03 16:34                       ` Ken Brown
2020-09-03 17:13                         ` Hamish McIntyre-Bhatty
2020-09-03 17:27                           ` Hamish McIntyre-Bhatty
2020-09-03 18:50                             ` Ken Brown
2020-09-04 13:38                               ` Hamish McIntyre-Bhatty
2020-09-09 10:36                                 ` Hamish McIntyre-Bhatty
2020-09-12 22:19                                   ` Hamish McIntyre-Bhatty
2020-09-13  6:13                                     ` Achim Gratz
2020-09-13  7:39                                       ` Hamish McIntyre-Bhatty
2020-09-13 15:02                                         ` Brian Inglis
2020-09-13 16:08                                           ` Hamish McIntyre-Bhatty [this message]
2020-09-14 18:29                                             ` Hamish McIntyre-Bhatty
2020-09-13 14:57                     ` Jon Turney
2020-09-13 16:07                       ` Hamish McIntyre-Bhatty
2020-09-22 13:32                         ` Hamish McIntyre-Bhatty

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DB7PR02MB399670F98FF5365B728F6D16E7220@DB7PR02MB3996.eurprd02.prod.outlook.com \
    --to=hamishmb@live.co.uk \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).