Linux-Development-Sys Digest #108, Volume #8 Tue, 29 Aug 00 02:13:10 EDT
Contents:
Re: where is "make" in linux ("Ross Crawford")
RTLinux + SMP? ("news.crdva1.bc.wave.home.com")
uClinux configuration setup options for Gerry (Yew Fai, Wong)
Re: spin locks (Karl Heyes)
Re: kernel compiles root device as (3,65); boots for (3,41) (Dirk Foersterling)
Re: Q: SMP question (Hugo Varotto)
Re: root password ([EMAIL PROTECTED])
Re: root password ("Ross Crawford")
Re: where is "make" in linux (Josef Moellers)
Re: spin locks (Josef Moellers)
SOLVED! Re: Kernel panic: VFS: (Koch)
Re: where is "make" in linux ("Ross Crawford")
----------------------------------------------------------------------------
From: "Ross Crawford" <[EMAIL PROTECTED]>
Subject: Re: where is "make" in linux
Date: Mon, 28 Aug 2000 16:04:04 +1000
Is this sounding more & more like a Windoze solution?
ROSCO
<[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Thanks for everybody's help.
> Being an entry level user, I end up reinstall the latest version of
RedHat,
> which solved the problem.
>
------------------------------
From: "news.crdva1.bc.wave.home.com" <[EMAIL PROTECTED]>
Subject: RTLinux + SMP?
Date: Mon, 28 Aug 2000 23:03:58 GMT
I want to experiment with Real Time Linux on an mutli-processor box. Say I
have two real time processes that need to run at high priority, loaded as
modules for RTLinux. Will they ever get scheduled to run at the same time
on both processors? Or is there a single kernel-semaphore that will prevent
this?
Best Regards
Jeff Koftinoff
[EMAIL PROTECTED]
------------------------------
From: Yew Fai, Wong <[EMAIL PROTECTED]>
Subject: uClinux configuration setup options for Gerry
Date: Mon, 28 Aug 2000 23:05:15 GMT
Hello :
I need to port linux (uClinux) to a switch : Gerry, that has a MCF5307
motorola microprocessor. I've followed instructions from the
www.uClinux.org website but I've encountered some problems and wondered
if anyone can offer some help.
Because I do not have direct access to the Gerry Hardware at the
moment, I'm not entirely sure how to configure the various setup
options during "make config" stage. Is anyone familiar with the Gerry
so as to help me on this setup configuration? This is what I've done
but it does NOT compile sucessfully during the "make" stage :
*
* Code maturity level options
*
Prompt for development and/or incomplete code/drivers
(CONFIG_EXPERIMENTAL) [Y/n/?] n
*
* Platform dependant setup
*
CPU (MC68000, MC68328, MC68EZ328, MC68332, MC68360, MCF5206, MCF5206e,
MCF5307, MCF5204) [MCF5307] mcf5307
defined CONFIG_M5307
*
* Platform
*
Arnewsh 5307 eval board support (CONFIG_ARNEWSH) [N/y/?] n
Moreton Bay NETtel support (CONFIG_NETtel) [N/y/?] n
Moreton Bay eLIA development board support (CONFIG_eLIA) [N/y/?] n
Moreton Bay DISKtel support (CONFIG_DISKtel) [N/y/?] n
Cadre-III eval board support (CONFIG_CADRE3) [N/y/?] n
Old mask (broken watchdog timer) (CONFIG_OLDMASK) [N/y/?] n
Kernel executes from (RAM, ROM) [RAM] ram
defined CONFIG_RAMKERNEL
*
* General setup
*
PCI bios support (CONFIG_PCI) [Y/n/?] n
Networking support (CONFIG_NET) [Y/n/?] y
System V IPC (CONFIG_SYSVIPC) [Y/n/?] n
Reduced memory footprint (CONFIG_REDUCED_MEMORY) [Y/n/?] y
Kernel support for flat binaries (CONFIG_BINFMT_FLAT) [Y/n/?] y
Compile kernel as ELF - if your GCC is ELF-GCC (CONFIG_KERNEL_ELF)
[Y/n/?] y
Console support (CONFIG_CONSOLE) [Y/n/?] n
*
* Floppy, IDE, and other block devices
*
ROM disk memory block device (CONFIG_BLK_DEV_BLKMEM) [Y/n/?] y
IDE harddisk support (CONFIG_BLK_DEV_IDE) [Y/n/?] y
Include IDE/ATAPI CDROM support (CONFIG_BLK_DEV_IDECD) [Y/n/?] n
Include IDE/ATAPI TAPE support (CONFIG_BLK_DEV_IDETAPE) [Y/n/?] n
Include IDE/ATAPI FLOPPY support (new) (CONFIG_BLK_DEV_IDEFLOPPY)
[Y/n/?] y
*
* Additional Block Devices
*
Loopback device support (CONFIG_BLK_DEV_LOOP) [Y/n/?] n
Multiple devices driver support (CONFIG_BLK_DEV_MD) [Y/n/?] n
RAM disk support (CONFIG_BLK_DEV_RAM) [Y/n/?] y
Release empty RAM disk blocks (CONFIG_RD_RELEASE_BLOCKS) [Y/n/?] y
*
* Networking options
*
Network firewalls (CONFIG_FIREWALL) [Y/n/?] n
Network aliasing (CONFIG_NET_ALIAS) [Y/n/?] y
TCP/IP networking (CONFIG_INET) [Y/n/?] y
IP: forwarding/gatewaying (CONFIG_IP_FORWARD) [Y/n/?] y
IP: multicasting (CONFIG_IP_MULTICAST) [Y/n/?] y
IP: syn cookies (CONFIG_SYN_COOKIES) [Y/n/?] y
IP: accounting (CONFIG_IP_ACCT) [Y/n/?] y
IP: optimize as router not host (CONFIG_IP_ROUTER) [Y/n/?] y
IP: tunneling (CONFIG_NET_IPIP) [Y/n/?] y
IP: aliasing support (CONFIG_IP_ALIAS) [Y/n/?] y
*
* (it is safe to leave these untouched)
*
IP: PC/TCP compatibility mode (CONFIG_INET_PCTCP) [N/y/?] n
IP: Reverse ARP (CONFIG_INET_RARP) [N/y/?] n
IP: Disable Path MTU Discovery (normally enabled)
(CONFIG_NO_PATH_MTU_DISCOVERY) [N/y/?] n
IP: Drop source routed frames (CONFIG_IP_NOSR) [N/y/?] n
IP: Allow large windows (not recommended if <16Mb of memory)
(CONFIG_SKB_LARGE) [N/y/?] n
*
*
*
The IPX protocol (CONFIG_IPX) [N/y/?] n
Appletalk DDP (CONFIG_ATALK) [N/y/?] n
Amateur Radio AX.25 Level 2 (CONFIG_AX25) [N/y/?] n
Kernel/User network link driver (CONFIG_NETLINK) [N/y/?] y
Routing messages (CONFIG_RTNETLINK) [Y/n/?] y
*
* Network device support
*
Network device support (CONFIG_NETDEVICES) [Y/n/?] y
Dummy net driver support (CONFIG_DUMMY) [N/y/?] n
SLIP (serial line) support (CONFIG_SLIP) [Y/n/?] y
CSLIP compressed headers (CONFIG_SLIP_COMPRESSED) [Y/n/?] y
Keepalive and linefill (CONFIG_SLIP_SMART) [N/y/?] n
Six bit SLIP encapsulation (CONFIG_SLIP_MODE_SLIP6) [N/y/?] n
PPP (point-to-point) support (CONFIG_PPP) [Y/n/?] y
*
* CCP compressors for PPP are only built as modules.
*
EQL (serial line load balancing) support (CONFIG_EQUALIZER) [N/y/?] n
Cirrus Logic cs8900 ethernet (CONFIG_UCCS8900) [N/y/?] n
SMC 9194 ethernet (CONFIG_SMC9194) [Y/n/?] n
NE2000/NE1000 ISA ethernet (CONFIG_NE2000) [N/y/?] n
*
* Filesystems
*
Quota support (CONFIG_QUOTA) [N/y/?] y
Minix fs support (CONFIG_MINIX_FS) [N/y/?] n
Extended fs support (CONFIG_EXT_FS) [N/y/?] n
Second extended fs support (CONFIG_EXT2_FS) [Y/n/?] n
xiafs filesystem support (CONFIG_XIA_FS) [N/y/?] n
Native language support (Needed for FAT and ISO9660) (CONFIG_NLS)
[N/y/?] n
/proc filesystem support (CONFIG_PROC_FS) [Y/n/?] y
NFS filesystem support (CONFIG_NFS_FS) [N/y/?] y
Root file system on NFS (CONFIG_ROOT_NFS) [N/y/?] (NEW) y
BOOTP support (CONFIG_RNFS_BOOTP) [N/y/?] (NEW) n
RARP support (CONFIG_RNFS_RARP) [N/y/?] (NEW) n
SMB filesystem support (to mount WfW shares etc..) (CONFIG_SMB_FS)
[N/y/?] n
OS/2 HPFS filesystem support (read only) (CONFIG_HPFS_FS) [N/y/?] n
System V and Coherent filesystem support (CONFIG_SYSV_FS) [N/y/?] n
ROM filesystem support (CONFIG_ROMFS_FS) [Y/n/?] n
UFS filesystem support (read only) (CONFIG_UFS_FS) [N/y/?] n
*
* Character devices
*
ColdFire serial support (CONFIG_COLDFIRE_SERIAL) [Y/n/?] y
16550 serial support (CONFIG_SERIAL) [N/y/?] y
ColdFire MBUS Support (CONFIG_MCF_MBUS) [N/y/?] y
Support for TEXT based LCD driver (CONFIG_LCDTXT) [N/y/?] n
Support for ColdFire DMA driven LCD driver (CONFIG_LCDDMA) [N/y/?] n
Support for ColdFire DMA driven DAC0800 driver (CONFIG_DAC0800) [N/y/?]
n
Support for ColdFire DMA driven I2S DAC driver (CONFIG_DACI2S) [N/y/?] n
Support for ColdFire T6963 driver (CONFIG_T6963) [N/y/?] n
Hifn 7901 encryption accellerator support (CONFIG_HIFN7901) [N/y/?] n
Watchdog Timer Support (CONFIG_WATCHDOG) [N/y/?] y
*
* Kernel hacking
*
Kernel profiling support (CONFIG_PROFILE) [N/y/?] n
Magic SysRq Key (CONFIG_MAGIC_SYSRQ) [N/y/?] n
Panic/Dump to FLASH (CONFIG_DUMPTOFLASH) [N/y/?] y
The linux kernel is now hopefully configured for your setup.
Check the top-level Makefile for additional configuration,
and do a 'make dep ; make clean' if you want to be sure all
the files are correctly re-made
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: Karl Heyes <[EMAIL PROTECTED]>
Subject: Re: spin locks
Date: Tue, 29 Aug 2000 00:29:02 +0000
In article <8ocug8$9sv$[EMAIL PROTECTED]>, "Peter Huang"
<[EMAIL PROTECTED]> wrote:
> Hi all
>
> I'm new at Linux programming and I was suggested by some helpful people in to
> use spin locks for things I'm doing. I have Rubini's book on Linux
> programming but it doesn't cover spin locks since it is a new subject. Can
> any one tell me where I can get comprehensive information on spin locks or
> can give me some ideas over the net on how to use spin locks.. I would
> appreciate it.
>
look in linux/Documentation/spinlocks.txt. It's definitely a kernel thing
though, if that is what you are wanting.
karl
------------------------------
From: [EMAIL PROTECTED] (Dirk Foersterling)
Crossposted-To: comp.os.linux.misc
Subject: Re: kernel compiles root device as (3,65); boots for (3,41)
Date: 28 Aug 2000 04:40:40 GMT
On Mon, 28 Aug 2000 01:29:24 GMT, xavian anderson macpherson wrote:
>
>M. Buchenrieder wrote:
>>
>> man rdev
>> man lilo.conf
>>
>> Michael
>> --
>> Michael Buchenrieder * [EMAIL PROTECTED] *
>http://www.muc.de/~mibu
>> Lumber Cartel Unit #456 (TINLC) & Official Netscum
>> Note: If you want me to send you email, don't munge your address.
>--------------------------------------------------------------------------
>I HAD ALREADY READ THE MAN RDEV. IT DID NOT TELL ME HOW TO SET THE DEVICE
>FROM 3,41 TO 3,65 OR REVERSE. if you know the exact code to fix this, give
First, it does. Here's the passage:
When using the rdev, or swapdev commands, the root_device
or swap_device parameter are as follows:
/dev/hda[1-8]
/dev/hdb[1-8]
/dev/sda[1-8]
/dev/sdb[1-8]
If you look at /dev/hdb1 using ls -l, you will see something like that:
brw------- 1 root root 3, 65 Nov 15 1993 /dev/hdb1
This is Device 3,65. The other number you mentioned is 3,41. This would
be /dev/hda41 which I don't think is correct. Are you sure that you
didn't get confused by hex numbers? (Hex 41 = Dec 65).
-dirk
--
D i r k F "o r s t e r l i n g
[EMAIL PROTECTED] ******** http://www.DeathsDoor.com/milliByte/
-------------
"If p gleich tail then wird hilf auch auf tail gesetzt." - R.K.
------------------------------
From: Hugo Varotto <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Re: Q: SMP question
Date: Mon, 28 Aug 2000 23:09:31 -0400
Yes and no. Linux tries to keep tasks in the same CPU, but doesn't make any
guarantees.
The ready tasks are in a "runqueue" ( which is global and common to all the
CPUS ). When a CPU enters the schedule() routine, it will check all the tasks
that are in the runqueue. Each task will be processed by the "goodness()"
function, which basically will return a numeric value for every task. That value
will depend on the priority associated with the task, if ii uses real-time
scheduling or not, etc. Also, if that task was previously dispatched by the
current CPU, it will add an addditional amount to the calculated value.
Eventually, the task with the biggest value will be selected for dispatch. If no
task is in the runqueue, the CPU will schedule the "idle" task (which has an
initial value of zero ).
So, if in the runqueue there's a task that was previously dispatched by the
current CPU, most probably will be dispatched again by the same CPU. If however
no task in the runque was previously dispatched by the current CPU ( assuming
there's at least a task there ), then one of those tasks will be "migrated" to
the current CPU.
When I was in grad school I did some research on binding tasks to different
CPUS, disallowing the inherent global migration, migrating tasks to certain
CPUS, reserving CPU time for particular tasks, mixing "bounded" tasks and
regular tasks, etc. It's a very interesting topic.
I'll recommend that you get a copy of the excellent book "Linux Core Kernel
Commentary", which explains these topics in detail.
Hugo
Kaz Kylheku wrote:
> On 28 Aug 2000 13:18:19 GMT, Holger Eitzenberger
> <[EMAIL PROTECTED]> wrote:
> >Hi,
> >
> >me and a colleague were discussing how SMP is implemented on Linux.
> >I know that in true SMP you don't have the guarantee on which CPU a
> >process will run the next time the process gets processor time. Is
> >this different on Linux?
>
> Yes. Each processor self-schedules from a global run queue. So a process that
> is sitting in the run queue can be picked up by any processor.
>
> > My coleague is pretty sure that a process on
> >Linux always runs on the same CPU.
>
> Not only is that not true, but there is no interface for assuring it.
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: root password
Date: Tue, 29 Aug 2000 04:50:12 GMT
In article <8od7t4$2e6k$[EMAIL PROTECTED]>,
"Alexei Sinitsyn" <[EMAIL PROTECTED]> wrote:
> > What i can do to login as a root if i fergot my root password??
> If you have a PC machine you can type in LILO prompt something like
this:
> linux single
> or
> linux init=/bin/bash
>
> and then change your root password
>
> sincerely,
> Alex
> Thanks Alex for the replay
But at Lilo prompt if system will not ask for my root password than any
one can change it. What's about sequrity?
A person who knows this can go and destroy any Linux system!!!!
Thanks again.
Bharat.
>
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: "Ross Crawford" <[EMAIL PROTECTED]>
Subject: Re: root password
Date: Tue, 29 Aug 2000 13:45:29 +1000
<[EMAIL PROTECTED]> wrote in message news:8offdu$41j$[EMAIL PROTECTED]...
> In article <8od7t4$2e6k$[EMAIL PROTECTED]>,
> "Alexei Sinitsyn" <[EMAIL PROTECTED]> wrote:
> > > What i can do to login as a root if i fergot my root password??
> > If you have a PC machine you can type in LILO prompt something like
> this:
> > linux single
> > or
> > linux init=/bin/bash
> >
> > and then change your root password
> >
> > sincerely,
> > Alex
> > Thanks Alex for the replay
> But at Lilo prompt if system will not ask for my root password than any
> one can change it. What's about sequrity?
> A person who knows this can go and destroy any Linux system!!!!
Only if they have physical access to the console. Security is more than just
choosing the right password....
ROSCO
------------------------------
From: Josef Moellers <[EMAIL PROTECTED]>
Subject: Re: where is "make" in linux
Date: Tue, 29 Aug 2000 07:42:21 +0200
Ross Crawford wrote:
> =
> Is this sounding more & more like a Windoze solution?
While I would be hard pressed to use the words "Windows" and "make" and
"kernel generation" in one sentence ... no, this does not sound more &
more like a Windoze solution.
It _may_ sound like a Windoze solution, if it were a Windoze problem
with Windoze symptoms:
1. Windows does not have "make" and you certainly cannot generate your
own kernel.
2. (and more important) Windoze will not give you any clue whatsoever
that "make" might be missing. It would probably tell you something about
missing interface lines on COM1 or it would just crash. Under ideal
circumstances, it might just tell you that C: is full, but I have made
the experience that you have to reproduce a problem several times and
the only reason Windows will _not_ give you for failing is most likely
the reason why it failed.
BTW You must be carefull mentioning The OS That Must Not Be Named in
this here newsgroup. It might build up so much negative energy that
mixed words up get.
SCNR
-- =
Josef M=F6llers (Pinguinpfleger bei FSC)
------------------------------
From: Josef Moellers <[EMAIL PROTECTED]>
Subject: Re: spin locks
Date: Tue, 29 Aug 2000 07:49:28 +0200
Karl Heyes wrote:
> =
> In article <8ocug8$9sv$[EMAIL PROTECTED]>, "Peter Huang"
> <[EMAIL PROTECTED]> wrote:
> > Hi all
> >
> > I'm new at Linux programming and I was suggested by some helpful peop=
le in to
> > use spin locks for things I'm doing. I have Rubini's book on Linux
> > programming but it doesn't cover spin locks since it is a new subject=
=2E Can
> > any one tell me where I can get comprehensive information on spin loc=
ks or
> > can give me some ideas over the net on how to use spin locks.. I woul=
d
> > appreciate it.
> >
> =
> look in linux/Documentation/spinlocks.txt. It's definitely a kernel th=
ing
> though, if that is what you are wanting.
I beg to differ. A slightly different implementation may allow spinlocks
to be used in user land:
do {
result=3Dget_spinlock();
if (result !=3D GOT_SPINLOCK)
yield(); /* Voluntarily give up CPU */
} until (result =3D=3D GOT_SPINLOCK);
You can use it on shared memory segments and it will also work on
uniprocessors. The disadvantages are that you will not have an idle CPU,
so you might need to get that other fan. Also, people will complain
about a 100% busy CPU. If yield() pushes the current process on the end
of the run queue, you will not have a large performance impact.
-- =
Josef M=F6llers (Pinguinpfleger bei FSC)
------------------------------
From: [EMAIL PROTECTED] (Koch)
Subject: SOLVED! Re: Kernel panic: VFS:
Date: Tue, 29 Aug 2000 05:34:06 GMT
Reply-To: [EMAIL PROTECTED]
>Q1. What item or option shuld I select?
I have got it by checking options as show below.
# I use (and only) SCSI HDD.
============================
old new
============================
SCSI driver "M" "*"
ext2fs "M" "*"
============================
Thank you.
koch
------------------------------
From: "Ross Crawford" <[EMAIL PROTECTED]>
Subject: Re: where is "make" in linux
Date: Tue, 29 Aug 2000 14:33:28 +1000
Josef,
I was referring to the quote from the previous post:
"I end up reinstall the latest version of RedHat, which solved the problem."
This seems to be the solution for most Windoze problems as well. (Re-install
latest version, not necessarily RedHat!!)
Regards,
ROSCO
"Josef Moellers" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
Ross Crawford wrote:
>
> Is this sounding more & more like a Windoze solution?
While I would be hard pressed to use the words "Windows" and "make" and
"kernel generation" in one sentence ... no, this does not sound more &
more like a Windoze solution.
It _may_ sound like a Windoze solution, if it were a Windoze problem
with Windoze symptoms:
1. Windows does not have "make" and you certainly cannot generate your
own kernel.
2. (and more important) Windoze will not give you any clue whatsoever
that "make" might be missing. It would probably tell you something about
missing interface lines on COM1 or it would just crash. Under ideal
circumstances, it might just tell you that C: is full, but I have made
the experience that you have to reproduce a problem several times and
the only reason Windows will _not_ give you for failing is most likely
the reason why it failed.
BTW You must be carefull mentioning The OS That Must Not Be Named in
this here newsgroup. It might build up so much negative energy that
mixed words up get.
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list (and comp.os.linux.development.system) via:
Internet: [EMAIL PROTECTED]
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Development-System Digest
******************************
