Change permisions of a file with my cat's help
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I realize the question title probably sounds weird, theoretical, or just plain stupid. There's a long backstory to this!
root@system:~# less myfile
-bash: /bin/less: Input/output error
The root filesystem is dead. But my cat is still alive (in my memory):
root@system:~# cat > /tmp/somefile
C^d
root@system:~#
He's kind of lonely though, all his friends are gone:
root@system:~# mount
-bash: /bin/mount: Input/output error
root@system:~# dmesg
-bash: /bin/dmesg: Input/output error
root@system:~# less
-bash: /bin/less: Input/output error
root@system:~# chmod
-bash: /bin/chmod: Input/output error
The system is still running, and fulfilling its purpose.
I know, I know, the only sane response to this is to get the system down and replace the root drive. Unfortunately that's not a option as it would cost a lot of time and money. Also, it would kill my cat, and that would make me sad.
I've thought of bringing him his usual friends from a donor.
I dare not try to scp them in, in case ssh tries to load it and cuts the line (the binary is gone anyway). This sounds like a job for my cat's cousin:
root@system:~# netcat -l 1234 > /tmp/less
-bash: netcat: command not found
Unfortunately he's long gone.
Now, I can sort of trick my cat to resurrect him:
cat > netcat < /dev/tcp/localhost/9999
And that sort of worked. He's almost alive:
root@system:/tmp# /tmp/netcat
-bash: /tmp/netcat: Permission denied
He just needs a tiny spark of life. That little +x
magic incantation that I cannot recite at the moment.
Can you please help me bringing my cat's friends back?
bash filesystems cat root-filesystem system-recovery
add a comment |Â
up vote
0
down vote
favorite
I realize the question title probably sounds weird, theoretical, or just plain stupid. There's a long backstory to this!
root@system:~# less myfile
-bash: /bin/less: Input/output error
The root filesystem is dead. But my cat is still alive (in my memory):
root@system:~# cat > /tmp/somefile
C^d
root@system:~#
He's kind of lonely though, all his friends are gone:
root@system:~# mount
-bash: /bin/mount: Input/output error
root@system:~# dmesg
-bash: /bin/dmesg: Input/output error
root@system:~# less
-bash: /bin/less: Input/output error
root@system:~# chmod
-bash: /bin/chmod: Input/output error
The system is still running, and fulfilling its purpose.
I know, I know, the only sane response to this is to get the system down and replace the root drive. Unfortunately that's not a option as it would cost a lot of time and money. Also, it would kill my cat, and that would make me sad.
I've thought of bringing him his usual friends from a donor.
I dare not try to scp them in, in case ssh tries to load it and cuts the line (the binary is gone anyway). This sounds like a job for my cat's cousin:
root@system:~# netcat -l 1234 > /tmp/less
-bash: netcat: command not found
Unfortunately he's long gone.
Now, I can sort of trick my cat to resurrect him:
cat > netcat < /dev/tcp/localhost/9999
And that sort of worked. He's almost alive:
root@system:/tmp# /tmp/netcat
-bash: /tmp/netcat: Permission denied
He just needs a tiny spark of life. That little +x
magic incantation that I cannot recite at the moment.
Can you please help me bringing my cat's friends back?
bash filesystems cat root-filesystem system-recovery
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I realize the question title probably sounds weird, theoretical, or just plain stupid. There's a long backstory to this!
root@system:~# less myfile
-bash: /bin/less: Input/output error
The root filesystem is dead. But my cat is still alive (in my memory):
root@system:~# cat > /tmp/somefile
C^d
root@system:~#
He's kind of lonely though, all his friends are gone:
root@system:~# mount
-bash: /bin/mount: Input/output error
root@system:~# dmesg
-bash: /bin/dmesg: Input/output error
root@system:~# less
-bash: /bin/less: Input/output error
root@system:~# chmod
-bash: /bin/chmod: Input/output error
The system is still running, and fulfilling its purpose.
I know, I know, the only sane response to this is to get the system down and replace the root drive. Unfortunately that's not a option as it would cost a lot of time and money. Also, it would kill my cat, and that would make me sad.
I've thought of bringing him his usual friends from a donor.
I dare not try to scp them in, in case ssh tries to load it and cuts the line (the binary is gone anyway). This sounds like a job for my cat's cousin:
root@system:~# netcat -l 1234 > /tmp/less
-bash: netcat: command not found
Unfortunately he's long gone.
Now, I can sort of trick my cat to resurrect him:
cat > netcat < /dev/tcp/localhost/9999
And that sort of worked. He's almost alive:
root@system:/tmp# /tmp/netcat
-bash: /tmp/netcat: Permission denied
He just needs a tiny spark of life. That little +x
magic incantation that I cannot recite at the moment.
Can you please help me bringing my cat's friends back?
bash filesystems cat root-filesystem system-recovery
I realize the question title probably sounds weird, theoretical, or just plain stupid. There's a long backstory to this!
root@system:~# less myfile
-bash: /bin/less: Input/output error
The root filesystem is dead. But my cat is still alive (in my memory):
root@system:~# cat > /tmp/somefile
C^d
root@system:~#
He's kind of lonely though, all his friends are gone:
root@system:~# mount
-bash: /bin/mount: Input/output error
root@system:~# dmesg
-bash: /bin/dmesg: Input/output error
root@system:~# less
-bash: /bin/less: Input/output error
root@system:~# chmod
-bash: /bin/chmod: Input/output error
The system is still running, and fulfilling its purpose.
I know, I know, the only sane response to this is to get the system down and replace the root drive. Unfortunately that's not a option as it would cost a lot of time and money. Also, it would kill my cat, and that would make me sad.
I've thought of bringing him his usual friends from a donor.
I dare not try to scp them in, in case ssh tries to load it and cuts the line (the binary is gone anyway). This sounds like a job for my cat's cousin:
root@system:~# netcat -l 1234 > /tmp/less
-bash: netcat: command not found
Unfortunately he's long gone.
Now, I can sort of trick my cat to resurrect him:
cat > netcat < /dev/tcp/localhost/9999
And that sort of worked. He's almost alive:
root@system:/tmp# /tmp/netcat
-bash: /tmp/netcat: Permission denied
He just needs a tiny spark of life. That little +x
magic incantation that I cannot recite at the moment.
Can you please help me bringing my cat's friends back?
bash filesystems cat root-filesystem system-recovery
bash filesystems cat root-filesystem system-recovery
asked 7 mins ago
goncalopp
1,65211423
1,65211423
add a comment |Â
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f475353%2fchange-permisions-of-a-file-with-my-cats-help%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password