Page 4 of 4 FirstFirst ... 234
Results 31 to 39 of 39

Thread: Just made a horrible horrible horrible mistake

  1. #31
    Join Date
    Jul 2008
    Location
    Seattle, WA
    Posts
    17,079

    Default Re: Just made a horrible horrible horrible mistake

    On Sun, 13 Dec 2009 20:33:18 +0000, palladium wrote:

    > hcvv wrote:
    >> "It does not do what *you think you told it* to do, it does what *you
    >> told it* to do").

    >
    > every time!


    I've explained it to people in the past that computers do exactly what
    you tell them to do. The trick is getting what you *want* them to do to
    equal what you *told* them to do.

    Jim
    --
    Jim Henderson
    openSUSE Forums Moderator

  2. #32

    Default Re: Just made a horrible horrible horrible mistake

    I wish you all the best to recover the data... But when you get your system up and running with all of your data.. mount Windows drives(where your windows is installed) as read only from Linux. Linux/Unix is very very powerful. And with more power comes more responsibility..
    --
    Vivek Bhat
    Linux User #496540
    Dell 620 S Desktop, 8GB, Intel(R) Core(TM) i5-2310 CPU @ 2.90GHz, openSuSE Leap 42.1
    +Plasma 5, Kernel 4.1.20-11-default x86_64

  3. #33
    Join Date
    Mar 2008
    Location
    San Diego (California)
    Posts
    475

    Default Re: Just made a horrible horrible horrible mistake

    Quote Originally Posted by hendersj View Post
    computers do exactly what you tell them to do.
    Except maybe Windowz, that seems to have a mind its own lol
    ~ There are 10 types of people. Those who understand binary, and those who don't. ~

  4. #34
    Join Date
    Jun 2008
    Location
    Frisco, TX
    Posts
    1,233

    Default Re: Just made a horrible horrible horrible mistake

    On Sat, 2009-12-12 at 03:06 +0000, ChrisH 16 wrote:
    > Ok, I'm trying not to hyperventilate here...
    >
    > I chdir'd to /.wine/drive_c/ and ran rm -rf on the /windows/ directory


    Well.. there's the rub. This isn't a symlink issue (they wouldn't
    be followed anyhow). The issue is that you told it to remove
    all of /windows (notice the beginning /). So it deleted everything
    in your /windows directory (which would be the mounted Windows drives,
    which we can all assume were writable).

    Sorry.. no magic bullet to recover from this...

    However, oddly enough the thing you were wanting to delete should
    be intact (/.wine/drive_c/) you can check to verify that.

    I wish I had better news...



  5. #35

    Default Re: Just made a horrible horrible horrible mistake

    Where are new Linux users, finding suggestions to use "rm -rf /windows" from? In general, I've seen "rm -rf /" explained as a simple way to destroy your system and described as a powerful command, one to respect and caution responsibility at comamndline.

    May be all the references and cautions, actually just feed the all too human failing of prefering shortcuts and quick solutions, over actually thinking something through and being patient.

    Or perhaps it's just Data Death Wish Syndrome. If the data was really important, you'ld make a proper backup copy, and not be sloppy with it, wouldn't you?

  6. #36
    palladium NNTP User

    Default Re: Just made a horrible horrible horrible mistake

    robopensuse wrote:
    > Where are new Linux users, finding suggestions to use "rm -rf /windows"
    > from? In general, I've seen "rm <snip>


    the more i think about the initial posting in this thread the more i
    think it was probably just another MS-hired troll salting the futile
    grounds....you know, adding a little FUD around in the archives..
    (for more on intentional MS FUD see http://tinyurl.com/er6ne and
    http://tinyurl.com/2478pa)

    where are new users finding the recipe for self-destruction??

    i guess maybe those are being spread mostly by ignorance (those
    impatient new users you reference who blindly copy/past) and also by
    design by Redmond Evangelists (see: http://tinyurl.com/y8ezxkl) and
    sometimes innocently by folks like us quoting the 'recipe for disaster'..

    perhaps a reasonable response would be to ask the mods/wiki keepers to
    go through the archives and fora looking for such offending, disaster
    producing commands and:

    -purge all

    -mung/change each to a 'safer' recipe, like maybe
    "rm --XX / see man rm for details"

    -or, ??

    wow, see i found it existing about 1360 times in opensuse.org--just
    waiting for new guys/gals to find and use, simple and easy: see
    http://tinyurl.com/y8wj25f

    so, ChrisH_16, if you are not a troll come back and speak:

    -we all want to know where you found the command?

    -what was the mistake you made "pertaining to several files in wine's
    windows directory" which you felt deleting *all* the files in the
    directory was the way fix the problem?

    -what were the symptoms of your difficulties with WINE, that lead you
    to believe forced deletion was the solution?

    -how long did you watch your command process before you "ran off to
    eat dinner"?

    -how new is "I'm still somewhat new to OpenSUSE"?

    -since you didn't come here until after you made this big boo-boo,
    where were you asking your questions earlier? (google finds ZERO
    posting by, about or referencing 'ChrisH_16' in the entire universe!)

    don't tell me you just appeared out of nowhere, made eight post in
    three days and disappeared again, please..

    i wish a mod would look at all of ChrisH_16's post and analyze the
    headers for IPs and posting agent...all the same? from where?

    OH wow, this thread got spread to
    http://www.linuxine.com/node/7989/related_links
    by 'bolly' who has submitted 243 'scoops' on problems arising in Linux
    in only THREE weeks [cite: http://www.linuxine.com/users/bolly]

    i sure would like to know if 'bolly' and 'ChrisH_16' post via the same
    agent and IP!!

    -oh, and last Q for 'ChrisH_16': why did you feel the need to write
    "If you think I'm trolling I'm not."

    my conclusion: http://www.youtube.com/watch?v=6bMLrA_0O5I

    --
    palladium

  7. #37

    Default Re: Just made a horrible horrible horrible mistake

    Quote Originally Posted by palladium View Post
    robopensuse wrote:
    > Where are new Linux users, finding suggestions to use "rm -rf /windows"
    > from? In general, I've seen "rm <snip>


    the more i think about the initial posting in this thread the more i
    think it was probably just another MS-hired troll salting the futile
    grounds....
    Actually it's a fairly common mistake people make at some time. There used to be an amusing "Levels of UNIX" text which would go round. It went something like this :

    #3 You have had your first bad experience with rm(1)
    #4 You learn to call vi(1) Vee-Eye, rather than "vye".
    ...
    #12 You write device drivers at terminal with cat > foo.c

    So I wouldn't doubt the genuineness of the OP, nor be unsympathetic.

    Now frankly, having to habitually confirm a dialog has never really helped me avoid mistakes. My worst were with mkfs(8) and restore(8), there's no substitute for being careful and checking things.

    A habit of making yourself type './foo' rather than just 'foo', and using longwinded 'pushd /windows; rm -rf ./C' if you need to do it, and pausing and thinking before hittinug <RETURN> is what works for me.

  8. #38
    Join Date
    Jan 2009
    Location
    USA Pennsylvania
    Posts
    1,287

    Default Re: Just made a horrible horrible horrible mistake

    Quote Originally Posted by cjcox View Post
    On Sat, 2009-12-12 at 03:06 +0000, ChrisH 16 wrote:
    > Ok, I'm trying not to hyperventilate here...
    >
    > I chdir'd to /.wine/drive_c/ and ran rm -rf on the /windows/ directory


    Well.. there's the rub. This isn't a symlink issue (they wouldn't
    be followed anyhow). The issue is that you told it to remove
    all of /windows (notice the beginning /). So it deleted everything
    in your /windows directory (which would be the mounted Windows drives,
    which we can all assume were writable).

    Sorry.. no magic bullet to recover from this...

    However, oddly enough the thing you were wanting to delete should
    be intact (/.wine/drive_c/) you can check to verify that.

    I wish I had better news...
    Notice the output from the terminal though:

    Code:
    #
    rm: cannot remove directory `/windows/C/Users/Public/Documents/My Videos': Operation not supported
    #
    rm: cannot remove directory `/windows/D': Device or resource busy
    #
    rm: cannot remove directory `/windows/E': Device or resource busy
    It says Operation not supported throughout the whole /windows/ directory. And at the end, windows D and E are both busy. So could rm have removed them without permission? And also how does rm remove the files? Is it not possible to recover them using something like testdisk?

    I'm just curious, because I worked in a hospital IT dept over summer as a summer student and when one of the computers *magically* erased data on the hard drive my Windows superiors tried slaving the hard drive and recovering data from windows. That was useless. So I tried Testdisk from the ubuntu based System Rescue CD, and was able to find the files, restore the partition, and backup the files just in case.

    *EDIT: I guess I just saw the # sign in front of the output so he was logged in as root in the terminal. But the operation not being supported still doesn't add up.

    Take Care,

    Ian
    Laptop: Dell Inspiron E1505 | OpenSUSE 12.1/Windows Vista | KDE | Intel CPU T2050 1.6 GHz | Intel 945GM | 3.2GB RAM
    Box: OpenSUSE 12.1/Windows 7 | KDE | Intel Core 2 Quad 8300 2.5GHz/core | nVidia Geforce 9500GT 1GB| 4 GB RAM

  9. #39

    Default Re: Just made a horrible horrible horrible mistake

    Quote Originally Posted by ijbreakey View Post
    Notice the output from the terminal though:

    Code:
    #
    rm: cannot remove directory `/windows/C/Users/Public/Documents/My Videos': Operation not supported
    #
    rm: cannot remove directory `/windows/D': Device or resource busy
    #
    rm: cannot remove directory `/windows/E': Device or resource busy
    It says Operation not supported throughout the whole /windows/ directory. And at the end, windows D and E are both busy. So could rm have removed them without permission?
    No root has "permission" unless the process gave up some capabilities, it might be something like leaf optimisation not working in NTFS.

    If you "rm -rf /" you tend to see quite a lot of errors when devices go, but it's often still fairly effective. IIRC losing /dev/zero would cause things to halt on some systems.

    rm(1) doesn't do anything about data, so making the filesystem ro, and making an image copy for further experiments, would likely have lead to recovery of the files, by undeletion. It sounds like you had a corrupted partition table, which has happened to me a few times. There's utility to guess partition tables, and I've used it to recover disk data few times in past, when I've forgotten to make a partition table dump with sfdisk(8) for future recovery purposes.

Page 4 of 4 FirstFirst ... 234

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •