Re: The disappearing sys_call_table export.

Ahmed Masud
2003-05-15T16:10:53Z

On Thu, 15 May 2003, Richard B. Johnson wrote:

> On Thu, 15 May 2003, Chris Ricker wrote:
>
> > On Thu, 15 May 2003, Richard B. Johnson wrote:
> >
> > > > You don't have to do that. Richard is mis-informed. Any of the following
> > > > still work on Red Hat Linux 9:
> > > >
> > > > init=/bin/bash # drops you straight to a bash shell
> > > > init 1 # runs runlevel 1 SysV init scripts and rc.sysinit
> > > > init single # runs rc.sysinit, but not runlevel 1
> > > > init emergency # runs a shell
> > > >
> > > > all without going to rescue media.
> > > >
> > >
>
> Sill bullshit. I did nothing except to try to help a neighbor
> who got locked out of her machine. I spent most of Saturday
> and all of Sunday trying to break in. The LILO command prompt
> readily took "parameters". However, any parameter passed on
> the command-line resulted in a try-to-kill init error. Her
> machine uses an Adaptec SCSI controller which needs to be
> loaded via initrd to make the root file-system available.
>
> I tried Red-Hat 8.0 here at work. It works as you described.
> There is no problem with it and LILO and initrd. However
> Red Hat 9/Professional does not allow break-in, at least on
> the machine tested...and I have several pissed off witnesses.
>

This is an issue directly to be taken up with the manufacturer and is a
bit off topic here. RedHat 9 professional can conceivably disallow
parameter passing. The fact that a system does not, out of the box, allow
for break-ins is a good thing(tm) for most part... manually editing
password files is a bad thing(tm), this is why command line tools such as
useradd are provided.

Any how, I hope you got it all fixed.

Cheers,

Ahmed.