On Mon, Jul 16, 2001 at 02:01:53PM -0400, Alan Shutko wrote:
>
> > So, does anyone have a way to recover using only shell builtins, for
> > just in case there aren't any executable files left?
>
The sash shell (in the sash package) has built-ins for most of these
utilities (chmod, chown, ls, cp,
Dave Sherohman <[EMAIL PROTECTED]> writes:
> Easy enough to bootstrap yourself out of that one, provided /bin/cp
> is still executable:
Or, if /lib/ld-linux.so.2 is still executable:
/lib/ld-linux.so /bin/chmod a+x /bin/chmod
> So, does anyone have a way to recover using only shell builtins, fo
%% Dave Sherohman <[EMAIL PROTECTED]> writes:
ds> Changing it to:
ds> find . -name .[^.] -print0 | xargs -0 chmod r-owx
Not to be anal retentive, but ITYM:
... -name '.[^.]*' ...
Your glob won't match anything except ".x" where x is exactly one
character long but != ".".
--
---
On Tue, Jul 10, 2001 at 10:42:42PM -0400, Paul D. Smith wrote:
> %% Dave Sherohman <[EMAIL PROTECTED]> writes:
> ds> On Mon, Jul 09, 2001 at 12:29:40PM -0400, Paul D. Smith wrote:
> dc> find . -print0 | xargs -0 chmod r-owx
> ds> while the find version will leave .foo/bar alone and change
>
On Sun, Jul 08, 2001 at 10:14:12PM -0400, Paul D. Smith wrote:
> Both chmod -R and ls -R behave the same way. However, your description
> above is not actually what happens, and I haven't seen anyone else here
> correct it in so many words. So, just to be clear:
>
> Remember that the shell expan
%% Dave Sherohman <[EMAIL PROTECTED]> writes:
ds> On Mon, Jul 09, 2001 at 12:29:40PM -0400, Paul D. Smith wrote:
>> >> BTW, the best way to do what you wanted to do is this:
>> >>
>> >> $ chmod -R o-owx .[!.]*
dc> Or even better, ignore the -R in the chmod command and use find:
dc>
On Mon, Jul 09, 2001 at 12:29:40PM -0400, Paul D. Smith wrote:
> %% Dave Carrigan <[EMAIL PROTECTED]> writes:
> >> BTW, the best way to do what you wanted to do is this:
> >>
> >> $ chmod -R o-owx .[!.]*
>
> dc> Or even better, ignore the -R in the chmod command and use find:
>
> dc>
%% Dave Carrigan <[EMAIL PROTECTED]> writes:
dc> "Paul D. Smith" <[EMAIL PROTECTED]> writes:
>> BTW, the best way to do what you wanted to do is this:
>>
>> $ chmod -R o-owx .[!.]*
dc> Or even better, ignore the -R in the chmod command and use find:
dc> find . -print0 | xargs -0
"Paul D. Smith" <[EMAIL PROTECTED]> writes:
> BTW, the best way to do what you wanted to do is this:
>
> $ chmod -R o-owx .[!.]*
Or even better, ignore the -R in the chmod command and use find:
find . -print0 | xargs -0 chmod r-owx
--
Dave Carrigan ([EMAIL PROTECTED])| YOW!!
hiya marin
> > if you only wanted to change the local dot files... oh well...
> > we all learn and remember the hard way... :-)
> > shoulda been: chmod pattern ~/.*
>
> NO. ~/.* includes .. ~/.. too, if expanded by the shell. In this case this
> would be /root/.. which is nothing els but
> if you only wanted to change the local dot files... oh well...
> we all learn and remember the hard way... :-)
> shoulda been: chmod pattern ~/.*
NO. ~/.* includes .. ~/.. too, if expanded by the shell. In this case this
would be /root/.. which is nothing els but / ... the same mess agai
Thanks for the very full explanation.
Sigh.
Reinstall? I have done fresh installs many
times. Sorry I don't know the drill for reinstalls.
I could move the stuff I want to save to one parti
tion, and then reinstall on just / and /boot?
Josh Narins
PS Tough to type like that :)
On 8 Jul 2001, David Z Maze wrote:
> Alvin Oga <[EMAIL PROTECTED]> writes:
> AO> if you only wanted to change the local dot files... oh well...
> AO> we all learn and remember the hard way... :-)
> AO> shoulda been: chmod pattern ~/.*
>
> ...which will still catch ~/. and ~/.., which you don
%% [EMAIL PROTECTED] writes:
j> 1. ( ) text/plain (*) text/html
No need for HTML on the mailing list.
j> I tried, in a subdir of /root, the command
j> chmod -R o-rwx .*
j> It changed the permissions on the parent directory,
j> the parent's parent directory, all the
Alvin Oga <[EMAIL PROTECTED]> writes:
AO> if you only wanted to change the local dot files... oh well...
AO> we all learn and remember the hard way... :-)
AO> shoulda been: chmod pattern ~/.*
...which will still catch ~/. and ~/.., which you don't want.
(Particularly as root, whose home dire
hi ya josh
the .* told it to change it to the directory above it too...
geez what fun
if you only wanted to change the local dot files... oh well...
we all learn and remember the hard way... :-)
shoulda been: chmod pattern ~/.*
an easy fix might be:
( your system might/
[EMAIL PROTECTED] writes:
> Is there any chance chmod -R o-rwx .* started working
> on subdirectories of / ?
Yes, since that's what -R means. Your system is hosed. Reinstall.
--
Alan Shutko <[EMAIL PROTECTED]> - In a variety of flavors!
Do not think by infection, catching an opinion like a co
On Sun, Jul 08, 2001 at 06:25:27PM -0400, [EMAIL PROTECTED] wrote:
>
> Ah, I see now how -R and .* could get kinda crazy.
>
> Thank you.
>
> But I changed the perms of / a bit, but it still won't
> work (cd is now working for regular user, but no logins,
> nor does ls work).
/bin/login is setui
Ah, I see now how -R and .* could get kinda crazy.
Thank you.
But I changed the perms of / a bit, but it still won't
work (cd is now working for regular user, but no logins,
nor does ls work).
Does anyone have a proper perms setup for / ?
Is there any chance chmod -R o-rwx .* started working
on
On Sun, Jul 08, 2001 at 04:17:34PM -0400, [EMAIL PROTECTED] wrote:
|
| I tried, in a subdir of /root, the command
| chmod -R o-rwx .*
| It changed the permissions on the parent directory,
| the parent's parent directory, all the way up.
Yes, '.*" includes ".." which is the parent directory.
| No
20 matches
Mail list logo
