(): causing triple fault by IDT (disabled) ...
cpu_reset(): causing triple fault by address space unmap ...
cpu_reset(): entering infinite loop ...
*HANG*
-
Any clue ?
Faulty hardware ? (looking for identical hardware to test)
Kind regards,
Ilya A. Kovalenko
OM> I know this behaviour form every Unix system I've worked on. Besides,
OM> the nice thing about the current way of doing things is that you can
OM> read a script form a pipe and have the desired behaviour without any
OM> special case code.
This behavior has any advantages for regular files ? Co
TK> just edit a copy, chmod +x and mv(1) it into place.
Slightly complicated, but works, because mv(1) removes
old file, so sh(1) working either old version or new one
(no "hybrids").
reliable and/or dangerous. Is there any
IAK> existing ways to solve this problem ?
IAK> Is there sense to make sh(1) to read whole script file before
IAK> executing (optionally, at least), because, as far as I understand,
IAK> current behavior is pretty useless as feature ?
Ilya A. Ko
script file before
executing (optionally, at least), because, as far as I understand,
current behavior is pretty useless as feature ?
Thank you,
Ilya A. Kovalenko (mailto:[EMAIL PROTECTED])
Special EQ SW section
JSC Oganer-Service
oops, wrong list
n reset NIC until next fault). Maybe, due driver imperfection.
So I recommend you to avoid VIA NICs.
Ilya A. Kovalenko
S.A.
7 matches
Mail list logo