On Fri, Jul 24, 2020 at 09:52:29AM -0400, Greg Wooledge wrote:
[...]
> I don't know of any specific term for a directory's physical
> manifestation, other than "directory".
>
> In the olden days, a directory was basically a series of 16-byte
> records (14 bytes for the filename, 2 bytes for the
On Fri, Jul 24, 2020 at 09:56:27AM -0400, The Wanderer wrote:
> On 2020-07-24 at 09:50, to...@tuxteam.de wrote:
[...]
> Since writing that, I've had occasion to remember the term 'dirent',
> which I think is more the in-memory representation of a directory than
> the on-disk representation, but m
On 2020-07-24 at 09:50, to...@tuxteam.de wrote:
>
> On Fri, Jul 24, 2020 at 09:42:24AM -0400, The Wanderer wrote:
>
>> On 2020-07-24 at 09:22, to...@tuxteam.de wrote:
>>> Nitpick: the directory entry is the one carrying the name.
>>
>> I had the impression that even a directory is stored in/as
On Fri, Jul 24, 2020 at 09:42:24AM -0400, The Wanderer wrote:
> On 2020-07-24 at 09:22, to...@tuxteam.de wrote:
>
> > On Fri, Jul 24, 2020 at 07:54:27AM -0400, Greg Wooledge wrote:
> >
> >> On Fri, Jul 24, 2020 at 07:49:26AM -0400, The Wanderer wrote:
> >>
> >>> Sounds like a case where directly
On Fri, Jul 24, 2020 at 09:42:24AM -0400, The Wanderer wrote:
On 2020-07-24 at 09:22, to...@tuxteam.de wrote:
On Fri, Jul 24, 2020 at 07:54:27AM -0400, Greg Wooledge wrote:
On Fri, Jul 24, 2020 at 07:49:26AM -0400, The Wanderer wrote:
Sounds like a case where directly editing the underlying
On Fri, Jul 24, 2020 at 09:42:24AM -0400, The Wanderer wrote:
> On 2020-07-24 at 09:22, to...@tuxteam.de wrote:
>
> > On Fri, Jul 24, 2020 at 07:54:27AM -0400, Greg Wooledge wrote:
> >
> >> On Fri, Jul 24, 2020 at 07:49:26AM -0400, The Wanderer wrote:
> >>
> >>> Sounds like a case where directly
On 2020-07-24 at 09:22, to...@tuxteam.de wrote:
> On Fri, Jul 24, 2020 at 07:54:27AM -0400, Greg Wooledge wrote:
>
>> On Fri, Jul 24, 2020 at 07:49:26AM -0400, The Wanderer wrote:
>>
>>> Sounds like a case where directly editing the underlying device,
>>> to modify inode-or-equivalent contents s
On Fri, Jul 24, 2020 at 07:54:27AM -0400, Greg Wooledge wrote:
> On Fri, Jul 24, 2020 at 07:49:26AM -0400, The Wanderer wrote:
> > Sounds like a case where directly editing the underlying device, to
> > modify inode-or-equivalent contents such that the slash is no longer
^
Nitpick:
On Fri, Jul 24, 2020 at 07:49:26AM -0400, The Wanderer wrote:
> Sounds like a case where directly editing the underlying device, to
> modify inode-or-equivalent contents such that the slash is no longer
> there, might even be *advisable*.
Yeah, some sort of direct hex-edit on the unmounted file sy
On 2020-07-24 at 07:45, Greg Wooledge wrote:
> On Thu, Jul 23, 2020 at 07:16:06PM -0400, The Wanderer wrote:
>
>> On 2020-07-23 at 06:26, Andrei POPESCU wrote:
>>> Seriously? Could you please show me how would I create a file on
>>> *nix containing '/' in the name?
>>
>> It's theoretically possi
On Thu, Jul 23, 2020 at 07:16:06PM -0400, The Wanderer wrote:
> On 2020-07-23 at 06:26, Andrei POPESCU wrote:
> > Seriously? Could you please show me how would I create a file on *nix
> > containing '/' in the name?
>
> It's theoretically possible, but AFAIK basically nothing would support
> it or
>>> Yes. Unfortunately Systemd decided to forbid '/' in unit names,
You can probably work around that by using '⁄', for example ;-)
Stefan
On 2020-07-23 at 06:26, Andrei POPESCU wrote:
> On Mi, 22 iul 20, 16:26:24, Jonathan Dowland wrote:
>
>> On Wed, Jul 22, 2020 at 07:38:54AM -0400, Greg Wooledge wrote:
>>
>>> Apparently this unit refers to the root file system. I have no
>>> idea why it's masked for you, but that's where I'd st
13 matches
Mail list logo
