I notice that QNX 6.3 on x86 has several copies of “login”
running. Is it bringing up the serial ports as user terminals,
or what?
John Nagle
Team Overbot
John Nagle <nagle@downside.com> wrote:
I notice that QNX 6.3 on x86 has several copies of “login”
running. Is it bringing up the serial ports as user terminals,
or what?
I belive that it brings up the tty logins even if Photon starts.
chris
–
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
Chris McKillop wrote:
John Nagle <> nagle@downside.com> > wrote:
I notice that QNX 6.3 on x86 has several copies of “login”
running. Is it bringing up the serial ports as user terminals,
or what?
I belive that it brings up the tty logins even if Photon starts.
That is so 1980s. How do I turn it off?
John Nagle
Team Overbot
That is so 1980s. How do I turn it off?
I mean for /dev/con*, not serial devices.
chris
–
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
John Nagle wrote:
Chris McKillop wrote:
I belive that it brings up the tty logins even if Photon starts.
That is so 1980s. How do I turn it off?
Edit /etc/config/ttys …
HTH,
Karsten.
–
Karsten P. Hoffmann <karsten.p.hoffmann@web.de>
“I love deadlines. I especially like the whooshing sound
they make as they go flying by.”
[In memoriam Douglas Adams, 1952-2001]
The Neutrino User’s Guide discusses this in a few places (look in the User’s
Guide’s keyword index under ‘login’), and the configuration file is also
described in the Utilities Reference under the tinit utility.
- Eric
“Karsten P. Hoffmann” <karsten.p.hoffmann@web.de> wrote in message
news:ch2c3u$6mg$1@inn.qnx.com…
John Nagle wrote:
Chris McKillop wrote:I belive that it brings up the tty logins even if Photon starts.
That is so 1980s. How do I turn it off?
Edit /etc/config/ttys …HTH,
Karsten.
–
Karsten P. Hoffmann <> karsten.p.hoffmann@web.de
“I love deadlines. I especially like the whooshing sound
they make as they go flying by.”
[In memoriam Douglas Adams, 1952-2001]
My point is that I saw this in QNX 6.3, but the
6.21 systems aren’t running “login”. So I am trying to
figure out what changed.
John Nagle
Team Overbot
Karsten P. Hoffmann wrote:
John Nagle wrote:
Chris McKillop wrote:
I belive that it brings up the tty logins even if Photon starts.That is so 1980s. How do I turn it off?
Edit /etc/config/ttys …HTH,
Karsten.
I had a QNX 6.21NC machine taken in for a disk replacement.
Unfortunately, 40GB drives were no longer available, so the
repair shop copied the existing QNX partition to a new
partition. The old disk had a QNX partition, plus empty
space.
This resulted in a system that boots, but won’t run
chkfsys.
The system will come all the way up, allow logins,
and shows valid files.
But if I try to run “chkfsys -f /dev/hd0t79” from
safe mode, it complains of invalid extents on the
root directory, errors in the bitmaps, and finally
reports a negative amount of space in use.
There’s also a “/dev/hd0t11”, reported as an “invalid
DOS file system”.
Is there any way to straighten this out without
reloading everything?
John Nagle
It gets worse.
Completely reinstalled QNX 6.21NC. Deleted all disk
partitions. Selected “quarter” of disk (20GB) for the
QNX partition.
QNX installed OK. Rebooted and finished installation.
(Remember the 6.21 double-install issue.) Everything looked
good. Did the final reboot as instructed.
On reboot, got
“Cannot load diskboot(8)”
Tried it again. Same error.
Booted from CD, and ran “chkfsys /dev/hd0t79”. No errors,
128 blocks recovered. Shut down and restarted.
“Cannot load diskboot(8)”
Reinstalled entire system again. Same error.
This machine ran QNX just fine for two years, had a hard
drive failure, and now I’m trying to bring up the new hard
drive. It’s not working.
Is there any possibility that there could be a corrupted
partition table, and that the QNX installer can neither detect
nor correct this?
John Nagle
John Nagle wrote:
I had a QNX 6.21NC machine taken in for a disk replacement.
Unfortunately, 40GB drives were no longer available, so the
repair shop copied the existing QNX partition to a new
partition. The old disk had a QNX partition, plus empty
space.This resulted in a system that boots, but won’t run
chkfsys.The system will come all the way up, allow logins,
and shows valid files.But if I try to run “chkfsys -f /dev/hd0t79” from
safe mode, it complains of invalid extents on the
root directory, errors in the bitmaps, and finally
reports a negative amount of space in use.
There’s also a “/dev/hd0t11”, reported as an “invalid
DOS file system”.Is there any way to straighten this out without
reloading everything?John Nagle
Even wierder.
Erased hard drive to totally blank with a Maxstor
intialization utility. Reinstalled QNX 6.21NC.
Install went OK. After final reboot, the system
restarts, gets most of the way up, prints
“Unable to allocate resource: Invalid argument”,
switches to a graphics mode, and the screen blanks.
It’s in a valid graphics mode, though. If I
bring the system up in safe mode, and run “ph”,
Photon comes up just fine.
The message seems to come from “seedres”, of
all things.
John Nagle
John Nagle wrote:
It gets worse.
Completely reinstalled QNX 6.21NC. Deleted all disk
partitions. Selected “quarter” of disk (20GB) for the
QNX partition.QNX installed OK. Rebooted and finished installation.
(Remember the 6.21 double-install issue.) Everything looked
good. Did the final reboot as instructed.On reboot, got
“Cannot load diskboot(8)”
Tried it again. Same error.
Booted from CD, and ran “chkfsys /dev/hd0t79”. No errors,
128 blocks recovered. Shut down and restarted.“Cannot load diskboot(8)”
Reinstalled entire system again. Same error.
This machine ran QNX just fine for two years, had a hard
drive failure, and now I’m trying to bring up the new hard
drive. It’s not working.Is there any possibility that there could be a corrupted
partition table, and that the QNX installer can neither detect
nor correct this?John Nagle
John Nagle wrote:
I had a QNX 6.21NC machine taken in for a disk replacement.
Unfortunately, 40GB drives were no longer available, so the
repair shop copied the existing QNX partition to a new
partition. The old disk had a QNX partition, plus empty
space.This resulted in a system that boots, but won’t run
chkfsys.The system will come all the way up, allow logins,
and shows valid files.But if I try to run “chkfsys -f /dev/hd0t79” from
safe mode, it complains of invalid extents on the
root directory, errors in the bitmaps, and finally
reports a negative amount of space in use.
There’s also a “/dev/hd0t11”, reported as an “invalid
DOS file system”.Is there any way to straighten this out without
reloading everything?John Nagle