On Mon, 3 Mar 2025, David Dyck wrote:
> Is the format of /proc/mounts changing from being space delimited to being
> null delimited?
No. Fields are still delimited by space, and records are still delimited
by newlines. What has changed is that 'special' characters (space, tab,
newline, hash, ba
My earlier question was triggered by noticing several uses of the null
delimiter when reading from
/proc/*/mounts and/or /proc/mounts
I see now that there is cygwin-3.6.0-dev branch in
https://cygwin.com/git/newlib-cygwin.git
and I am catching up on the log entries
I am aware of other places wher
Is the format of /proc/mounts changing from being space delimited to being
null delimited?
where can I read more about this change?
On Sun, Mar 2, 2025 at 10:57 PM Jeremy Drake via Cygwin
wrote:
> On Sun, 2 Mar 2025, Jeremy Drake via Cygwin wrote:
>
> > > 2) assuming there is not, I want to make
On Sun, 2 Mar 2025, Jeremy Drake via Cygwin wrote:
> > 2) assuming there is not, I want to make a script using only things
> > present in a "base system" to clean them up.
>
> Now that the mount points are escaped and contain the Windows volume roots
> starting with 3.6, here's my script. It uses
On Mon, 3 Jun 2024, Jeremy Drake via Cygwin wrote:
> I'm not necessarily sure that the subject is clear enough, so I want to be
> explicit that I'm talking about files (or I guess potentially directories,
> though I've never seen that) generated by the `try_to_bin` function in
> winsup/cygwin/sysc
I'm not necessarily sure that the subject is clear enough, so I want to be
explicit that I'm talking about files (or I guess potentially directories,
though I've never seen that) generated by the `try_to_bin` function in
winsup/cygwin/syscalls.cc. Specifically, you can generate one with this
simpl
6 matches
Mail list logo
