From: bashley101+et@gmail.com   
      
   Pastor Dave wrote:   
      
   >   spake thusly:   
   >> Pastor Dave wrote:   
   >>   
   >>> I highly recommend AGAINST sharing your entire C: drive! If someone does   
   >>> hack into your network, EVERYTHING is up for grabs and they can bring   
   >>> your system down! Especially since when sharing it, you're probably   
   >>> giving read & write access to the folders, right?   
   >>   
   >> Of course, why else do it?   
   >   
   > What I said, I said about your C: drive.  If you are hacked, then anyone can   
   > delete important system files and mess with your whole setup.   
      
   I know, but the machine is off most of the time, we have a wired network, and   
   the c: drive is unshared again.   
      
   >> The intent was to copy the contents of a friend's USB windows drive (her   
   >> photos) to a linux machine.  I was just using my own machine to test the   
   >> syntax, which is not necessarily all that obvious, and I have only one   
   >> drive/partition on my winmachine (aside from the HP restore partition,   
   >> which warned me that any change might destroy my ability to restore my   
   >> system -- like it would actually work anyway if I needed it!). For some   
   >> reason I couldn't share the DVD drive.  There's actually no reason to do   
   >> that, but it seemed safer than using c:\.   
   >   
   > I haven't shared a DVD drive, but what may be happening, is that it doesn't   
   > see any data there to share, if you don't have a disc in it.   
      
   I thought of that, so I put a disk in.  Given that all the machines have DVD   
   writers, there's no point in worrying about it -- sneakernet is alive and well.   
     I have enough REAL problems without paying attention to the irrelevant ones.   
      
   > As for restore working, it usually does, but not always, but I would suggest   
   > that you look into ERUNT. :)   
      
   Thanks, just downloaded it.  I haven't played with the registry since win95,   
   the last time I used windows for my main machine.  I think I only did something   
   stupid enough to require restoring the registry ONCE, which was entirely   
   enough!   
      
   >> Unsharing happened instantaneously, but when I wanted to shut the machine   
   >> down it refused.  Everything else worked, it simply refused to shut down.   
   >> Ultimately I just flipped the switch on the power strip (I hate doing   
   >> that, you never know what's going to hit the fan).  No problem this time.   
   >> I've never seen that happen before, though.   
   >   
   > That can trash data.  Make sure to run a chkdsk.   
   >   
   > Open a command prompt and type the following:   
   >   
   > chkdsk c: /f   
   >   
   > It will ask you if you want to run it the next time you boot.  Say yes and   
   > reboot.   
      
   It's running without the /f switch even as we speak.  I don't trust windows to   
   fix ANYTHING by itself.  "Giving a teenager his head is the same as giving him   
   a cabbage" has many applications beyond child-rearing...   
      
   OK it's finished.  I ran it from the 'run' menu item rather than in a CLI   
   window and went back to the linux machine.  When I checked on the winmachine it   
   was apparently finished -- the window was gone.  I assume it found nothing it   
   wanted to tell me about, but I'm doing it again in a separate window... It   
   found a few lost things, so I'm re-running with with /f.  Thanks for the   
   suggestion.   
      
   >>> Please reconsider this move, Bev.  You don't have to wait for it to go   
   >>> through all that again.  You can just "unshare" the drive and then just   
   >>> share the folders that you want shared.  In fact, if you're running XP,   
   >>> it even has a folder called "Shared Documents" that will allow you to   
   >>> keep files that you would normally keep in your "My Documents" folder in   
      
   Never touch those subdirectories.  UNCLEAN!   
      
   >>> that folder and share them across your network, while you keep that type   
   >>> of files that you don't want shared across the whole network in the "My   
   >>> Documents" folder on each machine.  You can also share certain other   
   >>> folders, like a music folder that you create, etc..   
   >>   
   >> My winmachine knows nothing about my linux machine, but I have a c:\share   
   >> directory that I use to transfer stuff back and forth.  Not that common an   
   >>  occurrence, so that system works well enough.  I have a deep distrust of   
   >> filenames with spaces and avoid using them whenever possible.  8+3 ought   
   >> to be good enough for anybody!  (Well, no, not really, long filenames are   
   >> actually useful, but I draw the line at spaces and special characters!)   
   >   
   > The spaces are not a problem.  It's just that you have to use quotes for the   
   > folder name.  But it is much easier to do it your way. :)   
      
   Easy is almost always good.  I think I'd prefer that linux not distinguish   
   between upper- and lower-case letters, but there are workarounds.   
      
   >>> The best network setup is a dedicated server and clients, rater than   
   >>> peer to peer.  But you can use a peer to peer and just use one of the   
   >>> machines as if it were a server, leaving that one on, but still using it   
   >>> if you want to.   
   >>   
   >> The winmachine uses my machine as a gateway.  Ultimately we have 7   
   >> machines in the wired network and can flip on a wireless router when we   
   >> want to tweak the laptop.  There's not a lot of commonality of function   
   >> among the machines, so the server idea isn't all that useful.  One of the   
   >> machines is a music/movie server which plugs into the TV/sound system, and   
   >> we can control that from any of the other machines.   
   >   
   > This is an issue though and with all due respect, a bad way to go.  You have   
   > to go to different machines and turn them on, to share different things and   
   > frankly, that doesn't make any sense.   
      
   Well, the more machines we have on the warmer the living room is :-)  This is   
   SoCal, we don't actually NEED heat in the winter most of the time -- I haven't   
   turned on the furnace in decades, and now I'm afraid it will explode if I try.   
     Summer is, of course, very different.   
      
   > I understand about plugging into the TV sound and so forth, but a dedicated   
   > server that does all of what you need to do for sharing purposes would be a   
   > better networking concept for you.   
      
   The music-server is the only common task we need.   
      
   > Just put a huge drive in it and if you so fancy, set it up for RAID, with   
   > drive mirroring, with hot swappable drives in drawers.  That way, if a drive   
   > fails, you can take it out while the system is running and it will   
   > automatically kick over to the other drive and you then get a replacement   
   > drive and when that comes in, you just slide it in and the RAID setup   
   > automatically starts copying the data to it (it will slow the network until   
      
   [continued in next message]   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)