Pages

Search

Location of program in various distros - Forums Linux

Location of program in various distros - Forums Linux

Location of program in various distros

Posted: 13 Oct 2004 11:06 PM PDT

John Karuski wrote: 

On RHEL3 it is:

$ which dialog
/usr/bin/dialog
$ which perl
/usr/bin/perl


--
.~. Jean-David Beyer Registered Linux User 85642.
/V\ Registered Machine 241939.
/( )\ Shrewsbury, New Jersey http://counter.li.org
^^-^^ 08:05:00 up 21 days, 19:10, 4 users, load average: 4.11, 4.17, 4.17

lilo fails with VolumeID read error on non-referenced disk

Posted: 13 Oct 2004 05:58 PM PDT

Rob Yampolsky <com> wrote: 

Just run lilo -vvv. Then talk to us.

Peter

rescue disk

Posted: 13 Oct 2004 05:01 AM PDT

"chabral" <com> escribió en el mensaje
news:416d191a$0$56896$sunsite.dk...
 
the 
of 
share 

First of all, I want to thank everyone for your comments, all have been very
usefull.

The thing is that now I've an operational "rescue diskette". It boots,
reinstall lilo reading the lilo.conf in the hard disk, and ask the user to
press a key to restart.

During my search of a method for acomplishing this, I analized only two:

- Reutilize tomsrtbt

- Build my own diskete using a ramdisk, as suggested by Laurenz Albe



From the two methods above, the first was not suitable for me. It was too
hard to edit tomsrtbt for accomplishing such a simple task, and the worst
thing was that even the provided scripts (buildit.s) didn't work because of
a libc incompatibility.



So I followed the way suggested by Laurenz. I build my own kernel with only
the basic options: ramdisk support, ide support for my disks, ext3 support,
console support, and a few others. No hardware support for devices of course
and no modules as I compiled everything important inside the kernel. At the
end, I got a 1MB 2.6.8.1 kernel.

Then I began the ramdisk creation. I'm using Slackware 10, so I used a
script named mkinitrd, but building an initrd is not a big deal, it can
easily be done by hand. The benefit of a script is that in the process of
creating your final version you'll have to build several ramdisk versions,
so having a script saves time. A workaround for the case that you don't have
a script for creating the ramdisk, is using any ramdisk you have and editing
it. For example, if the file is initrd.gz you can create a backup of it
(lets say restore.gz), then unzip it with gunzip, and mounting it with:
mount ./restore /mnt/initrd -o loop (remember to create /mnt/initrd or
whatever you like). Then you can browse inside the file, make any changes
you like, unmount it, zip it, and use it in your diskette. Basically, you
must edit the file linuxrc to do what you want, and remember to use absolute
paths (eg /bin/echo) because no PATH is defined.



The last part was installing lilo in the floppy. The best way I found to do
this was to write the lilo.conf as if the floppy where your root disk, and
then with the floppy mounted running: lilo -r /mnt/floppy. I tried to use
the script makebootdik provided with Slackware, but it required a lot of
editing to have things done as I wanted.

From here is all try and correct.



I hope this helps anyone wanting to do the same. Don't forget to do a backup
of your diskette with dd, because they don't have a long life and tend to
fail when you most need them :)

MCPAN / CPAN configuration question

Posted: 12 Oct 2004 11:11 AM PDT

Keith Keller wrote: 

It's usable... for making a honeypot.

--

Jose Maria Lopez Hernandez
Director Tecnico de bgSEC
com
bgSEC Seguridad y Consultoria de Sistemas Informaticos
http://www.bgsec.com
ESPAÑA

The only people for me are the mad ones -- the ones who are mad to live,
mad to talk, mad to be saved, desirous of everything at the same time,
the ones who never yawn or say a commonplace thing, but burn, burn, burn
like fabulous yellow Roman candles.
-- Jack Kerouac, "On the Road"

Compile & Upgrade Kernel

Posted: 12 Oct 2004 07:51 AM PDT


"vgaswin" <com> wrote in message
news:google.com... 

First, simply upgrade to Fedora Core 2. Seriously, this gets you all the
other applications and tools you need for the 2.6 kernel in one step, and
installs a 2.6 kernel.

Second, take a look at whether you can use the latest RPM based kernels in
the Fedora development FTP sites. This can provide you automatic editinig of
the lilo.conf or grub.conf files, report dependencies, make it easier and
safer to *remove* an old kernel, etc.

Third, if you're still determined to do it yourself, take a look at the
"kernel-source" RPM's. They already include configuration files for various
hardware configurations, and a set of patches either backported from newer
kernels to support new hardware and fix known bugs, or to set things up the
way RedHat likes them. Then read the various HOW-TO's on the net about
compiling RedHat kernels.