On Wed, 10 Jul 2013, John Morris wrote:
On Wed, 2013-07-10 at 14:09 +0200, Karel Volný wrote:
Dne středa, 10. července 2013 5:13:22 CEST, John Morris napsal(a):
...
But then I remembered that if things have really went wrong you could boot
with init=/usr/bin/bash.
how do these advices help
On Wed, 10 Jul 2013, "Jóhann B. Guðmundsson" wrote:
On 07/10/2013 12:32 PM, Karel Volný wrote:
Dne úterý, 9. července 2013 16:57:22 CEST, "Jóhann B. Guðmundsson"
napsal(a):
No need too, Bill will just close this WONTFIX and reach through the
screen and smack you on the back of your head or Vác
On Wed, 2013-07-10 at 14:09 +0200, Karel Volný wrote:
> Dne středa, 10. července 2013 5:13:22 CEST, John Morris napsal(a):
> ...
> > But then I remembered that if things have really went wrong you could boot
> > with init=/usr/bin/bash.
>
> how do these advices help when the system is already so
On 07/10/2013 12:32 PM, Karel Volný wrote:
Dne úterý, 9. července 2013 16:57:22 CEST, "Jóhann B. Guðmundsson"
napsal(a):
No need too, Bill will just close this WONTFIX and reach through the
screen and smack you on the back of your head or Václav will just
find you with something to throw at yo
Dne úterý, 9. července 2013 16:57:22 CEST, "Jóhann B. Guðmundsson" napsal(a):
No need too, Bill will just close this WONTFIX and reach
through the screen and smack you on the back of your head or
Václav will just find you with something to throw at you, either
way you need to find a helmet and
Thanks to all for their opinion.
Now the last question: Could init sent on ctr-alt-del at least TERM and
KILL to all processes in case, everything else failed ?
Could systemd do that?
My answers are YES and NO, but I may be wrong.
For systemd I saw (after power interruption) in the log this:
Dne středa, 10. července 2013 5:13:22 CEST, John Morris napsal(a):
If you want sysrq and understand the implications you can enable it
...
But then I remembered that if things have really went wrong you could boot
with init=/usr/bin/bash.
how do these advices help when the system is already
On 07/09/2013 01:42 AM, Gavin Flower wrote:
I sync I know what youmean!
:)
Seriously, thanks for the short history lesson, puts it all into
perspective.
To be clear, I didn't write it.
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/
On 07/09/2013 06:17 AM, John Reiser wrote:
Yes it does, because the rest of the system might not be quiescent
during the first sync.
While that is certainly true, "sync" doesn't make the rest of the system
quiescent.
The first sync disturbs the system
with an impulse of activity. This may
On Mon, 2013-07-08 at 18:02 +0200, Adam Pribyl wrote:
> OK, so the systemd people say, it is perfecly fine you can not reboot via
> ctrl-alt-del (while it was always possible with init) and give me the
> advice to enable sysrq for the purpose, and sysrq people say, it's not for
> users, we will
On 07/09/2013 10:41 AM, Karel Volný wrote:
Dne pondělí, 8. července 2013 14:03:00 CEST, Adam Pribyl napsal(a):
So to avoid the worst - the need to interrupt the power and risk the
damage to all other mounted file systems, I'd like to open a
discussion on enabling the sysrq in Fedora by default
On 07/09/2013 01:22 AM, Gordon Messmer wrote:
> On 07/08/2013 09:39 AM, John Reiser wrote:
>> 1. Install a userid whose login shell is /usr/bin/sync
>> (or a script which does "sync; sync")
>> 2. Login as the sync user (twice, perhaps.)
>
> Running sync multiple times doesn't have any particul
Dne pondělí, 8. července 2013 14:03:00 CEST, Adam Pribyl napsal(a):
So to avoid the worst - the need to interrupt the power and
risk the damage to all other mounted file systems, I'd like to
open a discussion on enabling the sysrq in Fedora by default to
work around this feature:
https://bugz
On 09/07/13 20:22, Gordon Messmer wrote:
On 07/08/2013 09:39 AM, John Reiser wrote:
1. Install a userid whose login shell is /usr/bin/sync
(or a script which does "sync; sync")
2. Login as the sync user (twice, perhaps.)
Running sync multiple times doesn't have any particular purpose on Li
On 07/08/2013 09:39 AM, John Reiser wrote:
1. Install a userid whose login shell is /usr/bin/sync
(or a script which does "sync; sync")
2. Login as the sync user (twice, perhaps.)
Running sync multiple times doesn't have any particular purpose on Linux.
http://utcc.utoronto.ca/~cks/space/bl
On Mon, 8 Jul 2013, Samuel Sieb wrote:
On 07/08/2013 09:02 AM, Adam Pribyl wrote:
OK, so the systemd people say, it is perfecly fine you can not reboot
via ctrl-alt-del (while it was always possible with init) and give me
That seems unlikely that init would have been ok... Ctrl-alt-del
swit
On 07/08/2013 04:02 PM, Adam Pribyl wrote:
On Mon, 8 Jul 2013, "Jóhann B. Guðmundsson" wrote:
No need to open a discussion. SysRq is disable for are a reason and
what you are propose allows anyone that sits at the keyboard to kill
all process,reboot without syncing or authorization and all bec
On 07/08/2013 09:02 AM, Adam Pribyl wrote:
OK, so the systemd people say, it is perfecly fine you can not reboot
via ctrl-alt-del (while it was always possible with init) and give me
That seems unlikely that init would have been ok... Ctrl-alt-del
switched to runlevel 6, so it still depended
On 07/08/2013, Adam Pribyl wrote:
> On Mon, 8 Jul 2013, "Jóhann B. Guðmundsson" wrote:
>
>> No need to open a discussion. SysRq is disable for are a reason and what you
>> are propose allows anyone that sits at the keyboard to kill all
>> process,reboot without syncing or authorization and all b
On Mon, 8 Jul 2013, "Jóhann B. Guðmundsson" wrote:
No need to open a discussion. SysRq is disable for are a reason and what
you are propose allows anyone that sits at the keyboard to kill all
process,reboot without syncing or authorization and all because you got
a corrupted filesystem.
OK,
Sounds like an unfortunate situation that should be addressed by use of a
Live system, which can repair or salvage data from the afflicted file
systems. If repair is possible, job done. If not possible, solution is
to re-install the operating system.
Rather than invest serious effort to make sys
On 07/08/2013 12:03 PM, Adam Pribyl wrote:
I've hit very unpleasant trouble - my ext4 rootfs gots crazy and I had
a thousands of "multiply claimed blocks" files. This revealed to me
one systemd weakness - it depends so heavily on a files on a rootfs,
it can not, in case they are damaged, do its
22 matches
Mail list logo
