I have read several books on the subject, and the best "howto' book for Tcl/Tk is Practical Programming in Tcl/Tk. It covers tcl/tk 8.0x, and is quite good for beginners and pros alike.
Ok, good enough. Until now, the best reference book is Practical Programming in Tcl/Tk. But that book is huge, and picking through to find the gems can be a pain.
I found the review as well thought out as it could be under the circumstances. My suggestion is that slashhdot should have book reviews done by people who have experience with the language.
As someone who is a very experienced Tcl/Tk programmer, I cannot trust a Tcl/Tk book review done by someone who admittedly has little or no experience with the language. Although the reviewer mentions that the book is not for the beginner, he lacks the understanding of the language to adequately comment on the ability of the book to address advanced issues.
Please understand that this is not an attack. As I said, I found the review gave a good overview of what is covered, all things concidered.
DHCP can be configured to serve static IP addresses. Configure your clients to use DHCP. The next time something like this happens, you'll have to edit one file on one server rather than visit 200 clients. I can't imagine having to do that, and if I had to, I would seriously reconcider my approach to IP management.
Why not use a private netwotk? Is there some reason why you need public-side IP addresses for your clients/servers? Cut your netowrk into a private side and a public side. Place all publically accessable boxes into the DMZ and secure them. You may need another router (or box) to route between the public and private side. The next time changes such as this are required, you need only reconfigure the public side boxes, leaving the clients as they are.
Make sure your clients never have to leave your network for services. From what I read I assume your clients are using your ISP's name servers?
I also have a question:
If you are the 'network' administrator, why are you concerned with client configurations? Is your job description sys damin/network admin? There should definately be a destinction between the two. Telecom analysts are not necessarily good sysadmins and good sysadmins might now know a thing about telecom.
While the writer may not have engineered the network he was hired to maintain, there is such a thing as re-engineering, time allowing of course.
On another note, DHCP can be configured to serve static addresses. This way, massive changes such as the one he suggests would require editing a single file on one of the servers, averting the headaches of visiting 200 desktops.
Slashdot Mirror
I have read your book.
It is also good starting point for people wanting to learn Tcl/tk, especially Tk.
A good piece of work.
I have read several books on the subject, and the best "howto' book for Tcl/Tk is Practical Programming in Tcl/Tk. It covers tcl/tk 8.0x, and is quite good for beginners and pros alike.
Ok, good enough. Until now, the best reference book is Practical Programming in Tcl/Tk. But that book is huge, and picking through to find the gems can be a pain.
What revision does it cover?
I found the review as well thought out as it could be under the circumstances. My suggestion is that slashhdot should have book reviews done by people who have experience with the language.
As someone who is a very experienced Tcl/Tk programmer, I cannot trust a Tcl/Tk book review done by someone who admittedly has little or no experience with the language. Although the reviewer mentions that the book is not for the beginner, he lacks the understanding of the language to adequately comment on the ability of the book to address advanced issues.
Please understand that this is not an attack. As I said, I found the review gave a good overview of what is covered, all things concidered.
DHCP can be configured to serve static IP addresses. Configure your clients to use DHCP. The next time something like this happens, you'll have to edit one file on one server rather than visit 200 clients. I can't imagine having to do that, and if I had to, I would seriously reconcider my approach to IP management.
Why not use a private netwotk? Is there some reason why you need public-side IP addresses for your clients/servers? Cut your netowrk into a private side and a public side. Place all publically accessable boxes into the DMZ and secure them. You may need another router (or box) to route between the public and private side. The next time changes such as this are required, you need only reconfigure the public side boxes, leaving the clients as they are.
Make sure your clients never have to leave your network for services. From what I read I assume your clients are using your ISP's name servers?
I also have a question:
If you are the 'network' administrator, why are you concerned with client configurations? Is your job description sys damin/network admin? There should definately be a destinction between the two. Telecom analysts are not necessarily good sysadmins and good sysadmins might now know a thing about telecom.
While the writer may not have engineered the network he was hired to maintain, there is such a thing as re-engineering, time allowing of course.
On another note, DHCP can be configured to serve static addresses. This way, massive changes such as the one he suggests would require editing a single file on one of the servers, averting the headaches of visiting 200 desktops.
Let's hope he has learned a lesson.