Pessoal, boa tarde.
Após suspender o sistema com o comando 'sudo pm-suspend', ao reinicia-lo é
exibido essa mensagem após a tela do GRUB:
*/bin/sh: Can’t access tty; job control turned off *
*(initramfs) *
*
*
Alguem pode me dar uma ajuda?
2013/8/27 Daniel Ferreira Bonfim daniel.f...@gmail.com:
Pessoal, boa tarde.
Ôlas Daniel, Comunidade e Navegante futuro.
Após suspender o sistema com o comando 'sudo pm-suspend', ao reinicia-lo é
exibido essa mensagem após a tela do GRUB:
/bin/sh: Can’t access tty; job control turned off
.
Ôlas Daniel, Comunidade e Navegante futuro.
Após suspender o sistema com o comando 'sudo pm-suspend', ao
reinicia-lo é
exibido essa mensagem após a tela do GRUB:
/bin/sh: Can’t access tty; job control turned off
(initramfs)
Alguem pode me dar uma ajuda?
O comando era para
El Sun, 28 Apr 2013 12:47:33 -0600, Carlos Carcamo escribió:
El día 14 de abril de 2013 03:55, Camaleón noela...@gmail.com
escribió:
(...)
es seguro fsck, nunca había escuchado sobre eso, pero ya leí algo por
ahí aunque no me queda muy claro si es recomendado o no utilizarlo!
Pues
-in commands.
/bin/sh can't access tty job control turned off (initramfs)
La solución fue utilizar fsck, ahora estoy feliz de nuevo con mi debian!
Muchas gracias, Santiago José y Camaleón, sin su ayuda de seguro no
hubiera logrado recuperar mi sistema, muchas gracias de verdad!
El día 14 de
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
El 28/04/13 20:47, Carlos Carcamo escribió:
(...)
Muchas gracias, Santiago José y Camaleón, sin su ayuda de seguro no
hubiera logrado recuperar mi sistema, muchas gracias de verdad!
Ese 'Top-Posting'...
De nada, pero para la próxima vez,
El 14/04/13 07:31, Carlos Carcamo escribió:
es seguro fsck, nunca había escuchado sobre eso, pero ya leí algo por
ahí aunque no me queda muy claro si es recomendado o no utilizarlo!
Haz copia de seguridad de todo lo que tienes y házlo con el FSCK, pero vía
LiveCD y desmontado.
--
Saludos de
El Sat, 13 Apr 2013 23:31:07 -0600, Carlos Carcamo escribió:
El día 13 de abril de 2013 14:59, Camaleón noela...@gmail.com
escribió:
(...)
sera que tengo que formatear? de ser así, cuando instale debian deje
las siguientes particiones:
dev/sda3 -- /
dev/sda2 -- /boot
dev/sda4 --
.
/bin/sh can't access tty job control turned off (initramfs)
no tengo idea de cual es el problema, buscando en google en unos foros
lei que podria tener problemas mi disco duro, y no lo creo, cargue un
live cd de fedora y puedo entrar y ver todos mis archivos, entonces el
disco duro funciona
convendría que nos enviaras sea en el formato que sea
(texto o foto) :-)
y por ultimo esto:
BusyBox v1.1.3 (Debian 1:1.1.3-4) Built-in shell (ash)
Enter 'help' for a list of built-in commands.
/bin/sh can't access tty job control turned off (initramfs)
no tengo idea de cual es el
access tty job control turned off (initramfs)
no tengo idea de cual es el problema, buscando en google en unos foros
lei que podria tener problemas mi disco duro, y no lo creo, cargue un
live cd de fedora y puedo entrar y ver todos mis archivos, entonces el
disco duro funciona!
Pues sin tener
El 13/04/13 17:32, Camaleón escribió:
(...)
Lo que puedes hacer para ver más datos en el arranque es editar la línea
del kernel desde GRUB y quitar el quiet para que el arranque sea más
verboso. Pero has de tener ojos para leer lo que pone y lápiz para
transcribirlo...
No es _tan
. Try passing init= bootarg
BusyBox v1.17.1 (Debian 1:1.17.1-8) built-in shell (ash)
Enter 'help' for a list of built-in commands.
/bin/sh: can´t access tty; job control turned off
(initramfs)
...
hasta acá no se que problema tiene, parece que no encuentra la
partición root o algo así, pero no se
El 13/04/13 20:07, Carlos Carcamo escribió:
mount: mounting /proc on /root/proc failed: No such file or directory
Target filesystem doesn't have requested /sbin/init.
No init found. Try passing init= bootarg
Ahí está el problema... El /root/proc no existe. Por lo tanto, ha de estar
en /proc.
tardando en hacer una copia de seguridad
de todos los datos (carga una LiveCD y rescata todo lo que puedas si te lo
permite).
BusyBox v1.17.1 (Debian 1:1.17.1-8) built-in shell (ash) Enter 'help'
for a list of built-in commands.
/bin/sh: can´t access tty; job control turned off (initramfs
.
/bin/sh: can´t access tty; job control turned off (initramfs)
...
hasta acá no se que problema tiene, parece que no encuentra la partición
root o algo así, pero no se que habrá pasado, lo ultimo que estuve
haciendo en la computadora fue navegar por internet!
No es que no la encuentre
El 13/04/13 22:36, Carlos Carcamo escribió:
Entre con el disco de rescate pero efectivamente no puedo montar nada
en dev/sda3, desde el live CD puedo entrar y ver todos mis datos del
home, pero no puedo entrar al /, dice que no puedo montar esa
partición, textualmente dice:
Entonces, debes
El Sat, 13 Apr 2013 14:36:13 -0600, Carlos Carcamo escribió:
El día 13 de abril de 2013 13:53, Camaleón noela...@gmail.com
escribió:
(...)
hasta acá no se que problema tiene, parece que no encuentra la
partición root o algo así, pero no se que habrá pasado, lo ultimo que
estuve haciendo en
es seguro fsck, nunca había escuchado sobre eso, pero ya leí algo por
ahí aunque no me queda muy claro si es recomendado o no utilizarlo!
El día 13 de abril de 2013 14:59, Camaleón noela...@gmail.com escribió:
El Sat, 13 Apr 2013 14:36:13 -0600, Carlos Carcamo escribió:
El día 13 de abril de
2012/2/24, Miguel Barrera Fernández mbarr...@ismm.edu.cu:
Hola a todos
Mi pc empezó a dar el siguiente error /bin/sh: can´t acces tty; job control
turned off por lo que no me deja entrar al sistema.
Hoy me encontré con ese error al cambiar un HD con Squeeze
de un equipo a otro, lo solucioné
El Fri, 24 Feb 2012 14:20:53 -0600, Miguel Barrera Fernández escribió:
Mi pc empezó a dar el siguiente error /bin/sh: can´t acces tty; job
control turned off por lo que no me deja entrar al sistema.
¿Y el error empezó así sin más, de un día para otro sin haber hecho nada?
Google encuentra
Hola a todaos
Mi pc empezó a dar el siguiente error /bin/sh: can´t acces tty; job control
turned off por lo que no me deja entrar al sistema.
--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I have had a problem for a long time now when logging in on tty1 as root
or any user. On logging in the system reports -bash: no job control
in this shell on tty1. Others here have also reported the problem but
we never found a fix, other then Ctrl c and re-logging in.
I have been annoyed
On Sun, Feb 08, 2009 at 08:27:09PM -0800, Daniel Burrows wrote:
On Sun, Feb 08, 2009 at 07:58:51AM -0500, Douglas A. Tutty
dtu...@vianet.ca was heard to say:
Perhaps your controller program will have
to be a filter between the process and the terminal: pipe its std-in an
std-out to the
On Mon, Feb 09, 2009 at 10:37:07AM -0500, Douglas A. Tutty dtu...@vianet.ca
was heard to say:
On Sun, Feb 08, 2009 at 08:27:09PM -0800, Daniel Burrows wrote:
On Sun, Feb 08, 2009 at 07:58:51AM -0500, Douglas A. Tutty
dtu...@vianet.ca was heard to say:
Perhaps your controller program
On Sun, Feb 08, 2009 at 05:52:34PM +1000, Adrian Levi wrote:
2009/2/8 Daniel Burrows dburr...@debian.org:
Hello list,
I've been banging my head on this one for a while.
I have a need to write some code that can manage job control on a
terminal. More specifically, I need to run
to the controlling terminal?
Is the controlling terminal actually connected to the stdin of your
subprocess in the normal case (check in /proc to be sure)?
The libc info also has example code for implementing a shell with job
control, but I haven't looked at it closely yet.
Regards,
Mirko
On Sun, Feb 08, 2009 at 05:52:34PM +1000, Adrian Levi adrian.l...@gmail.com
was heard to say:
2009/2/8 Daniel Burrows dburr...@debian.org:
Hello list,
I've been banging my head on this one for a while.
I have a need to write some code that can manage job control on a
terminal
to write some code that can manage job control on a
terminal. More specifically, I need to run a single process and stuff
it into the background at will, so that it gets suspended when it tries
to read from the terminal. So, there's a controller process and
a subprocess process
:) -- I meant that the terminal has been taken
away via tcsetpgrp().
The libc info also has example code for implementing a shell with job
control, but I haven't looked at it closely yet.
Yeah, that's basically what I was basing my ideas on.
The fundamental issue seems
Hello list,
I've been banging my head on this one for a while.
I have a need to write some code that can manage job control on a
terminal. More specifically, I need to run a single process and stuff
it into the background at will, so that it gets suspended when it tries
to read from
On Saturday 07 February 2009 18:58:13 Daniel Burrows wrote:
I've been banging my head on this one for a while.
The source for /bin/dash and /bin/bash are available. You might should be
able to peruse them and find the correct way to suspend/resume/detach/etc.
processes.
--
Boyd Stephen
On Sat, Feb 07, 2009 at 10:43:11PM -0600, Boyd Stephen Smith Jr. wrote:
On Saturday 07 February 2009 18:58:13 Daniel Burrows wrote:
I've been banging my head on this one for a while.
The source for /bin/dash and /bin/bash are available. You might should be
able to peruse them and find
are available. You might should
be able to peruse them and find the correct way to
suspend/resume/detach/etc. processes.
Would the screen program (or its sources) be of any help?
My first guess would be no. Screen does not multiplex the terminal the same
way job control does. In particular
2009/2/8 Daniel Burrows dburr...@debian.org:
Hello list,
I've been banging my head on this one for a while.
I have a need to write some code that can manage job control on a
terminal. More specifically, I need to run a single process and stuff
it into the background at will, so
On 12:51 Mon 07 Jan , Scott Gifford wrote:
To find out, create a brand new user with default dotfiles, and try
logging in as that user.
Hope this helps,
No such luck :(.
Every user who initially logs in to tty1 gets the no job control message!
Here is some information.
I find
initially login to the pc
the shell says to me (ominously):
-bash: no job control in this shell.
1) I don't know what this means.
2) I don't know what causes it.
3) It bothers me (I dont know why. Just in principle!).
4) So if I really want that job control thingy back, what do I have
Mitchell Laks [EMAIL PROTECTED] writes:
[...]
1) I don't know what this means.
It means you can't hit CTRL-Z to suspend a process, move processes to
the foreground and background, or use the jobs command. See the JOB
CONTROL section of bash(1) for more details.
Not sure what causes it, but I
):
-bash: no job control in this shell.
1) I don't know what this means.
2) I don't know what causes it.
3) It bothers me (I dont know why. Just in principle!).
4) So if I really want that job control thingy back, what do I have to do.
I figure it is a left over from some mess up of my . files
On 2008-01-07 01:08:20 -0500, Mitchell Laks wrote:
I notice right after I initially login to the pc
the shell says to me (ominously):
-bash: no job control in this shell.
1) I don't know what this means.
2) I don't know what causes it.
Perhaps some command in your .bashrc
: Waiting for device /dev/hda3 to
appear: not found...exiting to /bin/sh
sh: can't access tty; job control turned off.
Primero pense que era cosa del file system asi que cheque para ver si habia
puesto al sistema ext3 ( que el que utilizo) en el kernel y si esta y no
esta como modulo sino lo
Hola lista ..
Mi problema es el siguiente, recompile el kernel 2.6.14 y a la hora de
reiniciar me marca el siguiente error: Waiting for device /dev/hda3 to
appear: not found...exiting to /bin/sh
sh: can't access tty; job control turned off.
Primero pense que era cosa del file system asi
/bin/sh: can't access tty; job control turned off
#
with even the simplest linuxrc : (
I created an initrd consisting of:
/bin
/bin/dash
/bin/echo
/bin/sh - dash
/dev
/dev/console c 5 1
/lib
/lib/ld.so.1
/lib/libc.so.6
/linuxrc
linuxrc is a not-overly-complicated shell script:
#!/bin/sh
echo linuxrc
.
Freeing unused kernel memory: 164k init 4k chrp 32k prep
/bin/sh: can't access tty; job control turned off
#
with even the simplest linuxrc : (
I created an initrd consisting of:
/bin
/bin/dash
/bin/echo
/bin/sh - dash
you probably want more binaries ... insmod, rmmod, mount, ..
/dev
For the archives:
On Sat, Nov 08, 2003 at 04:16:23PM -0800, Bill Moseley wrote:
Common question: how do I make the viewer a child of init so that when
mutt exits it's not a zombie waiting on the viewer or closing mutt
doesn't kill the viewer?
Well, one answer would seem a script called
I'm using a modification of mutt_bgrun where a .mailcap entry might be:
image/png; /home/moseley/bin/mutt_bgrun display '%s'; test=test -n $DISPLAY
and mutt_bgrun is basically:
file=$(mktemp);
cp $2 $file
( $1 $file; rm $file )
That allows control to return to mutt while the viewer is
At Fri, 30 Mar 2001 18:40:31 -0700 (MST), John Galt [EMAIL PROTECTED]
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
nohup
On Thu, 29 Mar 2001 [EMAIL PROTECTED] wrote:
- Begin Hush Signed Message from [EMAIL PROTECTED]
-
This is not a debian question, but it's so generic
Quoth Brian May,
Erik == Erik Steffl [EMAIL PROTECTED] writes:
Erik nohup, I think you can also set up the shell not to kill
Erik children when it exits (start command in background (append
Erik at the end of command line) or background it while it
Erik works, usually
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
nohup
On Thu, 29 Mar 2001 [EMAIL PROTECTED] wrote:
- Begin Hush Signed Message from [EMAIL PROTECTED] -
This is not a debian question, but it's so generic I'm not sure where else
to ask it.
How do you free a process from your login? I
- Begin Hush Signed Message from [EMAIL PROTECTED] -
This is not a debian question, but it's so generic I'm not sure where else
to ask it.
How do you free a process from your login? I want to start a commandline
program, then logoff and have the program continue to execute. Currently
[EMAIL PROTECTED] wrote:
- Begin Hush Signed Message from [EMAIL PROTECTED] -
This is not a debian question, but it's so generic I'm not sure where else
to ask it.
How do you free a process from your login? I want to start a commandline
program, then logoff and have the program
to start a commandline
program, then logoff and have the program continue to execute. Currently
I'm using at as a work around, but it seems like you should be able to
interactively spin the process off on its own. Thanks.
You can use your shell's own built-in job control, but my preference
Erik == Erik Steffl [EMAIL PROTECTED] writes:
Erik nohup, I think you can also set up the shell not to kill
Erik children when it exits (start command in background (append
Erik at the end of command line) or background it while it
Erik works, usually ctrl-z to stop it, bg to
-BEGIN PGP SIGNED MESSAGE-
On Tue, 12 Oct 1999 [EMAIL PROTECTED] wrote:
Then I think I am in trouble...
I chose to run dselect on an xterm as su root.
So, if I kill that window to install a new version of afterstep,
what i am currently running, am I up the creek?
Oh, boy.
Now I am
Hi,
Got a quick one.
How do I get a particular transfer control of a particular PID to
another ttyX or xterm?
Don't think I've ever read anything about this.
Thanks,
bw
bwarsing [EMAIL PROTECTED] writes:
BW On Tue, Oct 12, 1999 at 04:38:08PM -0400, Noah L. Meyerhans wrote:
NLM There is a utility called 'screen' to handle this. It's
NLM packaged for Debian. You'd run your program in a screen session
NLM in one window ('screen mutt' for example).
BW
BW Then I
Hi,
I remember there's patch or else to make 'es'
have job control ability.
Do you know where to get it?
thanks
-mlt
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . Trouble?
e-mail to [EMAIL PROTECTED] .
57 matches
Mail list logo
