Difference between revisions of "Talk:Extended host attribute matching"

From WPKG | Open Source Software Deployment and Distribution
Jump to: navigation, search
Line 5: Line 5:
 
[[User:StefanP|StefanP]] 19:31, 27 July 2011 (CEST)
 
[[User:StefanP|StefanP]] 19:31, 27 July 2011 (CEST)
  
 +
: I thought they could be useful if you are going to prepare your packages for a specific OS. Of cause everybody can check them out from the logs, but if you are in the process of setting up packages for new OSs the list might come handy. I personally really would like to know what OS strings there are "in the wild".
  
I thought they could be useful if you are going to prepare your packages for a specific OS. Of cause everybody can check them out from the logs, but if you are in the process of setting up packages for new OSs the list might come handy. I personally really would like to know what OS strings there are "in the wild".
+
: When building regular expressions it is always nice to know what strings they might match. Sure, you can parse your logs on your own, but isn't it nicer if there is some community driven list already available?
  
When building regular expressions it is always nice to know what strings they might match. Sure, you can parse your logs on your own, but isn't it nicer if there is some community driven list already available?
+
: If you don't like the idea, feel free to remove the list I have started.
  
If you don't like the idea, feel free to remove the list I have started.
+
:: I do not think about removing it, but about its usefulness.
 +
 
 +
:: Wouldn't a generic list be as good?
 +
:: Who really needs the different editions of Win7 (Ultimate, Professional, Home, Starter), if there is no significant difference?
 +
 
 +
:: I envision a list of pattern matches like below.
 +
 
 +
:: Windows XP SP2 ................. os="sp2.+5\.1\.[0-9][0-9][0-9][0-9]"
 +
:: Windows 7/Server 2008 R2 ... os="6\.1\.[0-9][0-9][0-9][0-9]"
 +
:: Windows Server 2008 R2 ...... os="server.+6\.1\.[0-9][0-9][0-9][0-9]"
 +
 
 +
:: This would be something a user can use directly, without the need to invent match pattern on their own.
 +
 
 +
:: What do you think?
 +
:: [[User:StefanP|StefanP]] 00:04, 1 August 2011 (CEST)

Revision as of 22:04, 31 July 2011

Could the person posting the O/S strings explain their usefulness?

Anyone can check them out in their log files ;-)

StefanP 19:31, 27 July 2011 (CEST)

I thought they could be useful if you are going to prepare your packages for a specific OS. Of cause everybody can check them out from the logs, but if you are in the process of setting up packages for new OSs the list might come handy. I personally really would like to know what OS strings there are "in the wild".
When building regular expressions it is always nice to know what strings they might match. Sure, you can parse your logs on your own, but isn't it nicer if there is some community driven list already available?
If you don't like the idea, feel free to remove the list I have started.
I do not think about removing it, but about its usefulness.
Wouldn't a generic list be as good?
Who really needs the different editions of Win7 (Ultimate, Professional, Home, Starter), if there is no significant difference?
I envision a list of pattern matches like below.
Windows XP SP2 ................. os="sp2.+5\.1\.[0-9][0-9][0-9][0-9]"
Windows 7/Server 2008 R2 ... os="6\.1\.[0-9][0-9][0-9][0-9]"
Windows Server 2008 R2 ...... os="server.+6\.1\.[0-9][0-9][0-9][0-9]"
This would be something a user can use directly, without the need to invent match pattern on their own.
What do you think?
StefanP 00:04, 1 August 2011 (CEST)