Thanks,
I spent the better part of the day trying to figure this one out. Not only did
I lose the ablilty to become root, but my machine hung when trying to start the
postgresql postmaster (which I believe needed root privlages). I was stumped
because I was able to boot up from my rescue disk
Thanks,
I spent the better part of the day trying to figure this one out. Not only
did
I lose the ablilty to become root, but my machine hung when trying to start
the
postgresql postmaster (which I believe needed root privlages). I was stumped
because I was able to boot up from my
On Wed, 21 Oct 1998, Pete Harlan wrote:
The latest slink update to sysklogd 1.3-29 is SERIOUSLY broken. I
installed it and could no longer become root. If you have installed it,
Perhaps then a new version should be uploaded; this version would fail
during install with a brief
The latest slink update to sysklogd 1.3-29 is SERIOUSLY broken. I
installed it and could no longer become root. If you have installed it,
Perhaps then a new version should be uploaded; this version would fail
during install with a brief explanation, so we don't have to hear
people who don't
The latest slink update to sysklogd 1.3-29 is SERIOUSLY broken. I
installed it and could no longer become root. If you have installed it,
you will need to boot with your rescue disk (you do have one, don't you?)
and either disable sysklogd (chmod -x /etc/init.d/sysklogd) or install the
hamm
Bob Nielsen wrote:
The latest slink update to sysklogd 1.3-29 is SERIOUSLY broken. I
installed it and could no longer become root. If you have installed it,
you will need to boot with your rescue disk (you do have one, don't you?)
and either disable sysklogd (chmod -x /etc/init.d/sysklogd)
On Sat, 17 Oct 1998, Bob Nielsen wrote:
The latest slink update to sysklogd 1.3-29 is SERIOUSLY broken. I
installed it and could no longer become root. If you have installed it,
you will need to boot with your rescue disk (you do have one, don't you?)
and either disable sysklogd (chmod -x
7 matches
Mail list logo
