Mmm... yeah. If I could just get rid of NFS, I'd be able to open up my wifi.
Anyone know how to replicate a no_root_squash NFS environment with Samba and Linux CIFS clients? I need a Samba share to retain the uid and gid of the process that creates a file or directory, rather than setting the uid and gid to those of the CIFS user whose credentials were used to mount the share.
It sounds like they didn't have a plan at all. It seems like I was ignorant of the state of our CnC structure back then. Touche.
However, this seems to tie into my "You can't have a solid CoC that's populated by nutters" comment, even if the guy doesn't seem like that much of a nutter.
It also sounds like a plan would have been cooked post-haste. So, more topically, what do you know about the present day chain of command? (The only one that matters, really, as your comment about the present day CoC seems to have been informed by a twenty-year-old gaffe.)
Unless USB 3.0 offloads all of the protocol work from the CPU to the USB controller and attached devices, FireWire will still have its place as a relatively high-performance interconnect.
So, who was in command in 1981 when Reagan was shot? Really, I'd like to know.
I don't have the documentation that tells me this. You've mentioned an uncertain chain of command, but have not even attempted to prove that there is no documentation that defines it.
You're the one who's making baseless assertions. I'm not the one who has anything to prove in this conversation.
Anyway. We're on about having a vendor-supported multiple desktop mechanism. That's all, really. Why should we be required to install some third party software to unlock some feature that's already present and functional in the underlying system? (*cough*NTFS Junctions*cough*)
You're talking about a different sort of desktop. The "Virtual Desktop" that we're talking about could be as simple as: 0) Make N lists, each of which represents a "desktop". 1) Minimize all windows that are not in the list for the current desktop. 2) Remove taskbar entries for the affected windows. 3) Add a system tray icon (or keyboard shortcut or whatever) that allows one to switch through the N desktops. 4) Add a right-click context menu to the title bar of the active window (or a keyboard shortcut for the active window or whatever) that moves it to another "desktop" list.
How is the CoC fragile? If the top man is out of contact and presumed lost, or incapacitated, then command works its way down the chain. This is by design and is robust.
If your chain is populated by nutters, you don't stand a chance of having a rational response when they get command control, now do you?
(i.e. does not want the source code to leave *easily* the office),
I, um. Maybe you're thinking of the entire *history* of the source code? Cause any dev can (generally) burn a couple of discs containing the contents of an 'svn checkout' and carry them out of the door.
(Though dumping the entire history of a repo is possible using 'svn log' and 'svn diff', if more time consuming.)
I guess that OpenBSD doesn't have a decent package manager... Most package managers can figure out what packages are installed on a user's system, then only notify the user about updates to those installed packages. But, I suppose that *everything* is harder over in OpenBSD land.
Slashdot Mirror
I hear you saying "We have 'closed source' hardware 'cause a bunch of unethical folks own fabrication facilities."
Am I wrong here?
*grins* I was baiting the guy. I know about Ports. Gentoo's Portage was designed in its image. :D
My thanks! I stand corrected!
What distro are you running?
Mmm... yeah. If I could just get rid of NFS, I'd be able to open up my wifi.
Anyone know how to replicate a no_root_squash NFS environment with Samba and Linux CIFS clients? I need a Samba share to retain the uid and gid of the process that creates a file or directory, rather than setting the uid and gid to those of the CIFS user whose credentials were used to mount the share.
It sounds like they didn't have a plan at all. It seems like I was ignorant of the state of our CnC structure back then. Touche.
However, this seems to tie into my "You can't have a solid CoC that's populated by nutters" comment, even if the guy doesn't seem like that much of a nutter.
It also sounds like a plan would have been cooked post-haste. So, more topically, what do you know about the present day chain of command? (The only one that matters, really, as your comment about the present day CoC seems to have been informed by a twenty-year-old gaffe.)
TBH, I'd rather Apple drop the licensing fee requirement and see Firewire in more devices. Anything to get IO work out of my CPU!
*nods* LSD has this on lockdown.
Unless USB 3.0 offloads all of the protocol work from the CPU to the USB controller and attached devices, FireWire will still have its place as a relatively high-performance interconnect.
So, who was in command in 1981 when Reagan was shot? Really, I'd like to know.
I don't have the documentation that tells me this.
You've mentioned an uncertain chain of command, but have not even attempted to prove that there is no documentation that defines it.
You're the one who's making baseless assertions. I'm not the one who has anything to prove in this conversation.
Are you unable to install Intel's AHCI driver after the OS is installed?
Anyway. We're on about having a vendor-supported multiple desktop mechanism. That's all, really. Why should we be required to install some third party software to unlock some feature that's already present and functional in the underlying system? (*cough*NTFS Junctions*cough*)
Windows had virtual desktops before Linux got a GUI...
Um.
You *do* know about TWM? You know... the X11 window manager coded in the late 1980's? And before that there was UWM, coded in 1985.
RedHat 1.0 included X11 in its distro in the August 1995.
http://groups.google.com/group/comp.os.linux.announce/browse_thread/thread/3a9b67e29a9616cc/25f1a331d8f04e84
If this document is to be belived, they were releasing preview versions in the previous year:
http://www.smoogespace.com/documents/behind_the_names.html
Would you care to amend your statement?
You seem to have performed no research to arrive at your conclusion. You have no credible position. Please stop spouting your disinformation.
Whoa, whoa, whoa.
You're talking about a different sort of desktop. The "Virtual Desktop" that we're talking about could be as simple as:
0) Make N lists, each of which represents a "desktop".
1) Minimize all windows that are not in the list for the current desktop.
2) Remove taskbar entries for the affected windows.
3) Add a system tray icon (or keyboard shortcut or whatever) that allows one to switch through the N desktops.
4) Add a right-click context menu to the title bar of the active window (or a keyboard shortcut for the active window or whatever) that moves it to another "desktop" list.
You're over there gettin WAAAAY too fancy. :D
[citation needed]
*chuckles* I could write a better virtual desktop manager in Visual Basic 6.
(And I don't even know Visual Basic 6!)
Your leading questions seem to indicate that you think that you know the answer to your question.
So, who, at the time, could have responded to a Soviet nuclear strike? List your citations.
Aye. This is a good find. TSVN is pretty sweet. Hopefully, this will be, too.
How is the CoC fragile? If the top man is out of contact and presumed lost, or incapacitated, then command works its way down the chain. This is by design and is robust.
If your chain is populated by nutters, you don't stand a chance of having a rational response when they get command control, now do you?
(i.e. does not want the source code to leave *easily* the office),
I, um. Maybe you're thinking of the entire *history* of the source code? Cause any dev can (generally) burn a couple of discs containing the contents of an 'svn checkout' and carry them out of the door.
(Though dumping the entire history of a repo is possible using 'svn log' and 'svn diff', if more time consuming.)
I guess that OpenBSD doesn't have a decent package manager... Most package managers can figure out what packages are installed on a user's system, then only notify the user about updates to those installed packages. But, I suppose that *everything* is harder over in OpenBSD land.
Get a small cargo trailer.
Can't tow one? Get stronger. :D
I have a couple of 21" Viewsonic G810s. They're probably 50-70 lbs each.
So, really not that bad. I get resolutions up to 19NNx13NN (Can't remember what, exactly) and the only res that looks like shit is 640x480.
I <3 my CRTs.
Due to some quirk or other, FUS is disabled on my Windows video game machine.
(However, this video game machine has a singular purpose... playing video games. It doesn't need FUS.)
If they're running on Gentoo they do!
XD
I Fuckin' KNEW IT!