Hi,
I'm having an issue where if I have syslog output something to
/dev/console, it comes back to syslog again as a "kernel:" message.
I've verified that this is definitely something with /dev/console, since
even if I do :
valhalla# echo "STRAIGHT TO CONSOLE&q
On Mon, 26 Mar 2007, Kevin Kinsey wrote:
Neil Short wrote:
I'd like to redirect /dev/console to some file that
can be read by the xrootconsole port.
Is this ambition feasible?
I like the functionality of xconsole; but it's not
very pretty.
According to the default /etc/syslog
Neil Short wrote:
I'd like to redirect /dev/console to some file that
can be read by the xrootconsole port.
Is this ambition feasible?
I like the functionality of xconsole; but it's not
very pretty.
According to the default /etc/syslog.conf, you should
be able to enable syslogd t
I'd like to redirect /dev/console to some file that
can be read by the xrootconsole port.
Is this ambition feasible?
I like the functionality of xconsole; but it's not
very pretty.
==
Now I, Nebuchadnezzar, praise and extol and honor the King of heaven, for all
his works are trut
(94)
May 21 18:31:07 merkur smbd[554]: Unable to connect to CUPS server localhost
- Connection refused
May 21 18:31:07 merkur init: can't get /dev/console for controlling terminal:
Operation not permitted
May 21 18:31:37 merkur init: can't get /dev/console for controlling terminal:
Op
Hello Wash
Am Sat, May 13, 2006 at 07:49:29PM +0300 Odhiambo WASHINGTON schrieb:
> * On 13/05/06 15:38 +0200, Martin Schweizer wrote:
> | Hello
> |
> | After upgradeing to 5.4p14 I get this on the console:
>
> tell us how you upgraded.. what steps?
- cvsuped RELENG_5_4
- like described in the h
- Where come
this from?
May 13 14:25:09 merkur kernel: May 13 14:25:09 merkur init: can't get
/dev/console for controlling terminal: Operation not permitted
May 13 14:25:42 merkur kernel: May 13 14:25:39 merkur init: can't get
/dev/console for c
Kris Kennaway <[EMAIL PROTECTED]> wrote: On Wed, Mar 08, 2006 at 09:13:51PM
-0800, Mark Jayson Alvarez wrote:
>
>
> Kris Kennaway wrote:
> No, they're different. Anyway, /dev/cuaaN was replaced by /dev/cuadN.
>
> Kris
>
> Ok, its working now.. How about multiple console connections using
On Wed, Mar 08, 2006 at 09:13:51PM -0800, Mark Jayson Alvarez wrote:
>
>
> Kris Kennaway <[EMAIL PROTECTED]> wrote:
> No, they're different. Anyway, /dev/cuaaN was replaced by /dev/cuadN.
>
> Kris
>
> Ok, its working now.. How about multiple console connections using just a
> single console
Kris Kennaway <[EMAIL PROTECTED]> wrote:
No, they're different. Anyway, /dev/cuaaN was replaced by /dev/cuadN.
Kris
Ok, its working now.. How about multiple console connections using just a
single console cable?? sort of like pseudo terminal used by ssh.
It seems like /dev/cuaaN has been replaced by /dev/console.
No, they're different. Anyway, /dev/cuaaN was replaced by /dev/cuadN.
Kris
pgpQ1MXxzUBfP.pgp
Description: PGP signature
Hi,
I'm trying to secure our cisco router by hooking its console to a freebsd 6.0
box. I was reading this document:
http://www.onlamp.com/pub/a/bsd/2001/10/11/FreeBSD_Basics.html
It seems like /dev/cuaaN has been replaced by /dev/console. On my 6.0 box, I
can't seem to find
Tabor Kelly wrote:
[snip]
I have no idea what file it was or how it got changed, but thanks Ash.
I figured out what I did. I overwrote the default /boot/device.hints
with the 4 lines in my original email (I didn't realize there was a
default /boot/device.hints). This was all accomplished with the
Ash wrote:
[snip]
Well, I looked and looked for what was wrong, and I was 100% sure it
wasn't anything in the /boot directory. However, just to be sure I
copied everything in /boot and /boot/default from another FreeBSD 5.3R
system I had, and it started working again.
I have no idea what file i
/acpi.ko text=0x3fbfc data=0x1c04+0x112c
syms=[0x4+0x72f0+0x4+0x97c7
]
-
FreeBSD/i386 (laptop.taborandtashell.net) (ttyv0)
login:
Also, nothing that would normally be displayed on ttyv0 via /dev/console
(syslog stuff) is there. Booting with ACPI disabled does not help. The
weird thing is that this
data=0x1c04+0x112c
syms=[0x4+0x72f0+0x4+0x97c7
]
-
FreeBSD/i386 (laptop.taborandtashell.net) (ttyv0)
login:
Also, nothing that would normally be displayed on ttyv0 via /dev/console
(syslog stuff) is there. Booting with ACPI disabled does not help. The
weird thing is that this didn't used to h
og in from
another machine using SSH and look around. In /var/log/messages I have a
lot of entries: "init: can't get /dev/console for controlling terminal:
Operation not permitted".
OK, so I figured it might have something to do with terminal initialization
and read the man page o
g the
shell script rc with the command autoboot. After I killed them I was able
to start Samba by running the script in /usr/local/etc/rc.d.
The only messages I can find in /var/log/messages that seem to be related
are recurring "init: can't get /dev/console for controlling terminal:
O
18 matches
Mail list logo
