Of course, the Linux server can add up as a firewall/internet gateway! What more would a small company want?
How about security?
Having your main fileserver double as a firewall is a Bad Idea. Throw a little 386DX33 and a pair of NICs up to handle your modem or DSL line. I'm not certain if a 386 can handle a full T1 (I know a P75 can fill the pipe without problem) but the message is the same: Firewalls work best when they also aren't full of doors, windows and conduit holes. Keep the network firewall seperate.
A photocopy repair person arrived in a white shirt and proceded to get toner all over it. When asked why he doesn't wear a black shirt he tells us that management won't allow it, they think it makes their repair-people look like gangsters.
Actually the photocopy repair dude was here today (Canon) -- he wears a black golf shirt with the company logo on it and a pair of beige pants. <looking down> hmmm... kind of like what I'm wearing, only I'm in R&D and I don't design photocopiers.
But that's the whole problem. You can't just say "I think I'll just use konqueror". Just doing a ps after you start up konqueror proves that. And then you could say "but when I close it, all that's gone again", but that isn't true either. Run _one_ KDE application, and immediately you have cruft sticking to your system. It might all serve it's purpose while the app is running. But when I close the app, and revert to my trusted Windowmaker, I want all of KDE's stuff to get outta there. And it doesn't do that.
Care to prove it? I am running WindowMaker as my WM and KDE2.1.1 with kdelib 2.1.2 (security/bug fix) and when I start up Konq it loads a ton of stuff.. true enough. But when I quit... within 10 seconds everything KDE is gone. The main thing is kdeinit and that disappears in about 10 seconds.
Color me curious, but if you're short on time why rewrite the app in perl? For readability?:)
Because after coding in PHP for a while I have discovered that
I don't need two scripting languages
I like Perl's OO MUCH better
I feel that Perl is more powerful
Good going for getting all that working. The only thing i'm not sure about is the inability to edit entries? if i have that correct.
Yes that's correct; if you need to make a correction that is one thing (spelling,/usr/local/bin instead of/usr/bin, etc.) but the idea of not allowing edits is to build up a base of "what not to do."
i.e. if you say in an article that "rm -rf / is the best way to ensure security" and then want to change it to read "Actually a good security model is to run a kernel with a nonexec stack, don't install programs you don't know and be vigilant" then the system should instead add another article, marking the first one as supersceeded and (in another table) link up the superceeded article to the newer one. That way when I come along and i search for "linux security" It will pull up the new entry first but have a link to the "prior knowledge" at the bottom. That way I can't take a step back but I know that someone else did and that it didn't work.
It'll come along. I would like to have the system automatically determine if an edit should be a new article or simply a revision. Something along the lines of a character-granularity diff; if more than x characters in a row over y lines have changed, it's a new entry, otherwise it's just an edit.
I will have to check out amaya though; I had not heard of it (or rather I had but didn't take a look).
Carefully remove the shield on the optical fibre and put a light detecting device to read the traffic.
The very thing that makes fiber work (Total Internal Reflection (Refraction? I can never keep it straight)) prevents you from doing this. In order to see the light you must make some of it escape by bending the fiber such that some of the light escapes but not all of it, or else the remote end will detect the loss of signal.
Even with the fiber bent the remote end will see some loss of signal but should compensate without problem. Now if I were the NSA I'd make sure I could get away with very little bending so that hardly any loss would be detected, and simply rely on my advanced hardware to boost a very weak signal.
I've created my own KB already: http://www.mixdown.org/kb. This was done quite a while ago in PHP as a learning lesson and I've been itching for quite some time to finish it up. Three kids, a full time job and a couple of contract jobs make time scarce though.:-)
What the vision is:
Full text entry (including accepting HTML and code)
Adding graphics to the entries
auto-keywording (basically eliminate all common words and phrases, the rest is keywords)
manual keywording
auto-rating (searches turn up entries, if the user clicks on the entry the link between the keywords used in the search and the entry retrieved is nudged up so that entry will rate higher next time)
admin and peer rating - the traditional "was this useful to you?" type of rating
supersceeding of entries - you can't eliminate an entry. If you want to make a change you can change it but the original entry is kept and marked as "supersceeded". Searches turn up the new entry but link to the old one as well. That way you build up not only knowledge but also "how not to do it" knowledge which is very important.
Entry linking - Kind of like E2 but with a datastore a little more connected.:-)
I've got the text entry and bits and pieces of the keywording and rating working. I'll be redoing it in Perl and finishing it up When I Get Time<tm> -- the current source is available to anyone if they want. As you can see if you go and look, I use it as a place to store things I have learned the hard way or found interesting and know I won't be able to find again.
This isn't directly related to business KBs but I figure this type of system would work most excellently in a customer-service and engineering environment.
Re:Astroturfers now define slashdot content
on
Mundie Responds
·
· Score: 1
This is not the first time the editors of slashdot have admitted to posting stories with no redeeming value beyond the fact that they've been submitted repeatedly and they can no longer be bothered to send off rejections.
Send off rejections? I haven't had a message stating why any of my rejected stores have been rejected at all! How do I get to someone who tells me why instead of just "rejected"?
I think the fact that the submission queue is totally hidden just aggravates this "everyone posting the same story" crap. K5's system is pretty decent in this regard.
long distance power transmission as dc sucks. that is the main advantage of ac.
This sounds familliar. I encourage you to take a look at my comment to sig11 on K5. He said the exact same thing and it's dead wrong.
Aw hell I'll just copy and paste the whole thing here. It's my comment, anyway.:-)
Here is a link to an HVDC chapter in a power electronics course at the University of Missouri. In short: HVDC economically cheaper than HVAC when it comes to long distance transmission and, as a direct quote from that introductory page claims: With an HVDC system, the power flow can be controlled rapidly and accurately as to both the power level and the direction. This possibility is often usedin order to improve the performance and efficiency of the connected AC networks.
Now as I'd said in my first post and is backed up by the tutorial in the link above: DC transmission does not suffer reactive losses. Over large distances these losses can and do build up to become a large factor in your loss calculations. Also, unlike alternating current, DC will flow through the entire conductor instead of along the outer surface.
Now while I have not investigated the actual depth that 60Hz AC penetrates aluminum wire I do know that it is small enough that the high tension lines are specially made to take advantage of this. High tension cable has a steel core and then an aluminum outer layer to minimize the transmission losses and maximize cable strength. I'm not sure what they use for DC links but I imagine they will use solid aluminum wire and space the towers closer together. I'm not sure on this.
Furthermore, your claim that Tesla proved DC to be inferior at long distance transmission in the 19th century is only partially true. AC is more efficient for conversion and short-haul transmission: it's ability to be almost perfectly stepped up and down is wonderful and the AC motor is almost a 100% (98% efficient motors are sold every day) efficient electrical to rotating mechanical convertor. However as this link shows, Tesla also did recognize that DC was more efficient for long distance power transmission.
Lastly I refer you to this document from Siemens. (the txt version from google which also includes my search terms for this whole post is here.) It talks about the advances being made to move towards medium voltage (1200V-13kV) DC transmission since the advantages of DC power transmission for high voltage systems are so well proven.
Now that that's out of the way: you've emailled me on more than one occasion asking about information on electronics and electricity in general and where to learn more. I find it mildly amusing that you jump up claiming to have enough knowledge to scream at the top of your lungs that what you know is 100% true and proven and that what I had suggested was totally and wholly false. I didn't reply to bitchslap you but I do wonder why you did try to do it to me?
So they gave us the DLL with the offending code. I've not looked to see how big the DLL is but wouldn't it be pretty straightforward to locate the backdoor password now?
1) I walked into this store one day. They were clearly open for business. As I walked around I passed through an open door. Not long after it occurred to me that this place looked like a back room, not a display room.
2) I walked up to my friends house the other day. The front gate was open, which is normal, so I could walk up to his door and knock. I looked to my left, and lo and behold his garage door was open. Even without going inside I could see all sorts of stuff, including the bodies hanging from the rafters.
I do believe that in both of these cases you would not be arrested or, if you were, you would be let off quickly because there were no grounds. Want to try some better examples?
A coder knowing the context is a bad thing. His context ends at the public interface and if he needs more information then something is wrong with the design. If he knows more than the public interface spec then he is likely to use that information (consciously or not) and make assumptions about the environment in which his code will run. In the long run, those assumptions will turn out to be wrong and his code will break.
I disagree with this in the sense that, as a systems designer and a programmer (embedded systems), it pays for the coder in me to know what the system is to do as well as what the customer wants for the future. Nothing is worse than blindly following spec and having the customer say "I'd like it to be able to do x" after he sees it and having the codebase set up in such a way that it would be difficult to do. I suppose that is why I am very active in the specification design in the first place so I can try to see the future of the project and communicate my ideas and possibilities for future-proofing the desired system.
Modular programming helps this immensely but in my professional opinion having a programmer who's making code to meet "just a bit more" than the bare spec is essential. Of course, that "just a bit more" is very hard to quantify.
The most productive environment I ever worked thought about the problem and listed the functions that were likely to be useful in creating the application (we were coding in C).
Once the specific functions were identified, it was considered if they weren't instances of more generic functions. If so, then the generic function was substituted as a requirement.
I too am a big fan of this type of design or "software design/flow specification" -- it's created from the spec, usually started before the main specification is completed so that the two can be juggled back and forth in order to create a robust system.
Think top down then code bottom up, don't make assumptions about contexts, pass everything explicitly, test continuously (especially unit test - consider making it the last step make does when compiling), use good tools like make, RCS/CVS, ar, or whatever analogues apply in your environment.
Again, I agree totally. Your description of small functions with well defined entry and exits (and data dependencies too) makes it very easy to test rigorously. And in time you build up a very impressive general library of functions for future products. I think this is where I start to come apart from XP - modularity and making functions generic enough to be reused instead of recreated all the time. That, and programming pairs would bug me.
When I program I get into a very peculiar frame of mind -- part of my head as the top-down overview of the entire system and the other part is actually laying down code. The top-down (I call it the angellic point of view) part of my brain keeps the functions' use in mind and guides how the functions themselves are written. Having someone stand over my shoulder and ask questions would drive me insane.
I'd love to have 40 hour work weeks, get overtime for any time over my 8 hour day. Time and a half for saturdays, double time for sundays, and double time and a half for vacation days that I am forced to work (and triple time for anything over 8 hours on that forced work day on a holiday).
Then why the hell don't you negotiate that yourself? Are you that weak-willed or are you that incompetent? Where I work you'd be at the bottom of the food chain just because you are too cowardly to stand up and say what you want, instead hiding behind some union rep.
Grow some balls already; if you are that easily replaced then go to a union shop, pay yer dues and learn on the side so that you can negotiate your own terms with confidence.
Christ. "I'd love to this... I'd love to that... but I'm too scared to ask! Someone please take my money to do it for me?
This may be very convenient when powering your computer from solar cells, but unfortunately these -48V supplies tend to be very expensive:-(.
No more expensive than four 12V car batteries at whatever rated current you want...:-)
In fact, I believe this is exactly what the telcos tend to use. At least at our one POP we have some equipment run off of the 48VDC supply. (I just call it 48VDC, they (telcos) reference things backwards in my eyes. If anyone can explain why I'd love to know just for knowledge sake.) -- Anyway, the supply is a bunch of deep-cycle lead-acid batteries very similar to the marine-style batteries you buy for a boat with some float charge circuitry and DC breaker distribution panel.
The actual telco racks (what the OC3 is bolted to and Bell has a hissy fit if you poke around) use smaller batteries since they're only powering their own equipment, while the POP is actually providing enough juice to power whoever hooks up to it.
Also I do have kids, and funny thing is I can let them have access to the VHS tapes. They seem to stand up to standard kid wear. DVD's are a no-no. They can't pass the 6 year old test.
Totally agree here -- all of my wife's Disney collection is VHS for this specific reason: My three kids (well only one has the ability now) can grab a movie, pop it in and go to town. It's also why Fisher-Price hasn't come out with the sing-along CD box yet -- CDs and DVDs are just too susceptable to scratching.
However I do feel that in 10 years' time, my DVDs will be perfectly watchable, while my VHS tapes will be fading and generally crappy to watch.
This so called "durable media" isn't... when compared to VHS. Yes, virginis, this MORE FRAGILE MEDIA has a far greater NEED FOR CONSUMERS TO BE ABLE TO BACK UP.
I would debate that point. Magnetic media is far more fragile when presented with extreme heat and magnetic fields... things that consumers don't even think about.
Optically, DVDs are far more vulnerable, this is true. But causing damage to the surface of the disc is something which (IMO) happens on purpose -- scratching the disc, dropping it, letting the 3 year old get at it...
I'd also like to see some proof (press release?) that shows that Blockbuster only gets an average of ten rentals out of a disc. I know our little hometown movie store gets hundreds if not thousands of rentals on their DVD media without issue.
erhaps I don't fully understand this invention, but to me it sure looks like snake oil.
You don't understand the technology.
Check out the Ultra WideBand Working Group, time domain (mentioned in the article) and dozens of other sites. The pulses are what makes this thing work and the spectral splattering is exactly intended. They're trying to get FCC approval since it doesn't cause (enough) harmful interference to take down communications with existing equipment.
It's way cool stuff. Check the UWB link provided; they want to use this for positioning, through-wall "radar" and communications. It has very serious potential. If I can find the EDN issue which gave an in-depth study of this I'll post back.
I prefer to grab the.tar.gz or bz2 of the source and compile it myself. No incompatibilities yet.:-)
So long as I know whbat the package requirements are I have had no trouble installing quite a few RedHat (ick).RPMs. Even Win4Lin went in without a hitch. It's just a matter of reading the documentation. Needs PAM, glibc2.2, bash2.17. no problem. Sometimes there's some path altering and whatnot but it's generally not a problem.
Howso? I took it that the views expressed by Newton were better than Mundie. "To stink up a room" in this context often referrs to poor performance, not olfactory sense.
I don't know about you, but Mundie's performance did stink.
I too am from Canada. I usually work from 9-5:30ish (1/2hr lunch officially but I usually have 3/4-1hr). Work starts at 8 but I haven't been in on time for ages. I suppose that's about 40 hour weeks for me.
I also do contracting (electronic design, systems design) on my own time but that is usually only 10 hours a week (20 if I'm really busy). So now that's up to 50-ish hours, peaking at 60-65.
My day job is really good and I have a lot of fun with it, but that also means I tend to think about work even when I'm not working. New ideas come at any time (I'm in development) and solutions to problems come whenever as well. It's difficult to track that time.
Of course, a wife and three kids under 5 years of age really limits how much time you want to spend on work and indeed limits how much physical strength you have to get things done. About once or twice a year I do feel myself starting to burn out and I scale back everything. I try to go down to 7 hours a day at work and maybe 5 hours a week on my contracting. It seems to self-regulate pretty well but there are plenty of times I wish for the 36-hour day.:-)
For starters, it has a reflective screen so (unlike my palm)
What the hell are you talking about? The palm screen is transflective* which means that the backlight transmits through the back (sides) of the screen but daylight reflects off the back reflector just like your watch or calculator.
I don't know about you but my Palm screen looks best in bright sunlight.
* - Unless you're using a IIIc, in which case all bets are off. I'm not sure of the IIIc screen technology but hey're fugly, even with the backlight in a dark room. Reminds me of the old colour CGA screens, all "sparkly" and stuff.
Yes of course; I thought in terms of individual wires and wrote pair. duh.:-)
You'll connect the transmit pair on one end to the receive pair on the other, and vice versa.
Check.
The thing that you are missing is that one end needs to provide clocking for the other. Be default, they expect the telco to provide the clock on the line.
Yeah... The problem with these Adtran HTU-Rs has no option to generate clock. I guess that's why they have the HTU-C.
I'm not sure which Adtran box you are using, is it a normal csu/dsu? The cable lenght settings you are talking about are for LBO, the distance between the telco mounting and your CSU.
The cablelength options were just off of one of my Cisco AS5248; it's an access server with a couple of internal CSUs. I'd have to hook up the Adtran units to see what they have again.:-)
Thanks for the info, I'll take another look and see if I can't somehow convince one of these remote ends to generate clock. Thanks for the info.
Can't you serially connect the T-1 thru a PC ? I have seen old serial connectors for T-1's but I've never used one so I dunno if this will actually work...
Are you talking about V.35? It's just a high speed synchronous serial port and pretty much a standard for WAN; Offhand I don't recall how fast it can go but it's damn fast and the damn connectors are expensive as hell.:-)
Slashdot Mirror
Of course, the Linux server can add up as a firewall/internet gateway! What more would a small company want?
How about security?
Having your main fileserver double as a firewall is a Bad Idea. Throw a little 386DX33 and a pair of NICs up to handle your modem or DSL line. I'm not certain if a 386 can handle a full T1 (I know a P75 can fill the pipe without problem) but the message is the same: Firewalls work best when they also aren't full of doors, windows and conduit holes. Keep the network firewall seperate.
It's made for lefties.
No it's not... I would rather type with my left hand and write or mouse with my right than the other way around.
While I suspect they claim it's ambidextrous (or dextrous-neutral) it is most definately suited for right-handed people.
A photocopy repair person arrived in a white shirt and proceded to get toner all over it. When asked why he doesn't wear a black shirt he tells us that management won't allow it, they think it makes their repair-people look like gangsters.
Actually the photocopy repair dude was here today (Canon) -- he wears a black golf shirt with the company logo on it and a pair of beige pants. <looking down> hmmm... kind of like what I'm wearing, only I'm in R&D and I don't design photocopiers.
But that's the whole problem. You can't just say "I think I'll just use konqueror". Just doing a ps after you start up konqueror proves that. And then you could say "but when I close it, all that's gone again", but that isn't true either. Run _one_ KDE application, and immediately you have cruft sticking to your system. It might all serve it's purpose while the app is running. But when I close the app, and revert to my trusted Windowmaker, I want all of KDE's stuff to get outta there. And it doesn't do that.
Care to prove it? I am running WindowMaker as my WM and KDE2.1.1 with kdelib 2.1.2 (security/bug fix) and when I start up Konq it loads a ton of stuff.. true enough. But when I quit... within 10 seconds everything KDE is gone. The main thing is kdeinit and that disappears in about 10 seconds.
Take your FUD elsewhere.
Color me curious, but if you're short on time why rewrite the app in perl? For readability? :)
Because after coding in PHP for a while I have discovered that
Good going for getting all that working. The only thing i'm not sure about is the inability to edit entries? if i have that correct.
Yes that's correct; if you need to make a correction that is one thing (spelling, /usr/local/bin instead of /usr/bin, etc.) but the idea of not allowing edits is to build up a base of "what not to do."
It'll come along. I would like to have the system automatically determine if an edit should be a new article or simply a revision. Something along the lines of a character-granularity diff; if more than x characters in a row over y lines have changed, it's a new entry, otherwise it's just an edit.
I will have to check out amaya though; I had not heard of it (or rather I had but didn't take a look).
Carefully remove the shield on the optical fibre and put a light detecting device to read the traffic.
The very thing that makes fiber work (Total Internal Reflection (Refraction? I can never keep it straight)) prevents you from doing this. In order to see the light you must make some of it escape by bending the fiber such that some of the light escapes but not all of it, or else the remote end will detect the loss of signal.
Even with the fiber bent the remote end will see some loss of signal but should compensate without problem. Now if I were the NSA I'd make sure I could get away with very little bending so that hardly any loss would be detected, and simply rely on my advanced hardware to boost a very weak signal.
I've created my own KB already: http://www.mixdown.org/kb. This was done quite a while ago in PHP as a learning lesson and I've been itching for quite some time to finish it up. Three kids, a full time job and a couple of contract jobs make time scarce though. :-)
What the vision is:
I've got the text entry and bits and pieces of the keywording and rating working. I'll be redoing it in Perl and finishing it up When I Get Time<tm> -- the current source is available to anyone if they want. As you can see if you go and look, I use it as a place to store things I have learned the hard way or found interesting and know I won't be able to find again.
This isn't directly related to business KBs but I figure this type of system would work most excellently in a customer-service and engineering environment.
This is not the first time the editors of slashdot have admitted to posting stories with no redeeming value beyond the fact that they've been submitted repeatedly and they can no longer be bothered to send off rejections.
Send off rejections? I haven't had a message stating why any of my rejected stores have been rejected at all! How do I get to someone who tells me why instead of just "rejected"?
I think the fact that the submission queue is totally hidden just aggravates this "everyone posting the same story" crap. K5's system is pretty decent in this regard.
long distance power transmission as dc sucks. that is the main advantage of ac.
This sounds familliar. I encourage you to take a look at my comment to sig11 on K5. He said the exact same thing and it's dead wrong.
Aw hell I'll just copy and paste the whole thing here. It's my comment, anyway. :-)
Here is a link to an HVDC chapter in a power electronics course at the University of Missouri. In short: HVDC economically cheaper than HVAC when it comes to long distance transmission and, as a direct quote from that introductory page claims: With an HVDC system, the power flow can be controlled rapidly and accurately as to both the power level and the direction. This possibility is often usedin order to improve the performance and efficiency of the connected AC networks.
Now as I'd said in my first post and is backed up by the tutorial in the link above: DC transmission does not suffer reactive losses. Over large distances these losses can and do build up to become a large factor in your loss calculations. Also, unlike alternating current, DC will flow through the entire conductor instead of along the outer surface.
Now while I have not investigated the actual depth that 60Hz AC penetrates aluminum wire I do know that it is small enough that the high tension lines are specially made to take advantage of this. High tension cable has a steel core and then an aluminum outer layer to minimize the transmission losses and maximize cable strength. I'm not sure what they use for DC links but I imagine they will use solid aluminum wire and space the towers closer together. I'm not sure on this.
Furthermore, your claim that Tesla proved DC to be inferior at long distance transmission in the 19th century is only partially true. AC is more efficient for conversion and short-haul transmission: it's ability to be almost perfectly stepped up and down is wonderful and the AC motor is almost a 100% (98% efficient motors are sold every day) efficient electrical to rotating mechanical convertor. However as this link shows, Tesla also did recognize that DC was more efficient for long distance power transmission.
Lastly I refer you to this document from Siemens. (the txt version from google which also includes my search terms for this whole post is here.) It talks about the advances being made to move towards medium voltage (1200V-13kV) DC transmission since the advantages of DC power transmission for high voltage systems are so well proven.
Now that that's out of the way: you've emailled me on more than one occasion asking about information on electronics and electricity in general and where to learn more. I find it mildly amusing that you jump up claiming to have enough knowledge to scream at the top of your lungs that what you know is 100% true and proven and that what I had suggested was totally and wholly false. I didn't reply to bitchslap you but I do wonder why you did try to do it to me?
So they gave us the DLL with the offending code. I've not looked to see how big the DLL is but wouldn't it be pretty straightforward to locate the backdoor password now?
1) I walked into this store one day. They were clearly open for business. As I walked around I passed through an open door. Not long after it occurred to me that this place looked like a back room, not a display room.
2) I walked up to my friends house the other day. The front gate was open, which is normal, so I could walk up to his door and knock. I looked to my left, and lo and behold his garage door was open. Even without going inside I could see all sorts of stuff, including the bodies hanging from the rafters.
I do believe that in both of these cases you would not be arrested or, if you were, you would be let off quickly because there were no grounds. Want to try some better examples?
A coder knowing the context is a bad thing. His context ends at the public interface and if he needs more information then something is wrong with the design. If he knows more than the public interface spec then he is likely to use that information (consciously or not) and make assumptions about the environment in which his code will run. In the long run, those assumptions will turn out to be wrong and his code will break.
I disagree with this in the sense that, as a systems designer and a programmer (embedded systems), it pays for the coder in me to know what the system is to do as well as what the customer wants for the future. Nothing is worse than blindly following spec and having the customer say "I'd like it to be able to do x" after he sees it and having the codebase set up in such a way that it would be difficult to do. I suppose that is why I am very active in the specification design in the first place so I can try to see the future of the project and communicate my ideas and possibilities for future-proofing the desired system.
Modular programming helps this immensely but in my professional opinion having a programmer who's making code to meet "just a bit more" than the bare spec is essential. Of course, that "just a bit more" is very hard to quantify.
The most productive environment I ever worked thought about the problem and listed the functions that were likely to be useful in creating the application (we were coding in C).
Once the specific functions were identified, it was considered if they weren't instances of more generic functions. If so, then the generic function was substituted as a requirement.
I too am a big fan of this type of design or "software design/flow specification" -- it's created from the spec, usually started before the main specification is completed so that the two can be juggled back and forth in order to create a robust system.
Think top down then code bottom up, don't make assumptions about contexts, pass everything explicitly, test continuously (especially unit test - consider making it the last step make does when compiling), use good tools like make, RCS/CVS, ar, or whatever analogues apply in your environment.
Again, I agree totally. Your description of small functions with well defined entry and exits (and data dependencies too) makes it very easy to test rigorously. And in time you build up a very impressive general library of functions for future products. I think this is where I start to come apart from XP - modularity and making functions generic enough to be reused instead of recreated all the time. That, and programming pairs would bug me.
When I program I get into a very peculiar frame of mind -- part of my head as the top-down overview of the entire system and the other part is actually laying down code. The top-down (I call it the angellic point of view) part of my brain keeps the functions' use in mind and guides how the functions themselves are written. Having someone stand over my shoulder and ask questions would drive me insane.
I'd love to have 40 hour work weeks, get overtime for any time over my 8 hour day. Time and a half for saturdays, double time for sundays, and double time and a half for vacation days that I am forced to work (and triple time for anything over 8 hours on that forced work day on a holiday).
Then why the hell don't you negotiate that yourself? Are you that weak-willed or are you that incompetent? Where I work you'd be at the bottom of the food chain just because you are too cowardly to stand up and say what you want, instead hiding behind some union rep.
Grow some balls already; if you are that easily replaced then go to a union shop, pay yer dues and learn on the side so that you can negotiate your own terms with confidence.
Christ. "I'd love to this... I'd love to that... but I'm too scared to ask! Someone please take my money to do it for me?
Debian definately is the only one with FREE automatic upgrading.
Now see that's a feature I'd be willing to pay for. Debian has a great service contract option with the automatic updates.
This may be very convenient when powering your computer from solar cells, but unfortunately these -48V supplies tend to be very expensive :-(.
No more expensive than four 12V car batteries at whatever rated current you want... :-)
In fact, I believe this is exactly what the telcos tend to use. At least at our one POP we have some equipment run off of the 48VDC supply. (I just call it 48VDC, they (telcos) reference things backwards in my eyes. If anyone can explain why I'd love to know just for knowledge sake.) -- Anyway, the supply is a bunch of deep-cycle lead-acid batteries very similar to the marine-style batteries you buy for a boat with some float charge circuitry and DC breaker distribution panel.
The actual telco racks (what the OC3 is bolted to and Bell has a hissy fit if you poke around) use smaller batteries since they're only powering their own equipment, while the POP is actually providing enough juice to power whoever hooks up to it.
Also I do have kids, and funny thing is I can let them have access to the VHS tapes. They seem to stand up to standard kid wear. DVD's are a no-no. They can't pass the 6 year old test.
Totally agree here -- all of my wife's Disney collection is VHS for this specific reason: My three kids (well only one has the ability now) can grab a movie, pop it in and go to town. It's also why Fisher-Price hasn't come out with the sing-along CD box yet -- CDs and DVDs are just too susceptable to scratching.
However I do feel that in 10 years' time, my DVDs will be perfectly watchable, while my VHS tapes will be fading and generally crappy to watch.
This so called "durable media" isn't... when compared to VHS. Yes, virginis, this MORE FRAGILE MEDIA has a far greater NEED FOR CONSUMERS TO BE ABLE TO BACK UP.
I would debate that point. Magnetic media is far more fragile when presented with extreme heat and magnetic fields... things that consumers don't even think about.
Optically, DVDs are far more vulnerable, this is true. But causing damage to the surface of the disc is something which (IMO) happens on purpose -- scratching the disc, dropping it, letting the 3 year old get at it...
I'd also like to see some proof (press release?) that shows that Blockbuster only gets an average of ten rentals out of a disc. I know our little hometown movie store gets hundreds if not thousands of rentals on their DVD media without issue.
erhaps I don't fully understand this invention, but to me it sure looks like snake oil.
You don't understand the technology.
Check out the Ultra WideBand Working Group, time domain (mentioned in the article) and dozens of other sites. The pulses are what makes this thing work and the spectral splattering is exactly intended. They're trying to get FCC approval since it doesn't cause (enough) harmful interference to take down communications with existing equipment.
It's way cool stuff. Check the UWB link provided; they want to use this for positioning, through-wall "radar" and communications. It has very serious potential. If I can find the EDN issue which gave an in-depth study of this I'll post back.
I prefer to grab the .tar.gz or bz2 of the source and compile it myself. No incompatibilities yet. :-)
So long as I know whbat the package requirements are I have had no trouble installing quite a few RedHat (ick) .RPMs. Even Win4Lin went in without a hitch. It's just a matter of reading the documentation. Needs PAM, glibc2.2, bash2.17. no problem. Sometimes there's some path altering and whatnot but it's generally not a problem.
This is a rather personal attack.
Howso? I took it that the views expressed by Newton were better than Mundie. "To stink up a room" in this context often referrs to poor performance, not olfactory sense.
I don't know about you, but Mundie's performance did stink.
I too am from Canada. I usually work from 9-5:30ish (1/2hr lunch officially but I usually have 3/4-1hr). Work starts at 8 but I haven't been in on time for ages. I suppose that's about 40 hour weeks for me.
I also do contracting (electronic design, systems design) on my own time but that is usually only 10 hours a week (20 if I'm really busy). So now that's up to 50-ish hours, peaking at 60-65.
My day job is really good and I have a lot of fun with it, but that also means I tend to think about work even when I'm not working. New ideas come at any time (I'm in development) and solutions to problems come whenever as well. It's difficult to track that time.
Of course, a wife and three kids under 5 years of age really limits how much time you want to spend on work and indeed limits how much physical strength you have to get things done. About once or twice a year I do feel myself starting to burn out and I scale back everything. I try to go down to 7 hours a day at work and maybe 5 hours a week on my contracting. It seems to self-regulate pretty well but there are plenty of times I wish for the 36-hour day. :-)
Now I can keep doing it even if I'll go blind! Mom can't stop me now!
For starters, it has a reflective screen so (unlike my palm)
What the hell are you talking about? The palm screen is transflective* which means that the backlight transmits through the back (sides) of the screen but daylight reflects off the back reflector just like your watch or calculator.
I don't know about you but my Palm screen looks best in bright sunlight.
* - Unless you're using a IIIc, in which case all bets are off. I'm not sure of the IIIc screen technology but hey're fugly, even with the backlight in a dark room. Reminds me of the old colour CGA screens, all "sparkly" and stuff.
There are four wires in a T1, not four pair.
Yes of course; I thought in terms of individual wires and wrote pair. duh. :-)
You'll connect the transmit pair on one end to the receive pair on the other, and vice versa.
Check.
The thing that you are missing is that one end needs to provide clocking for the other. Be default, they expect the telco to provide the clock on the line.
Yeah... The problem with these Adtran HTU-Rs has no option to generate clock. I guess that's why they have the HTU-C.
I'm not sure which Adtran box you are using, is it a normal csu/dsu? The cable lenght settings you are talking about are for LBO, the distance between the telco mounting and your CSU.
The cablelength options were just off of one of my Cisco AS5248; it's an access server with a couple of internal CSUs. I'd have to hook up the Adtran units to see what they have again. :-)
Thanks for the info, I'll take another look and see if I can't somehow convince one of these remote ends to generate clock. Thanks for the info.
Can't you serially connect the T-1 thru a PC ? I have seen old serial connectors for T-1's but I've never used one so I dunno if this will actually work...
Are you talking about V.35? It's just a high speed synchronous serial port and pretty much a standard for WAN; Offhand I don't recall how fast it can go but it's damn fast and the damn connectors are expensive as hell. :-)