Mike, a note about using sudo. *NIX derives much of its security by
being a true, multi-user operating system, limiting the access a user
has by default. When you run things with sudo, you circumvent this
system and open yourself up to the largest security risk. Here's a good
rule of thumb to use when deciding whether to use sudo: try the command
as your normal user (without sudo) first. If it doesn't work, then run
with sudo.
This has been the source of many of your problems when you've tried
running various programs. When configuring/compiling a kernel or any
program, for instance, you only need super-user privileges to install
(copy to its destination). Compiling as the super-user allows malicious
code to do absolutely anything on your computer and potentially others,
including but not limited to actually frying your computer. Granted,
most programmers have more integrity than that, but there are those out
there that will take advantage of the inexperienced user that grants
them all the privileges they need to exercise their whatever their
ambitions may be.
This is just a warning and advisory to you Michael. I hope you
understood what I said and act on it. I believe many of your
difficulties will disappear with this information.
-Bryce
On Thu, 2004-07-29 at 11:23, Michael Havens wrote:
> [directory at (1)]
> I want to apply a patch to my existing kernel (openMosix->2.4.22)
> I believe that all that requires is for me to run 'make ...config' (menu, x)
> again but when I do so it says:
>
> bmike1@1[src]$ sudo make menuconfig
> make: *** No rule to make target `menuconfig'. Stop.
> bmike1@1[src]$
>
> I have tried doing it from /usr/src/linux-2.4.22 /usr/src/linux and /usr/src
> and some other directories with the same results.
> . . . .
> I then ran the program make since the program Makefile is in the directory
> resulting in:
>
> bmike1@1[linux-2.4.22]$ sudo make
> Makefile:259: arch/i386/Makefile: No such file or directory
> make: *** No rule to make target `arch/i386/Makefile'. Stop.
> bmike1@1[linux-2.4.22]$
>
> which lead me to wonder if I put Makefile
> into /lib/modules/2.4.22/kernel/arch/i386 (the only 'arch/i386' there is) if
> it would make. Unfortunately, that proved to be fruitless.
>
> Any ideas?
(text/plain)
