It's not the world they are worried about.
If China wanted to ruin hong-kong, nobody could stop them.
They lave hong-kong alone becuase they have no reason to change it. It works, it feeds them money... they will make slow adjustments as they get used to dealing with the place.
What if they had sent the letter to Sprint? Qwest? Any other large backbone provider?
The point is, the univeristy is only providing for routing of IP to student's rooms, PERIOD. They are not filtering ANYTHING.
If you think the university SHOULD ban napster a-la port filtering or stateful packet filtering or whatever, then where does it stop? What abou tsprint?
Remember, in theory, on the internet, all are equal. Sprint just has more bandwidth. There i snothing 'special' about what they can provide, and they have no special 'status' compared to a smaller network.
Because now is not the time.
A great many features start out as independent kernel patches.
When thigns stabilize down the road, I'm sure they will gladly put 'Big Iron' flags in the compile stuff.
The point is, linus (et al) can't just stick everyting everyone submits, big OR small, into the main kernel, especially if it's not even developed yet!
Also... the feature set for current kernels is already listed... and this isn't one of htem.
You don't just add shit to a project partway through because someone wants you to.
I'm sure than by the time 2.5 kicks up, we'll see a 'big iron' flag in main kernel options.
If 'linux' wants to be a mainstream desktop os? 'it' shouldn't fork?
This is the problem, folks.. linux isn't an 'it'. It's a plural, it's an ideology, and relatively loosely defined codebase.
We have compatability between distributions right now by *fluke* because noone has seen a need to change that. There is no 'rule' that says it has to stay this way.
If the community wants linux to be on the desktop, then THAT IS WHERE IT WILL GO. Period. Regardless of who forks what. If we need a way to distinguish between our 'community' supported stuff that runs on 'true' linux, and the forks, we will do so. It's no big deal, really.
Are you saying that they are forking it (as the headline suggests) or simply guessing that some day they may for it? Just fear mongering?
If they produce stable patches, that can compile cleanly in with everythign else, especially after the new kernel revs are done in 2.3, and 2.4 is stable, I bet they WOULD make it into the mainstream.
They simply don't add everything just because it's just starting. Lots of great features started out as separate kernel patches and eventually made it into the main tree.
And if they want to fork, what's the big deal? Who cares? They are more than free to do so, and produce their own. It's not like it would be any less open.. and heck, a third party can always glue them back together and ship his 'complete linux' or whatever...
Sun workstations support:
standard mouse
standard keyboard
standard svga monitor
PCI network card
PCI video card? (unsure)
SCSI peripherals of all kinds.
How much more 'standard' can you get?
The only thing they DON'T support is IDE.
And of course, they probably don't have support for your latest-and-gratest soudnblaster live or anything, but you don't need it. It's not a gaming platform.
Build your own? About the only thing you have to buy from Sun is the MOBO, processor, and the case (you DO want a case, no?)
Also.. where is the market for this? Companies that buy Sun don't WANT to build them themselves. Part of the reason sun is relaible is because of quality control; something you can't do if joe average is building his own high-end workstation.
And that's in an office using Ghost.
Multicast can be tailored to not smash your network, but the only reason this is fairly effective in the office is because it's not lossy;0
That would be great, if only EFnet would allow smaller servers to connect.
I know that I could responsibly run a server (ie: not abuse it, just leave it alone) and allow the 30 or 40 people that I know to connect, hassle free.
Why will EFNet not allow private servers? They only allow things that have HUGE pipes.
Simply make it a condition that a single abuse by an IRCOp on a small server is grounds for immediate and permanent detachment.
Actually, a large part of the reason there are fewer servers is becuase the admins on EFNet will not ALLOW anyone to add a server unless it is going to be extremely well connected. They don't like the 'disruptions' caused.
I know a great many people with T1 and such style links, who would GLADLY run a server and allow 50-100 people to connect. EFNet won't hear of it.
What the hell? First, I'm not at all criticizing or hating these people. Not at all. I have absolutely no issue with them being here whatsoever.
Second, I'm not American in the first place. And where my parents or grandparents came from is not relevant.
My point was one of immigration policy, and not directed at any 'race' or whatever. THe point is, a country should do everything it can to educate and get the help it needs from WITHIN before abandoning it's own people and getting help from WITHOUT.
I realize I'm starting to sound like a KKK member or something.. please uderstand I'm not talking about some kind of totalitarian idea here.. nothing like 'fuck the immigrants, bring back our country' or anything.
Just simple policy: jobs for locals before jobs for outsiders.
Disk drives do not work in 'bytes'. Low level software/hardware interpretes a constant coded stream of bits back into bytes for our convenience, as with a communication protocol.
The point, was that when you refer to, in most engineering docs I've ever read,
1 Kilobyte, that measn 1024 bytes if it's memory
and 1000 bytes if it's communication.
And it's rather up in the air for other media.
Wow. I explian that, in real life, storage capacities of hard disks and communication are usually termed in powers of ten, and that memory is in powers of two, and you sort of... flip out on me? No SHIT it's binary.
I have a VERY good idea of what I'm talking about.
For the most part, it is largely up to YOU, as an IT person, to LET the company know what to expect from you.
I don't mean you are supposed to be a BOFH to everyone... but...
DO NOT work those extra hours, unless it is really an emergency. And being in a 'continued state of emergency' is no excuse. If you can't do the ordinary day-to-day job in 8 hours, you aren't doing your job right. Server failures and disasters can be an aside.
IF THEY want or expect you to be on call, make SURE they pay extra for it. SIGNIFICANTLY extra, to discourage abusing you. If they can't or won't, make yourself unavailable.
Make certain things clear, in writing, when you are hired about hours worked, who you report to, etc. I know it's common for some manager, or VP, from some other department to come in and start 'demanding' things of the IT department. Those can usually be handled with 'can you please run that through the IT manager, or the IT Directory, or whoever?. What I've found is they will, more often than not, suddenly realize that it's not really THAT important. If it's not important enough for them to follow a simple procedure, it's not important enough for me to waste my time with. Of course, you have to use discretion. Some things really ARE emergencies.
Know who can fire you and who can't. Learn the politics of your company. Go out for lunch with your boss. I don't mean brownnose and suck up and stuff, but you have to know where you stand. Know when to say NO!
I can recall my conversation. The VP of something or other calls up and says 'I want you to do this, right now, today. It's very important.'. I say 'Sure. just call Mr. So-and-so (my boss) who's in his office RIGHT NOW, I'll even put you through, and run it by him. tell him I said I can do it immediately if he says it's okay'. "Oh.. well can't you just do it? "Sure, if you call him and explain to him why I'm disobeying his instructions not to do anything for anyone without his say-so". Catch 22. He says 'okay, it's not that important anyway'.
Get sleep, like others said. Sleep IS very important. The best way to go to bed on time is make a habit of doing your computing on weekends, and get this, IN THE MORNING. Even your personal stuff. Nothing keeps you up at night like a computer.
EXERCISE. I'm bad for this, but get exercise. It makes a HUGE difference.
Don't eat too much pasta. Use those IT skills to do up a spreadsheet of the crap you eat, and rationalize it.
Know where you are going. Always have a plan. Know why you are at the job you are at.
And most of all..
If you don't like something in life, CHANGE IT!
Slashdot Mirror
It's not the world they are worried about.
If China wanted to ruin hong-kong, nobody could stop them.
They lave hong-kong alone becuase they have no reason to change it. It works, it feeds them money... they will make slow adjustments as they get used to dealing with the place.
What if they had sent the letter to Sprint? Qwest? Any other large backbone provider?
The point is, the univeristy is only providing for routing of IP to student's rooms, PERIOD. They are not filtering ANYTHING.
If you think the university SHOULD ban napster a-la port filtering or stateful packet filtering or whatever, then where does it stop? What abou tsprint?
Remember, in theory, on the internet, all are equal. Sprint just has more bandwidth. There i snothing 'special' about what they can provide, and they have no special 'status' compared to a smaller network.
It's funny how the whole concept of internet transparency has been shot to hell now.
I mean, it used to be: If you were on the net, and you supported TCP/IP.. that was it. A software developer needed to know that, and that alone.
NOw we have: dynamic IP addressing, firewalls, intranets, transparent proxies & caches, port filtering by major ISPs (like @home), etc.
They aren't selling 'internet' anymore, they are selling 'use our network to surf'.
ISPs are charging yearly rentals for blocks of IP addresses, when it in fact costs them nothing.
It's kind of sad, really.
obscurity -vs- review isn't even an ARGUMENT with stuff like this.
If people know the exact mechanism the interception software uses, then they can figure out precisely how to get around it.
it DOES follow that if you are going to intercept something, you have to not let the other party know when and how you are going to do it.
Given that it's federal stuff... they specified that whoever was on the review team HAD to have security clearance.
And where have most people, nay, all who have clearnace worked? Well.. to have government security clearance, you have to have worked for them..
Because now is not the time.
A great many features start out as independent kernel patches.
When thigns stabilize down the road, I'm sure they will gladly put 'Big Iron' flags in the compile stuff.
The point is, linus (et al) can't just stick everyting everyone submits, big OR small, into the main kernel, especially if it's not even developed yet!
Also... the feature set for current kernels is already listed... and this isn't one of htem.
You don't just add shit to a project partway through because someone wants you to.
I'm sure than by the time 2.5 kicks up, we'll see a 'big iron' flag in main kernel options.
Solaris IS SunOS.
SunOS V4.x was based on BSD.
SunOS V5.x was based on SysV 4.x
Solaris is the name for SunOS 5 + OpenWin
If 'linux' wants to be a mainstream desktop os? 'it' shouldn't fork?
This is the problem, folks.. linux isn't an 'it'. It's a plural, it's an ideology, and relatively loosely defined codebase.
We have compatability between distributions right now by *fluke* because noone has seen a need to change that. There is no 'rule' that says it has to stay this way.
If the community wants linux to be on the desktop, then THAT IS WHERE IT WILL GO. Period. Regardless of who forks what. If we need a way to distinguish between our 'community' supported stuff that runs on 'true' linux, and the forks, we will do so. It's no big deal, really.
Are you saying that they are forking it (as the headline suggests) or simply guessing that some day they may for it? Just fear mongering?
If they produce stable patches, that can compile cleanly in with everythign else, especially after the new kernel revs are done in 2.3, and 2.4 is stable, I bet they WOULD make it into the mainstream.
They simply don't add everything just because it's just starting. Lots of great features started out as separate kernel patches and eventually made it into the main tree.
And if they want to fork, what's the big deal? Who cares? They are more than free to do so, and produce their own. It's not like it would be any less open.. and heck, a third party can always glue them back together and ship his 'complete linux' or whatever...
Sheesh. hard up for topics today?
Is it fairly hight? You have to compare it to the same platform, period.
I bet one could design a chip that was 100 times slower than your PII-450, but had a bogomips rating of 10,000.
It's a calibrated delay.. that's all.. how fast the computer can do nothing, basically. Rather meaningless as far as speed goes.
Hunh?
Standard PC hardware?
Sun workstations support:
standard mouse
standard keyboard
standard svga monitor
PCI network card
PCI video card? (unsure)
SCSI peripherals of all kinds.
How much more 'standard' can you get?
The only thing they DON'T support is IDE.
And of course, they probably don't have support for your latest-and-gratest soudnblaster live or anything, but you don't need it. It's not a gaming platform.
Build your own? About the only thing you have to buy from Sun is the MOBO, processor, and the case (you DO want a case, no?)
Also.. where is the market for this? Companies that buy Sun don't WANT to build them themselves. Part of the reason sun is relaible is because of quality control; something you can't do if joe average is building his own high-end workstation.
What page generates this postmodern tripe?
And that's in an office using Ghost. ;0
Multicast can be tailored to not smash your network, but the only reason this is fairly effective in the office is because it's not lossy
becuase with multicast, there is no flow control?
And no guaranteed delivery?
This is perfectly acceptable for media broadcast, where the codec can deal with dropped bytes.. but..
If anyone had actual hard evidence about NSA backdoors, they would either be under the control of the NSA, or they would be DEAD.
I find that too many carbs actually diminish performance, and you feel bloated ;)
Aside from all the details..
Microsoft is concerned any time ANYTHING they have that someone else doesn't is about to be released.
They don't want their file formats 'discovered'. They don't WANT anyone else to have NTFS. Otherwise, it becomes tooe asy to switch.
They don't WANT an RDP/X translator, even though there would be a HUGE market for it, because it would ease transition away from MS.
They don't WANT office on other platforms, because it would ease transition away from their OS.
That would be great, if only EFnet would allow smaller servers to connect.
I know that I could responsibly run a server (ie: not abuse it, just leave it alone) and allow the 30 or 40 people that I know to connect, hassle free.
Why will EFNet not allow private servers? They only allow things that have HUGE pipes.
Simply make it a condition that a single abuse by an IRCOp on a small server is grounds for immediate and permanent detachment.
Actually, a large part of the reason there are fewer servers is becuase the admins on EFNet will not ALLOW anyone to add a server unless it is going to be extremely well connected. They don't like the 'disruptions' caused.
I know a great many people with T1 and such style links, who would GLADLY run a server and allow 50-100 people to connect. EFNet won't hear of it.
What the hell? First, I'm not at all criticizing or hating these people. Not at all. I have absolutely no issue with them being here whatsoever.
Second, I'm not American in the first place. And where my parents or grandparents came from is not relevant.
My point was one of immigration policy, and not directed at any 'race' or whatever. THe point is, a country should do everything it can to educate and get the help it needs from WITHIN before abandoning it's own people and getting help from WITHOUT.
I realize I'm starting to sound like a KKK member or something.. please uderstand I'm not talking about some kind of totalitarian idea here.. nothing like 'fuck the immigrants, bring back our country' or anything.
Just simple policy: jobs for locals before jobs for outsiders.
My point was that
Disk drives do not work in 'bytes'. Low level software/hardware interpretes a constant coded stream of bits back into bytes for our convenience, as with a communication protocol.
The point, was that when you refer to, in most engineering docs I've ever read,
1 Kilobyte, that measn 1024 bytes if it's memory
and 1000 bytes if it's communication.
And it's rather up in the air for other media.
Wow. I explian that, in real life, storage capacities of hard disks and communication are usually termed in powers of ten, and that memory is in powers of two, and you sort of... flip out on me? No SHIT it's binary.
I have a VERY good idea of what I'm talking about.
MOS Tech. Not Mostek. Argh. Silly me.
It did have a serial port, and no, I don't hink it was the bank switch.
It wasn't rs232.. I believe the signalling was intact, but it was at ttl (or cmos) levels instead of rs232 levels, so you needed a powered converter.
Exactly.
But that's the point.
Fair use was never a specific law. It was merely an exemption from action under copyright laws.
It IS legal for you to reverse engineer and play with your DVD player. It is NOT legal, by DMCA, to publish that information.
Yes.. I hate teh DMCA, I think it's wrong.
But blanket statements like 'it keeps us from making fair use' is not good enough.
For the most part, it is largely up to YOU, as an IT person, to LET the company know what to expect from you.
I don't mean you are supposed to be a BOFH to everyone... but...
DO NOT work those extra hours, unless it is really an emergency. And being in a 'continued state of emergency' is no excuse. If you can't do the ordinary day-to-day job in 8 hours, you aren't doing your job right. Server failures and disasters can be an aside.
IF THEY want or expect you to be on call, make SURE they pay extra for it. SIGNIFICANTLY extra, to discourage abusing you. If they can't or won't, make yourself unavailable.
Make certain things clear, in writing, when you are hired about hours worked, who you report to, etc. I know it's common for some manager, or VP, from some other department to come in and start 'demanding' things of the IT department. Those can usually be handled with 'can you please run that through the IT manager, or the IT Directory, or whoever?. What I've found is they will, more often than not, suddenly realize that it's not really THAT important. If it's not important enough for them to follow a simple procedure, it's not important enough for me to waste my time with. Of course, you have to use discretion. Some things really ARE emergencies.
Know who can fire you and who can't. Learn the politics of your company. Go out for lunch with your boss. I don't mean brownnose and suck up and stuff, but you have to know where you stand. Know when to say NO!
I can recall my conversation. The VP of something or other calls up and says 'I want you to do this, right now, today. It's very important.'. I say 'Sure. just call Mr. So-and-so (my boss) who's in his office RIGHT NOW, I'll even put you through, and run it by him. tell him I said I can do it immediately if he says it's okay'. "Oh.. well can't you just do it? "Sure, if you call him and explain to him why I'm disobeying his instructions not to do anything for anyone without his say-so". Catch 22. He says 'okay, it's not that important anyway'.
Get sleep, like others said. Sleep IS very important. The best way to go to bed on time is make a habit of doing your computing on weekends, and get this, IN THE MORNING. Even your personal stuff. Nothing keeps you up at night like a computer.
EXERCISE. I'm bad for this, but get exercise. It makes a HUGE difference.
Don't eat too much pasta. Use those IT skills to do up a spreadsheet of the crap you eat, and rationalize it.
Know where you are going. Always have a plan. Know why you are at the job you are at.
And most of all..
If you don't like something in life, CHANGE IT!