SCOTT BACULA: We want to, we're out there peacefully exploring.
MARK: Picking up litter as you go?
SCOTT: Exactly.
How soon they forget Quark, the sci fi comedy about space garbage collectors.
Commander Quark, Ficus the science officer, (the male/female one), Andy the Android, and of course, the two Bettys!
The blond isn't very attractive, and she looks like she's smiling under gunpoint (aka not happy).
These are just my opinions, and if you disagree, you're just plain wrong.
Apparently, only where it counts. Uncle Floyd was a local tv show on a UHF station in NJ, and NBC bought the rights to the show. Silly little show, cheesy production quality, lotta in-jokes, and generally fun. SNL used to rip their stuff off on occasion, but that stopped soon after the show moved.
Uncle Floyd did a great parody of Joe Franklin, and apparently waited until NBC began broadcasting the show before he sued. NBC caved, and the show was soon off the air.
All software can be compromised if you've got the time and effort. But that's not what Bastille is about.
Bastille does you a favor, and asks you if you need certain services or not. Most people don't, and Bastille will turn them off for you. Also, once you've done it, you can duplicate the behavior across your new server farm, saving you Boatloads of time and effort.
Think of it as being the software to lock down your servers by reducing fluff in an easy fashion.
Yes, coders should be "better" and yes, linux providers should be better with coming up with more secure distros, but since they don't, what's the harm in using something that does? For now, Bastille is it.
My one gripe here is that what if you don't want X anywhere near your machine? I guess you're stuck with the clunky curses interface. (eh, well it's really not THAT bad).
He held his staff up at arms length, with the top leaning away, no?
In our D&D games, there was a figure of a Doppleganger in native form that we used to call "The Brain" because of the way I painted it's head pinkish. It would often end up being the last opponent to die...
I can prove that these probes are being affected by the Frisbee Force, which pulls frisbees onto rooftops and under cars.
The only problem is, Who's building roofs and abandoning cars that far out in the Solar System?????
Computers are the most important tool
on
Telecosm
·
· Score: 1
They are not the be-all, end-all some of us would believe. Computers are more a means to the end, whatever that end may be. That's not inflammatory at all.
Apparently they didn't use computers to proofread the book. What a pity.
He creates this telecosm and dispenses with the N layers. Telecosm, Schmelecosm. Damn buzzwords.
The N layers are generally an abstraction. I never hear anyone writing code in such a model to begin with, if you discount the switch manufacturers.
Someday, Fiber will be a thing of the past.
What a brave new world we'll live in, if only people stop being stupid. Yeah right.
Are you that thick? Open your eyes, and reread. The ISP has its own servers in our data center, and I was moving MX records to point to them. Nothing at all to do with Northpoint, thankfully. All we got from Northpoint was the ATM pipe to the ISP's router.
I won't even go into (ok, I will) the NorthPoint techs who blamed us when circuits didn't work (well, the traceroute from the Internet fails at your router, so you MUST be the problem). The ISP would say to the NP tech "we corrected everything, so could you check your stuff to make sure it's ok" and the NP techs would find the mistake on their side. No, blame someone else for your screwups. It's soo much easier!
You gotta relax, man! NorthPoint screwed up, and you can't blame that on anyone else but NorthPoint. Perhaps ISPs didn't pay up, but not the one I support. Whose fault is it that NorthPoint allowed the deadbeats to continue operation? Who could have gotten collection agencies on their tails? NorthPoint? Well, they did't, let things slide, and see where it got them? Who negotiated such a crappy arrangement with Verizon? NorthPoint! Accept some responsibility, bud, finger-pointing is so declasse'.
Oh, and by the way, here it is Monday, and my co-worker who got DSL through Northpoint is still reachable, even though a majority of the ISP's circuits are dead. Shows you how much of a clue Northpoint has, or ever had.
I truly feel sorry for you, but it's NorthPoint's own fault they went under. Bad management, too much finger pointing (It was the ISPs who didn't Pay, It was Verizon who was screwing us over, blah blah blah, oy). Accept it, and let it go. Your management should have handled EVEYTHING better. If they had, you'd still be working there, right?
I support the uplink connection for a ISP that has used Northpoint, and my company hosts and manages colocated equipment for them in our data center. Thank god we do, otherwise they'd be out of business TODAY.
I've been working like crazy editing MX records for those DSL customers who had their email delivered down their DSL pipe, and setting them up on the servers we manage. At least they have an alternative. What was that deal where NorthPoint forbid their ISPs from going elsewhere when it was clear with NP's future was?
The ISP related that there was a lot of finger pointing between Northpoint and Verizon as to why they had such a high failure rate on all circuit orderss. At one point, I believe I heard 70%. That was an issue for Northpoint to solve, and from what I hear, you guys really messed up there. I've worked with this ISP for almost two years now and I know they've not introduced any of these alleged delays you mention.
Your management worked out a terrible deal for working with Verizon. From what I heard, Verizon would blow your circuit requests off by simply dropping them and having them ignored.
Sure, order processing probably took only a couple of days on your end, but when the order was placed, there was a waiting period to have both Verizon and then Northpoint come in to do their respective parts. THEN, there were the delays in having NorthPoint follow up when something didn't occur. Due diligence, my ass.
Given the nature of the business, Northpoint did not own this process, and it was clear they should. The ISP would get plenty frustrated waiting for you guys and Verizon to work out your differences in many circumstances. When things went smoothly, that was great, but when there was a problem beyond the ISP's scope, God help them.
If Northpoint had been bought out by Verizon, that would have solved a lot of these little bickerings that I heard about. I blame your management for really screwing the pooch on that one. My personal guess is that when Verizon delved deeper and deeper into how Northpoint conducted business, they ran away and never looked back.
The gang was hanging around, and one of the lackeys was browsing the internet. Tony tells him to shut off the laptop, and says something like "You know how I hate that cookie sh*t!!!"
Kudos to the writers on that one!
Gotta love the FBI Sting going on, too. Good spy stuff going on there.
Yes, ncftp works perfectly well and just keeps trying until it gets in. What's your point? I never have to wait more than 5-10 minutes to get in.
I presume that apt-get allows some form of security checking (only allow these systems/servers in, only connect to those servers for updates, etc), because otherwise you're opening up scary big security holes.
In a production environment, automatic installs are definitely something that you have to worry about (either in the planning stages, or ongoing, or both). Suppose a patch comes down that fixes error A, but breaks function B in the process.
You'd never run it in a production environment, unfettered.
I would expect apt-get has some sort of flag/check in place to allow for when updates occur. Of course, on the backend, you could have control over what files are available for the clients to grab from, too.
Just thinking out loud. Pay no attention to the person typing at the keyboard.
Slashdot Mirror
Then, they can be the nation of SealandKroft...
be friggin' correct!
..."If this is true then we have a log time to wait..." would be grammatically correct.
..."If this is true, then we have a long time..."
really should be along the lines of
One should ALWAYS follow an introductory preposition with a comma. Also, remember what words you're paraphrasing - long, not log.
Sheesh. Now that I think about it, your post makes you out to be more of a grammar half-nazi.
SCOTT BACULA: We want to, we're out there peacefully exploring.
MARK: Picking up litter as you go?
SCOTT: Exactly.
How soon they forget Quark, the sci fi comedy about space garbage collectors. Commander Quark, Ficus the science officer, (the male/female one), Andy the Android, and of course, the two Bettys!
"Back away from that keg, you BITCH!"
The blond isn't very attractive, and she looks like she's smiling under gunpoint (aka not happy). These are just my opinions, and if you disagree, you're just plain wrong .
Apparently, only where it counts. Uncle Floyd was a local tv show on a UHF station in NJ, and NBC bought the rights to the show. Silly little show, cheesy production quality, lotta in-jokes, and generally fun. SNL used to rip their stuff off on occasion, but that stopped soon after the show moved.
Uncle Floyd did a great parody of Joe Franklin, and apparently waited until NBC began broadcasting the show before he sued. NBC caved, and the show was soon off the air.
How sad.
All software can be compromised if you've got the time and effort. But that's not what Bastille is about.
Bastille does you a favor, and asks you if you need certain services or not. Most people don't, and Bastille will turn them off for you. Also, once you've done it, you can duplicate the behavior across your new server farm, saving you Boatloads of time and effort.
Think of it as being the software to lock down your servers by reducing fluff in an easy fashion.
Yes, coders should be "better" and yes, linux providers should be better with coming up with more secure distros, but since they don't, what's the harm in using something that does? For now, Bastille is it.
My one gripe here is that what if you don't want X anywhere near your machine? I guess you're stuck with the clunky curses interface. (eh, well it's really not THAT bad).
He held his staff up at arms length, with the top leaning away, no?
In our D&D games, there was a figure of a Doppleganger in native form that we used to call "The Brain" because of the way I painted it's head pinkish. It would often end up being the last opponent to die...
Konquerer requires KDE (they're mated products, like a certain WA company's).
I am turned off by the comic-booky (BAM! POW!!! OOOOOF!!!) style of kde. Personally, I believe that Gnome has a more "civilised" appearance.
Convince me I should be using KDE instead, and I'll try it, but until then, feh.
We got ourselves one heavily armed recreational vehicle!
I want my screen to be made from Chuck Heston
I can prove that these probes are being affected by the Frisbee Force, which pulls frisbees onto rooftops and under cars.
The only problem is, Who's building roofs and abandoning cars that far out in the Solar System?????They are not the be-all, end-all some of us would believe. Computers are more a means to the end, whatever that end may be. That's not inflammatory at all.
Apparently they didn't use computers to proofread the book. What a pity.
He creates this telecosm and dispenses with the N layers. Telecosm, Schmelecosm. Damn buzzwords.
The N layers are generally an abstraction. I never hear anyone writing code in such a model to begin with, if you discount the switch manufacturers.
Someday, Fiber will be a thing of the past.
What a brave new world we'll live in, if only people stop being stupid. Yeah right.
Appendix A is probably already outdated.
isn't that the right term for the Goatse man?
Nah, I heard it was a British invention. Something about Tooth Beavers and stinky gumholes.I never saw anything announcing the winner...
a trunk for Spridle and ChimChim, nor any of the cool things like the buzzsaws!
Are you that thick? Open your eyes, and reread. The ISP has its own servers in our data center, and I was moving MX records to point to them. Nothing at all to do with Northpoint, thankfully. All we got from Northpoint was the ATM pipe to the ISP's router.
I won't even go into (ok, I will) the NorthPoint techs who blamed us when circuits didn't work (well, the traceroute from the Internet fails at your router, so you MUST be the problem). The ISP would say to the NP tech "we corrected everything, so could you check your stuff to make sure it's ok" and the NP techs would find the mistake on their side. No, blame someone else for your screwups. It's soo much easier!
You gotta relax, man! NorthPoint screwed up, and you can't blame that on anyone else but NorthPoint. Perhaps ISPs didn't pay up, but not the one I support. Whose fault is it that NorthPoint allowed the deadbeats to continue operation? Who could have gotten collection agencies on their tails? NorthPoint? Well, they did't, let things slide, and see where it got them? Who negotiated such a crappy arrangement with Verizon? NorthPoint! Accept some responsibility, bud, finger-pointing is so declasse'.
Oh, and by the way, here it is Monday, and my co-worker who got DSL through Northpoint is still reachable, even though a majority of the ISP's circuits are dead. Shows you how much of a clue Northpoint has, or ever had.
I truly feel sorry for you, but it's NorthPoint's own fault they went under. Bad management, too much finger pointing (It was the ISPs who didn't Pay, It was Verizon who was screwing us over, blah blah blah, oy). Accept it, and let it go. Your management should have handled EVEYTHING better. If they had, you'd still be working there, right?
I support the uplink connection for a ISP that has used Northpoint, and my company hosts and manages colocated equipment for them in our data center. Thank god we do, otherwise they'd be out of business TODAY.
I've been working like crazy editing MX records for those DSL customers who had their email delivered down their DSL pipe, and setting them up on the servers we manage. At least they have an alternative. What was that deal where NorthPoint forbid their ISPs from going elsewhere when it was clear with NP's future was?
The ISP related that there was a lot of finger pointing between Northpoint and Verizon as to why they had such a high failure rate on all circuit orderss. At one point, I believe I heard 70%. That was an issue for Northpoint to solve, and from what I hear, you guys really messed up there. I've worked with this ISP for almost two years now and I know they've not introduced any of these alleged delays you mention.
Your management worked out a terrible deal for working with Verizon. From what I heard, Verizon would blow your circuit requests off by simply dropping them and having them ignored.
Sure, order processing probably took only a couple of days on your end, but when the order was placed, there was a waiting period to have both Verizon and then Northpoint come in to do their respective parts. THEN, there were the delays in having NorthPoint follow up when something didn't occur. Due diligence, my ass.
Given the nature of the business, Northpoint did not own this process, and it was clear they should. The ISP would get plenty frustrated waiting for you guys and Verizon to work out your differences in many circumstances. When things went smoothly, that was great, but when there was a problem beyond the ISP's scope, God help them.
If Northpoint had been bought out by Verizon, that would have solved a lot of these little bickerings that I heard about. I blame your management for really screwing the pooch on that one. My personal guess is that when Verizon delved deeper and deeper into how Northpoint conducted business, they ran away and never looked back.
Nah. Just deport 'em to Canada.
Maybe this has something to do with that phrase,
Take off, eh?
The gang was hanging around, and one of the lackeys was browsing the internet. Tony tells him to shut off the laptop, and says something like "You know how I hate that cookie sh*t!!!"
Kudos to the writers on that one!
Gotta love the FBI Sting going on, too. Good spy stuff going on there.
Yes, ncftp works perfectly well and just keeps trying until it gets in. What's your point? I never have to wait more than 5-10 minutes to get in.
I presume that apt-get allows some form of security checking (only allow these systems/servers in, only connect to those servers for updates, etc), because otherwise you're opening up scary big security holes.
In a production environment, automatic installs are definitely something that you have to worry about (either in the planning stages, or ongoing, or both). Suppose a patch comes down that fixes error A, but breaks function B in the process.
You'd never run it in a production environment, unfettered.
I would expect apt-get has some sort of flag/check in place to allow for when updates occur. Of course, on the backend, you could have control over what files are available for the clients to grab from, too.
Just thinking out loud. Pay no attention to the person typing at the keyboard.
Actually, I think we found out that
SOMEBODY SET UP US THE DNA!!!
Maybe their 4004 is screwed up?
</i>
and I haven't seen it in the stores.
Next time I'll read the interviews first
It was that 1/2 hour animated Bloom County show that aired on TV a loooong time ago.
It wasn't very good, and I love BC
Any idea where I can find a copy?