...Course, my company also believes that I can be terminated for things on my personal computer at home if I connect to their VPN network and have as much as threatened to do so. Therefore I refuse to connect from my home PC, even if it is required by my job.. I tell em I will do it at 8:00 am the next morning when I get on-site...
This is just plain good security practice. Letting an unsecured PC onto your VPN isn't that different from letting that PC onto your internal network. If your employeers aren't comfortable delegating desktop security to end users, that's pretty easy to understand.
That said, if they want you to work from offsite, they should give you a mobile computer that they maintain and secure!
So you shared things with your co-workers and helped those less fortunate. This seems alot more in tune with "holiday" spirit than any of our boom-time booze-ups. If I had a job I'd be pleased and proud to participate in a clebration like that.
"The text of this line is a short phrase describing the organization to which the sender belongs, or to which the machine belongs. The intent of this line is to help identify the person posting the message, since host names are often cryptic enough to make it hard to recognize the organization by the electronic address."
Since "machine" isn't defined within the RFC, I think there's some latitude to allow Roadrunners practice.
Eh! They locked out their own curses-based linux client (as well as other third party apps that used the network) and simply told their "legit" users to download a "security update" from the kazaa website or the netowrk itself.
They have control over the sharing protocols, so they can fiddle with them as much as they like.
I was hoping this would fix problems with the board-mounted ATI Rage IIc that comes with the eTower, but in the end it was actually worse than the Mach64 server that comes with XFree86-3.3.3.1.
The setup probes your video and then tries to run XF86Setup with that server rather than the VGA16 server. Because of this I never made it through setup.
Additionally the "uninstall" that is provided leaves XFree86 in a bit of the mess - X remains slinked to the SDD server after it's been deleted.
I'll forward these bugs to SciTech, of course, but I'd love to hear from anybody who has made this card work with XFree86.
Linuc PPC Live + KDE + Dual processors = freeze?
on
LinuxPPC Live 4.0
·
· Score: 1
Admittedly, this is a LinuxPPC question more than anything, but this release is what tempted me to try the thing out.
My system: Power Mac 8500 with a dual 200 MHz processor upgrade 64 MB RAM Linux PPC Live file system on an external Jaz drive
Linux has successfully booted and KDE has completely launched.
I can run programs from the command line to my heart's content, launch additional X windows & use the keyboard to switch among them.
BUT, after a certain amount of mouse movement, KDE will freeze solid and I have to power cycle to get anywhere. (Unless there's a magic KDE server restart key sequence that I don't know.)
I've done a fair amount of work with i386 Linux and none at all with LinuxPPC or KDE. It's unclear from http://www.linuxppc.org/hardware/ whether dual processors are supported or not. It's also unclear to me whether this freeze has anything to do with that.
Additional datum: switching from a high-resolution (Mouse Systems ADB Little Mouse) to a regular Apple mouse caused the freeze to take longer to occur.
Slashdot Mirror
Speaking of tinydns: Notes on *.com wildcards .
"VeriSign did not respond requests for comment."
Isn't that what caused the problem in the first place?
Thanks, I'll be here all week!
This is just plain good security practice. Letting an unsecured PC onto your VPN isn't that different from letting that PC onto your internal network. If your employeers aren't comfortable delegating desktop security to end users, that's pretty easy to understand.
That said, if they want you to work from offsite, they should give you a mobile computer that they maintain and secure!
So you shared things with your co-workers and helped those less fortunate. This seems alot more in tune with "holiday" spirit than any of our boom-time booze-ups. If I had a job I'd be pleased and proud to participate in a clebration like that.
Here's a page on Beta Brite programming with links to some others.
regarding the optional "Organization" header:
"The text of this line is a short phrase describing the organization to which the sender belongs, or to which the machine belongs. The intent of this line is to help identify the person posting the message, since host names are often cryptic enough to make it hard to recognize the organization by the electronic address."
Since "machine" isn't defined within the RFC, I think there's some latitude to allow Roadrunners practice.
(BTW, aren't they owned by AT&T now?)
Eh! They locked out their own curses-based linux client (as well as other third party apps that used the network) and simply told their "legit" users to download a "security update" from the kazaa website or the netowrk itself.
They have control over the sharing protocols, so they can fiddle with them as much as they like.
I was hoping this would fix problems with the board-mounted ATI Rage IIc that comes with the eTower, but in the end it was actually worse than the Mach64 server that comes with XFree86-3.3.3.1.
The setup probes your video and then tries to run XF86Setup with that server rather than the VGA16 server. Because of this I never made it through setup.
Additionally the "uninstall" that is provided leaves XFree86 in a bit of the mess - X remains slinked to the SDD server after it's been deleted.
I'll forward these bugs to SciTech, of course, but I'd love to hear from anybody who has made this card work with XFree86.
Admittedly, this is a LinuxPPC question more than anything, but this release is what tempted me to try the thing out.
My system:
Power Mac 8500 with a dual 200 MHz processor upgrade
64 MB RAM
Linux PPC Live file system on an external Jaz drive
Linux has successfully booted and KDE has completely launched.
I can run programs from the command line to my heart's content, launch
additional X windows & use the keyboard to switch among them.
BUT, after a certain amount of mouse movement, KDE will freeze solid and I
have to power cycle to get anywhere. (Unless there's a magic KDE server
restart key sequence that I don't know.)
I've done a fair amount of work with i386 Linux and none at all with
LinuxPPC or KDE. It's unclear from http://www.linuxppc.org/hardware/ whether
dual processors are supported or not. It's also unclear to me whether this
freeze has anything to do with that.
Additional datum: switching from a high-resolution (Mouse Systems ADB Little
Mouse) to a regular Apple mouse caused the freeze to take longer to occur.
Anybody have any thoughts on this?