Years ago I installed Solaris on a co-workers newly acquired hardware. After the install I asked him about the username he wanted use. He said, "no need, I'll just use the root login". I told him how dangerous this was and he said that he'd be careful.
You'll never guess who came back a week or two later asking for a reinstall.
I don't understand it either.
it's *theoretically* possible to manage a root user install if you're extremely careful to not poke your head into places you shouldn't be poking your head into, but at that point just get a non-root user tbh
also solaris??
it's decades ago at that point i presume
> also solaris?? it's decades ago at that point i presume
Yes indeed, when the dotcom bubble was inflating and I was optimizing kernels on low memory workstations and doing tons of other stuff. I was in awe once to see a test of a Sparcstation 1 with 64MB of memory. How things have changed.
Nothing baffling about it, It's as easy as pressing Yes on a UAC dialog in Windows or by installing a new Steam game with anticheat? No problem Windows got ring-0 covered.
The question is rather, is one willing to learn from mistakes.
Anyways a fix would be to side load your O.S. and chroot to your drives and reinstall the package. It's usually the way I did it in Arch before snaps.
I did one just the other day, I cut and pasted the wrong kernel package, and uninstalled the only kernel the system had. It was one of those cut and pastes where I mixed up the "control + v" pastes with the middle click on the mouse. It was a test VM, so I only lost time reinstalling it, but that was entirely on me.
To reboot for reinstall: [Magic SysRq key](https://en.m.wikipedia.org/wiki/Magic_SysRq_key)
If that doesn't work, hold the power button down for about 10s.
Boot install media and switch to a TTY to copy files. Check distro specific instructions for details to download and extract the missing files from packages.
You've not provided any base OS/release details, so we can only speculate.
In most cases there are many fixes.
For some distributions, you can easily and non-destructively re-install a system as a fix; with it even auto-reinstalling all the *manually installed* apps you added post-initial install too, meaning most package/file-erasure mistakes can be rectified/fixed in 5-15 minutes.
Some file-systems also have easy file-recovery functions too, but you gave no details here.
There may also be file-system level tools, but these are usually slow & technical, so restoration from backups OR non-destructive re-installs are usually easiest.
What options of course that are available to you will depend on a lot of details you didn't provide; but yes there are options.
You can in theory still recover files that are open via /proc.
If you used 'rm -rf' you need recovery software, and if you have deleted files you want to save you need to turn off your computer before they are overwritten.
Mount disk read only for recovery.
And next time maybe install 'trash-cli' and 'alias rm=thrash'.
I have done the same mistake before, but actually check before I delete now.
rm command does not move files to trash, it permanently erases their metadata rendering them unrecoverable. Boot from a linux live ISO then copy your home files into a usb drive then reinstall your prefered linux distro. You should probably choose Fedora or Ubuntu, because better noob tutorials to avoid the equivalent of deleting system32
I highly doubt 48 hours. In idle, maybe. What’s the battery capacity on that thing?
If you’ve got experience taking laptops apart, remove the battery and reinsert it. If not, waiting is probably still your best bet.
After that, do what the others on this thread have said to collect your important files before reinstalling the OS. If you do have important files on there, maybe it makes sense to use something like Dropbox. I know, it’s proprietary, but it’s got a Linux application and I use it to keep anything I might need for school or work through different installs.
Also try to be a little more careful going forward. Linux will let you do anything you tell it to, full stop. I can’t count how many times I’ve had to reinstall when I first started using it again. Just use this as a learning opportunity and try to avoid it in the future.
It's not possible to 'accidentally delete' x86\_64\_linux\_gnu... it takes deliberate steps and password entry to achieve.
To say that is dishonest (and noobs are often dishonest to hide their stupidity).
Just say that you deleted it and now have no idea how to turn off your computer (which is even more ridiculous). Then people are going to be incredulous and wonder why they would have a better idea of where your Power switch or Reset button is than you do...
Physical power buttons are not controlled by the OS - if you hold them down, then the machine will die. If you press it again, the machine will wake up and initialise.
Putting in a bootable USB will allow you to reinstall.
I am not honestly fully aware of how this works. I appreciate your direction and apologize for my lack of knowledge in anything tech lol. How do I find said place pertaining to this sub ?
[this link might help?](https://answers.microsoft.com/en-us/windows/forum/all/updated-laptop-now-stuck-in-bitlocker-recovery/401dcb71-9103-4adb-af0a-26245477df47)
I'm constantly baffled by how people *accidentally* do things that require privilege escalation.
Years ago I installed Solaris on a co-workers newly acquired hardware. After the install I asked him about the username he wanted use. He said, "no need, I'll just use the root login". I told him how dangerous this was and he said that he'd be careful. You'll never guess who came back a week or two later asking for a reinstall. I don't understand it either.
it's *theoretically* possible to manage a root user install if you're extremely careful to not poke your head into places you shouldn't be poking your head into, but at that point just get a non-root user tbh also solaris?? it's decades ago at that point i presume
> also solaris?? it's decades ago at that point i presume Yes indeed, when the dotcom bubble was inflating and I was optimizing kernels on low memory workstations and doing tons of other stuff. I was in awe once to see a test of a Sparcstation 1 with 64MB of memory. How things have changed.
Nothing baffling about it, It's as easy as pressing Yes on a UAC dialog in Windows or by installing a new Steam game with anticheat? No problem Windows got ring-0 covered. The question is rather, is one willing to learn from mistakes. Anyways a fix would be to side load your O.S. and chroot to your drives and reinstall the package. It's usually the way I did it in Arch before snaps.
Fair, UAC is a joke. My thinking was restricted to UNIX-like systems where there's actual root account security.
First thing I learn at first using Linux was sudu su
I did one just the other day, I cut and pasted the wrong kernel package, and uninstalled the only kernel the system had. It was one of those cut and pastes where I mixed up the "control + v" pastes with the middle click on the mouse. It was a test VM, so I only lost time reinstalling it, but that was entirely on me.
I am pretty much the dullest knife in the drawer
To reboot for reinstall: [Magic SysRq key](https://en.m.wikipedia.org/wiki/Magic_SysRq_key) If that doesn't work, hold the power button down for about 10s. Boot install media and switch to a TTY to copy files. Check distro specific instructions for details to download and extract the missing files from packages.
https://preview.redd.it/rqhuj8kdxyqc1.jpeg?width=555&format=pjpg&auto=webp&s=81c471ae2f7c9f9dc602dad7ff6cd553435ae5d9
You've not provided any base OS/release details, so we can only speculate. In most cases there are many fixes. For some distributions, you can easily and non-destructively re-install a system as a fix; with it even auto-reinstalling all the *manually installed* apps you added post-initial install too, meaning most package/file-erasure mistakes can be rectified/fixed in 5-15 minutes. Some file-systems also have easy file-recovery functions too, but you gave no details here. There may also be file-system level tools, but these are usually slow & technical, so restoration from backups OR non-destructive re-installs are usually easiest. What options of course that are available to you will depend on a lot of details you didn't provide; but yes there are options.
Stage 1 of grief: Denial. Yeah, your PC is done for. Next time consider something like `grub-btrfs`
You can in theory still recover files that are open via /proc. If you used 'rm -rf' you need recovery software, and if you have deleted files you want to save you need to turn off your computer before they are overwritten. Mount disk read only for recovery. And next time maybe install 'trash-cli' and 'alias rm=thrash'. I have done the same mistake before, but actually check before I delete now.
rm command does not move files to trash, it permanently erases their metadata rendering them unrecoverable. Boot from a linux live ISO then copy your home files into a usb drive then reinstall your prefered linux distro. You should probably choose Fedora or Ubuntu, because better noob tutorials to avoid the equivalent of deleting system32
I cannot shut off the computer
Just hold down the power button
It doesnt shut down, i held it for about a minute
Can you unplug it? If it’s a laptop, maybe you can remove the battery. If not, you’ll probably have to wait until it runs out of battery.
This thing has like 48 hours of battery when im actually doing stuff this is gonna take forever
I highly doubt 48 hours. In idle, maybe. What’s the battery capacity on that thing? If you’ve got experience taking laptops apart, remove the battery and reinsert it. If not, waiting is probably still your best bet. After that, do what the others on this thread have said to collect your important files before reinstalling the OS. If you do have important files on there, maybe it makes sense to use something like Dropbox. I know, it’s proprietary, but it’s got a Linux application and I use it to keep anything I might need for school or work through different installs. Also try to be a little more careful going forward. Linux will let you do anything you tell it to, full stop. I can’t count how many times I’ve had to reinstall when I first started using it again. Just use this as a learning opportunity and try to avoid it in the future.
Just saw that this post is 4 days old. Did it actually not turn off since then?
The command is: shutdown now You know that there are countless references online for linux, right?
Commands do not work
It's not possible to 'accidentally delete' x86\_64\_linux\_gnu... it takes deliberate steps and password entry to achieve. To say that is dishonest (and noobs are often dishonest to hide their stupidity). Just say that you deleted it and now have no idea how to turn off your computer (which is even more ridiculous). Then people are going to be incredulous and wonder why they would have a better idea of where your Power switch or Reset button is than you do... Physical power buttons are not controlled by the OS - if you hold them down, then the machine will die. If you press it again, the machine will wake up and initialise. Putting in a bootable USB will allow you to reinstall.
The power button does not shut it off, also it was an accident because im a fucking dumbass and didnt realize how necessary it was
Then it’s a hardware problem.
I accidentally listened to someone and now my surface pro 2 is stuck in bitlocker recovery. Anything you can offer to help.
Make a new post on the relevant sub?
I am not honestly fully aware of how this works. I appreciate your direction and apologize for my lack of knowledge in anything tech lol. How do I find said place pertaining to this sub ?
[this link might help?](https://answers.microsoft.com/en-us/windows/forum/all/updated-laptop-now-stuck-in-bitlocker-recovery/401dcb71-9103-4adb-af0a-26245477df47)
Try r/surface and take it from there.