Hi, i just wish to gain some feedback on the following topic
: Naming/Formatting of OS-ShortNames - Asking for Additions
I am using ( for nearly two decades right now ) a self-thought/-taught formatting of shortnames for Operating-systems in their diversifications, like editions, service-pack states, etc.
Let me explain on a basic version ( 1st Mutator|Phase || General Definition )
EXAM | For example :
BMWN61SC // BootMgr - MicroSoft - Windows - NT - Family: 6 - Generation: 1 - Family-Type|Family-Release: Server - Family-Edition|Family-Variant : Core
so Syntax in short is like
: BootLoader - OS:Manufacturer|Author|Class - OS:Name-General - OS:Family-Name - OS:Family-Version||-Title - OS:Family-Generation - OS:Family-Type||:Family-Release(Service-Pack|RollOut|Mutation) - OS:Edition||:Variant
some more examples to make it easier to understand
Boot-Loader: NTLDR | Manufacturer: MicroSoft | OS-Name: Windows | OS-Family-Name: NT | OS-Family-Version: 5 | Family-Generation: 1 | Family-Release: 3 | Family-Edition: Home
... in clear-text as originally named : MicroSoft Windows XP SP3 Home Edition
Boot-Loader: GRUB | Manufacturer: Canonical | OS-Name: Linux | OS-Family-Name: Debian | OS-Family-Title: Ubuntu | Family-Generation: P=Precise-Pangolin=12.04 | Family-Release: 5 | Family-Edition: Alternate
... in clear-text as originally named : ( Debian-based Linux by Canonical ) Ubuntu Precise Pangolin 12.04 Release 5 Alternate
So you might have an idea, what my naming convention points out ; But what is it for ?
Due to the fact i am active with/on Computers of any kind since 1987 ( age of 10 ) and i am in need of systematics to remember things ( Asperger-Syndrome ) i use Schemes like these in any occasion to remember and define things ; You can think of it as a possibility to recognize things while itself points out in what context it is/will be used ;
I am using this naming-scheme ( vaguely remembering ) since the days of Suse-Linux 4 / Windows 98/, something inbetween; I got that idea while experiencing QNX in its Floppy-Based-Version and first contacts with the interna of Windows NT 3.1/4.0 and as i have always (coming from a HC-Background : Commodore C4/64 / Amiga 500 / Atari ST , etc. ) try to use things that are handled in the same manner indepent of analogue/digital || print/screen || handwritten/mnemonic to define what i am actually working on / running / using ;
So far to the story behind :
What i am out for ?
I wish to have some feedback on how you ( yes, each of you ) would handle OS-Short-Names according to my scheme; it's like having a counter-check on the variants i already use.
The reason why ?
Well, i am looking out for releasing my ' personal secrets ' in handling any kind of install/setup/deployment--tasks i've used in the last 3 decades and though i have always been able to differ things for myself, i was constantly asked what the cryptography secret behind this naming scheme is ; So i wish to have your thoughts to work it out as a precise scheme, in order to give it back to the community .
If you ask why One is using such a scheme :
Since the Home-Computer days ( besides custom disk-geometries / self-defined disk-access/-format ) we have a small but efficient and allday-used least common denominator for file/folder-naming/-sort :
It is mostly called FAT ( File Allocation Table )
and as ( especially here o reboot.pro ) most people know : FAT has some simple limitations, like
8.3-File-Names ( 8 chars followed by file-type-extension of 3 chars separated by dot ) ;
if you have counted the chars for my OS-Short-Naming you come to ?
BMWN513H || GCLDUP5A ... Yep, 8 characters
This kind of Naming can even be used on an Atari ST or a Commodore 64 .
However, i think i explained enough and in full detail.
It would be very nice and kind of all of you if you would please the request by just thinking out loud:
HOW WOULD YOU NAME THE OPERATING-SYSTEMS YOU PERSONALLY USE ACCORDING TO MY NAMING-CONVENTION GIVEN ABOVE ?
THANKS FOR YOUR INTEREST .
: To the networking Guys and those that wish to state this is nonsense -- consider to remember the naming-limitations of NetBios / SMB/ Samba calls ( WorkGroups/Node-Names) ; you might see why it is useful to have a short-naming convention that is identical from file-based ( e.g.: for systems booted on uefi-systems ESP via grub4dos/plop from usb/pxe stored on FAT reachable as same-named-node in a network, possibly for experimental/teaching/learning-use in a home-/school- -network or in deployment-scenarios whereas you steer the deployment via wifi to xxx-nodes by stacking up the needed variants locally to them cisco-switches via serial // if you know about - you'll get the idea ... )
Edited by S466531257BOSS, 04 August 2015 - 06:43 PM.