Pages

Search

kernel-2.6.16 make problem: "target pattern contains no `%' - Forums Linux

kernel-2.6.16 make problem: "target pattern contains no `%' - Forums Linux

kernel-2.6.16 make problem: "target pattern contains no `%'

Posted: 20 Apr 2006 08:26 AM PDT

On Thu, 20 Apr 2006 17:26:31 +0200, clemens fischer wrote:
 
<snip> 
Do you have bash on your system? You refer to using "env" which gives a
hint that you may not be using bash. I looked a little closer at the
makefile which sets CONFIG_SHELL.

Also, which distribution are you running?

--
Douglas Mayne

Who Are You? Remote Login Only if System In /etc/hosts.

Posted: 19 Apr 2006 09:15 AM PDT

Dave Uhring wrote: 

Dave.... I hang me head in shame. :)

Out of all the entries in the DNS reverse mine was the only one
missing. I sorted the IP field and right there between x.x.x.159 and
x.x.x.161 was a missing 160.

Thanks for your well founded "doubts." They proved to be most
insightful.

Now I think I will quickly run through all the DNS and make sure that
Microsoft DNS checkbox under TCP/IP "Register this connection's
addressess in DNS" did not fail elsewhere.

Problem installing Linux: please help

Posted: 19 Apr 2006 08:34 AM PDT

Hi Douglas,

I realised where I was going wrong. I have three hard disks on my
computer and I was trying to install LInux on one of them with all
three connected (one as Primary Master, the second as Primary Slave and
the third as Secondary Master; the CDRW connects as the Secondary
Slave). I disconnected the other two hard disks from my computer, made
the hard disk that i wanted to install Fedora on as the Primary Master
and, Hey Presto, it works.

So, for some reason, the installation drive (CDRW) was not able to
identify which IDE drive to install Linux on. Or am I still going
wrong?

Tarun

Slackware Lilo boot hang

Posted: 18 Apr 2006 09:45 AM PDT

On 18 Apr 2006, in the Usenet newsgroup comp.os.linux.setup, in article
<googlegroups.com>, com wrote:
 

-rw-rw-r-- 1 gferg ldp 287028 Mar 31 2003 Remote-Serial-Console-HOWTO

We set all of our headless boxes to run a remote serial console. This gives
a second way to access the box if the network doesn't come up.
 

That often indicates a hardware problem - noise wiggling the wire around,
or a failed 'pullup' function somewhere. What do you see in the boot
messages (/var/log/messages). Is logging not even started? That's where a
serial console would come in handy - even if all you did was redirect the
output on the receiving device to a file.
 

It's been a while since I dealt with that.
 

-rw-rw-r-- 1 gferg ldp 58787 Oct 21 09:45 LILO
-rw-rw-r-- 1 gferg ldp 8080 Apr 26 2001 Multiboot-with-LILO

those are mini-HOWTOs - and you also want to hit the man page.
 

Two different things. If this is all of /etc/lilo.conf, and you are just
single booting, the 'prompt' and 'timeout' lines could be commented out
or deleted (I don't recommend this normally, as I may want to interrupt
the boot process to bring it up in single user mode - by that's your
decision). But this screen isn't colored unless you have something
set in your BIOS to do so. Are you referring to a splash screen?

Old guy

Poss simple question : Installing old HD in new system

Posted: 18 Apr 2006 08:05 AM PDT

On 18 Apr 2006 08:05:32 -0700, rened wrote: 
<snip> 

If you unplugged the old dirve, did the install, and are expecting the
new drive to be the running os. Then the first thing to check/set is
the new drive is strapped as Master and the old drive is strapped
slave. You then have the PC's bios scan for drives and verify they
match what you expect based on the drive straps.

After that I would have to GUESS it is a partition label problem
because you are running some redhat os.

You might want to read http://www.catb.org/~esr/faqs/smart-questions.html

I did it just the way I should not have?

Posted: 16 Apr 2006 10:08 AM PDT


"Sirf" <de> wrote in message
news:googlegroups.com... 

Hold it. Grub should also be able to do this just fine. Henro, you should be
able to use a rescue disk and edit your grub.conf to use the right
settings, and if necessary run "grub-install" to be sure that your boot
loader is set correctly. Whee did you tell the boot loader to be installed
at Linux installation time?

But I *suspect* that the problem is that the BIOS setup is inappropriately
seeing the second disk as the first disk, or in the process of doing
interesting things you've swapped the SATA cables. What does "fdisk -l" and
/etc/fstab and /boot/grub/grub.conf say?

new user

Posted: 16 Apr 2006 05:22 AM PDT

Russ <net> did eloquently scribble: 

Multiposting aside...
first would be to type
startx
(assuming you've installed X and a GUI so far)
if not, run dselect or one of the other debian installers and install KDE or
Gnome and all their dependencies.
--
| |What to do if you find yourself stuck in a crack|
| co.uk |in the ground beneath a giant boulder, which you|
| |can't move, with no hope of rescue. |
|Andrew Halliwell BSc(hons)|Consider how lucky you are that life has been |
| in |good to you so far... |
| Computer Science | -The BOOK, Hitch-hiker's guide to the galaxy.|

What is SFS ?

Posted: 16 Apr 2006 03:48 AM PDT

Dave Stratford wrote: 
Have a look here:
http://www.cs.auckland.ac.nz/~pgut001/sfs/

--
Leo (Bing) Whiteway in Kelowna, BC, Canada: Ham calls: VE7UW and VE7OKV
A computer without Microsoft is like a chocolate cake without mustard.
< running Linux >

Installing Windows XP on a system with Suse 10

Posted: 15 Apr 2006 06:04 AM PDT

Groovy hepcat Igor Canadi was jivin' on Sat, 15 Apr 2006 13:04:47
+0000 (UTC) in comp.os.linux.setup.
Installing Windows XP on a system with Suse 10's a cool scene! Dig it!
 

Windoze has to be installed on one of the first two primary
partitions of a drive. Looks like you've installed it in an extended
logical partition. It has to be a primary partition marked as
bootable.
 

It's not really stupid to install Linux first, if you know what
you're doing, and if you install Windoze on a separate drive. My
advice is to get another hard drive (they're fairly inexpensive these
days) and install Windoze on that. Make sure to set it up as the
second hard drive (/dev/hdb), not the first. And delete the FAT/NTFS
partitions on /dev/hda. This is to make sure Windoze only sees the
second hard drive. (It ignores any partition types it doesn't
recognise, and can ignore a whole drive.) As long as you stick to this
setup, Windoze will never clober your boot loader.
When done installing Windoze, boot Linux and add an entry for
Windoze in your grub setup. (I don't know how to do that. I use lilo.)
In fact, it is a good idea to do this *before* you start to install
Windoze; because Windoze setup will need to reboot, and so you need to
be able to boot the Windoze partition when it reboots.

--

Dig the even newer still, yet more improved, sig!

http://alphalink.com.au/~phaywood/
"Ain't I'm a dog?" - Ronny Self, Ain't I'm a Dog, written by G. Sherry & W. Walker.
I know it's not "technically correct" English; but since when was rock & roll "technically correct"?