Re: Adding functions to libutil, part 2

2024-06-21 Thread Reinoud Zandijk
Hi Micheal, On Fri, Jun 21, 2024 at 11:27:33AM -, Michael van Elst wrote: > >> We also have 'df' where 'df -W' prints the original symbolic path > >> (but just for NAME=) because a resolved symbol path cannot be > >> reversed. > > >'df -W' just uses getmntinfo() and mount(8) only calls getfss

Re: Adding functions to libutil, part 2

2024-06-21 Thread Michael van Elst
rein...@dropje.13thmonkey.org (Reinoud Zandijk) writes: >> We have 'fsck' which resolves the device name and 'fsck_*' that gets passed >> the resolved name. >If they were never intended to be used separately then shouldn't they be in >libexec? Well, that's history for you :) >> We also have 'd

Re: Adding functions to libutil, part 2

2024-06-21 Thread Reinoud Zandijk
Hi Michael, thanks for your feedback, On Fri, Jun 21, 2024 at 06:24:53AM -, Michael van Elst wrote: > rein...@netbsd.org (Reinoud Zandijk) writes: > > >that returns a canonical raw device name when passed a device name in one of > >the following ways: > > /dev/ld0 > > name="UUID" > >

Re: Adding functions to libutil, part 2

2024-06-20 Thread Michael van Elst
rein...@netbsd.org (Reinoud Zandijk) writes: >that returns a canonical raw device name when passed a device name in one of >the following ways: > /dev/ld0 > name="UUID" > name="ROOT.x" > /dev/dk1 > /some/mountpoint > some/file/name That looks like many distinc