Aside from MAC address, there are no network parameters that
'belong' to a computer:
Take the scenario where you have two OSes installed on 1
computer:
- Each OS can have it's own: IP, Netmask, gateway etc.
These cannot be defined at the hardware level - at all. In
fact none can be defined without an OS.
- If you can go on to to parameters like: URL, DOMAIN,
hostname, WORKGROUP and so on - you'll easily see that the
same rule applies: they are all defined at the OS level,
none apply at the computer level.
As for the MAC address, which is the only parameter that can
be directly associated with hardware: even this data item is
really associated with the network CARD hardware installed
in the computer, and not the computer itself - thus the
computer can have numerous MAC addresses - depending on the
amount of network cards it has installed.
I think the current approach, where network data is assigned
to OS is the correct design.
Dan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
in the case the computer is in the same physical location,
IP, gateway, MAC should be the same. We are talking about
production environment, are we?
Example: I have bought OS campus license - 1 unit. How,
using this approach i should describe the computer?
Now every OS instance is binded to the particular box, and
in the case i need to get the count of OS'es used, it will
not reflect the actual situation.
> thus the computer can have numerous MAC addresses -
> depending on the amount of network cards it has installed.
Yes. So maybe network parameters should be binded to NIC
cards? But what should be done in the case the comouter has
built-in NIC? Or a computer has miltiport NIC card?
Maybe it's possible to add 'Interfaces' description (like
there is OS, software, hardware)?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm not familiar with the 'campus' license, and in general I
don't understand why your setup requires to assign network
data to a computer. Doesn't settle with my logic of how
things work.
As far as I can see, you're missing the idea that an OS is
an _instance_ of an OS, specifically the one installed on a
certain computer. So a particular OS is assigned to
specific hardware (=computer) where it is installed.
Thus by proxy the network data is also associated with that
computer.
I think it would be more comfortable to continue this via
email. mail me at: dan.a@hotpop.com
Dan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=126473
Hello:
Aside from MAC address, there are no network parameters that
'belong' to a computer:
Take the scenario where you have two OSes installed on 1
computer:
- Each OS can have it's own: IP, Netmask, gateway etc.
These cannot be defined at the hardware level - at all. In
fact none can be defined without an OS.
- If you can go on to to parameters like: URL, DOMAIN,
hostname, WORKGROUP and so on - you'll easily see that the
same rule applies: they are all defined at the OS level,
none apply at the computer level.
As for the MAC address, which is the only parameter that can
be directly associated with hardware: even this data item is
really associated with the network CARD hardware installed
in the computer, and not the computer itself - thus the
computer can have numerous MAC addresses - depending on the
amount of network cards it has installed.
I think the current approach, where network data is assigned
to OS is the correct design.
Dan
Logged In: NO
Hi,
in the case the computer is in the same physical location,
IP, gateway, MAC should be the same. We are talking about
production environment, are we?
Example: I have bought OS campus license - 1 unit. How,
using this approach i should describe the computer?
Now every OS instance is binded to the particular box, and
in the case i need to get the count of OS'es used, it will
not reflect the actual situation.
> thus the computer can have numerous MAC addresses -
> depending on the amount of network cards it has installed.
Yes. So maybe network parameters should be binded to NIC
cards? But what should be done in the case the comouter has
built-in NIC? Or a computer has miltiport NIC card?
Maybe it's possible to add 'Interfaces' description (like
there is OS, software, hardware)?
Logged In: YES
user_id=126473
Hi
I'm not familiar with the 'campus' license, and in general I
don't understand why your setup requires to assign network
data to a computer. Doesn't settle with my logic of how
things work.
As far as I can see, you're missing the idea that an OS is
an _instance_ of an OS, specifically the one installed on a
certain computer. So a particular OS is assigned to
specific hardware (=computer) where it is installed.
Thus by proxy the network data is also associated with that
computer.
I think it would be more comfortable to continue this via
email. mail me at: dan.a@hotpop.com
Dan