Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

MS Teams channels cannot contain MS-DOS device names

learn.microsoft.com

Post reply on HN
Print view View original

311–320 of 364 posts

Re: MS Teams channels cannot contain MS-DOS device names

#311

Post by doubleg72 »

kentonv wrote: post #202
saalweachter wrote: post #193

Earlier quoted context omitted.

Arch wasn't around in 1998. I'm going to put my money on Slackware.

I think it was RedHat. I had tried Debian first but switched to RedHat pretty quickly afterwards. (Back then, RedHat had nothing to do with "enterprise", it was just the most polished Linux distro around. Ubuntu didn't exist yet.) (These days FWIW I use boring old Debian, and I'm not a zealot about it. It works for me. Use what works for you, I don't care. I have a separate machine for gaming and it runs Windows. I k…

I ran Mandrake back then but also toyed with RH and Slackware. Back when all the leets ran enlightenment or fluxbox!

Re: MS Teams channels cannot contain MS-DOS device names

#312

Post by Brian_K_White »

gadders wrote: post #156
thefz wrote: post #33

Earlier quoted context omitted.

> essentially leaking the existence of something terrible inside It's just a restriction imposed on SharePoint folder names bubbling up. Nothing fancy.

It goes lower than that. Try creating a directory called "LPT1" in DOS

omg

Re: MS Teams channels cannot contain MS-DOS device names

#313

Post by yndoendo »

SoftTalker wrote: post #82
eastbound wrote: post #43

Earlier quoted context omitted.

Those should obviously be UUIDs. Labels and titles should be a simple changeable, internationalizable attribute. Like usernames. You don’t use usernames as primary keys for anything, do you? What happens when people marry?

> You don’t use usernames as primary keys for anything, do you? HAHAHAHHHAAHAHA Seen this so many times I literally laughed out loud.

Windows actually uses SIDs to map internal users to windows settings such as profile locations and group policies. Open regedit and under HKEY_USERS there will be the SID for your user account which maps to HKEY_CURRENT_USER.

Linux has UIDs that map to the username.

Both methods allow for changing the user name without having to change permissions on files. Both need manual manipulation to transition the user's folder name to the new username. Both also allow for creating a user folder that does not match the username. Example HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList on Windows.

Best practice and reality are two different things. Even Microsoft often will use the fully qualified user profile path in their coding instead of %USERPROFILE%, example would be OneDrive. Just look at the Environment key in regedit for the current user.

Re: MS Teams channels cannot contain MS-DOS device names

#314

Post by KETpXDDzR »

kentonv wrote: post #170

Circa 1998 I was a teenage Linux zealot who would attend LAN parties carrying a Linux box. It actually worked -- at the time, WINE practically existed to support Starcraft, Quake 2 could run natively, and that covered like 95% of what people were playing. One time I thought it would be funny to run a shell script that looped through every Windows share on the network and tried to open `CON/CON` on it, resulting in a…

Oh good old Windows nuker.

Re: MS Teams channels cannot contain MS-DOS device names

#315

Post by hn92726819 »

slaymaker1907 wrote: post #178
hn92726819 wrote: post #161

Earlier quoted context omitted.

It looks like non-utf8 is not allowed: https://superuser.com/questions/204287/what-characters-are-f... Maybe it goes without saying, but for completeness, / is not allowed in filenames, and neither is null terminator (0x00 or \0) on mac either. On Linux, only / and null terminator are banned from filenames.

Sadly, you are not correct about slashes. They are allowed in filenames for Macs https://alexwlchan.net/2021/slashes/

Thanks for the correction! It seems more complicated after looking more into it.

According to https://en.m.wikipedia.org/wiki/Filename , reserved characters are:

HFS:

> :

HFS+:

> : on disk, in classic Mac OS, and at the Carbon layer in macOS; / at the Unix layer in macOS

APFS:

> In the Finder, filenames containing / can be created, but / is stored as a colon (:) in the filesystem, and is shown as such on the command line. Filenames containing : created from the command line are shown with / instead of : in the Finder, so that it is impossible to create a file that the Finder shows as having a : in its filename.

TIL about a 'carbon layer' and 'POSIX layer'

Re: MS Teams channels cannot contain MS-DOS device names

#316

Post by wolfgang000 »

eddythompson80 wrote: post #200
Roark66 wrote: post #24

Why is it that most "chat/conference" apps become horrible sooner or later? I still remember when teams used to be an OK app. It even had a Linux desktop client. I remember when slack was actually fast, I remember Skype out being more reliable to make phone calls than my mobile/cell service. Today slack is extremely slow if you add few organisations to it (but at least you can add more than one). Teams has deprecated…

Because believe it or not, a chat/conference is the most easy gateway to an "everything app" just like with WeChat. Afterall, a chat/conference app is a microcosm of the "internet". Your chat app is great but imagine if we can send/share audio clips too. Your chat app is great but imagine if we can send/share video clips too. Your chat app is great but imagine if we can send/share live video too. Your chat app is gre…

I completely agree, I did a very small chat app just for fun, I thought, this is only going to take me a couple of days and before I realized it, that couple of days became weeks and it never felt finished, there was always something to add.

Re: MS Teams channels cannot contain MS-DOS device names

#317

Post by mmis1000 »

tenebrisalietum wrote: post #191
mmis1000 wrote: post #167

Earlier quoted context omitted.

I think it is already killed by telegram even before discord emerges. The only thing you can't do on other IM other than IRC is having a really big chatroom that contains thousands of people. But it is no longer the case after telegram. BTW, i think an irc bot is a good target if you are starting to learn writing a network program. The protocol is really simple(don't need complex xml parser...etc) yet requires all te…

IRC is so trivial that hosting your own is easy. Telegram is awesome but it's still centralized.

The same argument applies to discord. Well discord is great but no self-host, and teamspeak can be self-hosted.

The reality? Nobody cares. Even for most tech related communities. Most people just want somewhere they can share a join link to other to allow other to join without hassle.

Re: MS Teams channels cannot contain MS-DOS device names

#318

Post by inkyoto »

cesarb wrote: post #213
aidenn0 wrote: post #185

Earlier quoted context omitted.

Linux treats filenames as bytes and only disallows the ascii slash and null. All other bytes are fair game.

> [...] and only disallows the ascii slash and null. All other bytes are fair game. There's also the special treatment of "", ".", and ".." (that is, a file or directory name consisting entirely of zero, one, or two dots), and the convention that a name starting with a dot is hidden.

> and the convention that a name starting with a dot is hidden.

It is a UNIX shell implementation level convention. The file system and the kernel don't care, and a shell is not obliged to honour the convention.

Re: MS Teams channels cannot contain MS-DOS device names

#319

Post by inkyoto »

m3047 wrote: post #119
m3047 wrote: post #94

Earlier quoted context omitted.

> leaking the existence of something terrible inside If you should get the opportunity to look at a raw (DNS) NXDOMAIN passive DNS (PDNS) feed there's a lot of plain brokenness, but the nuggets can be truly alarming. This is what happens when translating between naming services: naming services typically have application domains, and names in one context are interpreted differently in another. Bobby Tables is well kn…

Looking at the list of characters and character ranges the omission of 7F is curious.

If my memory serves me well, 7F was historically used for the «Delete» key code, and outputting it on a real terminal (or in terminal emulator), would result in the in-place text deletion from the output.

Not that it has been relevant in last 2-3 decades tho.

Re: MS Teams channels cannot contain MS-DOS device names

#320

Post by nomel »

Anthony-G wrote: post #139
glonq wrote: post #70

Earlier quoted context omitted.

Whenever I create a filename that is long or has spaces, I still pause and worry "okay, what might break if I do this", even though such concerns probably died a couple decades ago. Actually scripts breaking if files or paths have a space in them seems to be a thorn in the side of dev/ops/it folks that never goes away, does it?

Unix shell scripts will break when filenames/paths have spaces if variable expansions are not quoted, resulting in word splitting and filename expansion (globbing). This is something that is drilled into learners by all good teachers, e.g., https://mywiki.wooledge.org/Quotes#When_Should_You_Quote.3F

Wait until you hear about `make`, completely cementing the idea of '_' as space for decades to come [1]!

Related, any time I join a new group, that uses bash in any capacity, I introduce them all to the `shellcheck` utility [2], and run a shell script of the person with the largest ego through, as a "demo".

[1] https://stackoverflow.com/a/9838604/1487072

[2] Online version: https://www.shellcheck.net/

Post reply on HN