Linux-Development-Sys Digest #247, Volume #8 Tue, 31 Oct 00 11:13:18 EST
Contents:
Re: Debugging Modules (Jean-Francois MOINE)
Re: Bootsector Question (Josef Moellers)
Re: visual process management tool for linux (Josef Moellers)
Re: source code.. (Josef Moellers)
Linux Software RAID problems (Borries Demeler)
Compress RAM filesystem question
Re: Advansys SCSI gives kernel oops (Kasper Dupont)
Re: Linux and PXE (Kasper Dupont)
Re: basic question(s) on libc5 vs. libc6 (Richard Zidlicky)
Re: Linux and PXE (Kasper Dupont)
Re: memory usage realloc() (Kasper Dupont)
Re: looking for (Kasper Dupont)
Re: using /linuxrc (Kasper Dupont)
Can I create a floppy with a simple Linux? ("Alan Po")
Where can find the source code for the bash or ash? ("Alan Po")
Re: About Embedded Linux and RAM disk (Kasper Dupont)
Re: Where can find the source code for the bash or ash? (Donovan Rebbechi)
Re: Where can find the source code for the bash or ash? (Josef Moellers)
Re: Bootsector Question (Kasper Dupont)
after compiling kernel 2.4.0-test8 booting won't work (Bart De Schuymer)
Re: visual process management tool for linux (Kasper Dupont)
Re: mouse block (Kasper Dupont)
Re: Multiple groups per file (Kasper Dupont)
Re: System.map problem! (Kasper Dupont)
----------------------------------------------------------------------------
From: [EMAIL PROTECTED] (Jean-Francois MOINE)
Subject: Re: Debugging Modules
Date: 31 Oct 2000 07:59:10 GMT
Oliver Graebner <[EMAIL PROTECTED]> a skrivas:
>Hi Anyone,
[snip]
>I found a command "add-symbol-file FILE ADDR" in the gdb online help but
>I don't know what kind of address I have to fill into ADDR. Am I on the
>right way or does anybody know how to debug modules?
Here is the way I do it.
First, the required packages are:
- gdb-5.0 with the patch below which fixes a problem with the option
-T in add-symbol-file (there may be an other patch at the gdb
home site).
- modutils-2.3.x with x >= 13.
When installing the modules, use the '-Y' option. Ex:
insmod -Y foo
(with modprobe/kmod, put 'insmod_opt=-Y' in /etc/modules.conf)
When gdb is active, search the module in the module_list, then scan
the symbols for '__insmod.*_S.*' (the last '*' is the section name
and the most important ones are 'text', 'data' and 'bss').
Then add the symbol to gdb with:
add-symbol-file <module.o> -T.text <taddr> -T.data <daddr> ...
As it is long when you do that many times, I use an expect script
in front of gdb, and I've just to enter 'zmodule <module_name>'
for all the previous job to be done. If anyone is interested by
this script (<300 lines)...
===========================8<===========================
--- gdb-5.0/gdb/elfread.c.orig Tue Feb 15 05:48:23 2000
+++ gdb-5.0/gdb/elfread.c Wed Jun 28 10:14:19 2000
@@ -293,8 +293,10 @@
if (number_of_symbols < 0)
error ("Can't read symbols from %s: %s", bfd_get_filename (objfile->obfd),
bfd_errmsg (bfd_get_error ()));
+#if 0 /*JFM*/
/* FIXME: Should use section specific offset, not SECT_OFF_TEXT. */
offset = ANOFFSET (objfile->section_offsets, SECT_OFF_TEXT);
+#endif
for (i = 0; i < number_of_symbols; i++)
{
sym = symbol_table[i];
@@ -305,6 +307,9 @@
continue;
}
+#if 1 /*JFM*/
+ offset = ANOFFSET (objfile->section_offsets, sym->section->index);
+#endif
if (dynamic
&& sym->section == &bfd_und_section
&& (sym->flags & BSF_FUNCTION))
===========================8<===========================
--
Ken ar c'henta� ** Breizh ha Linux atav ! **
mailto:[EMAIL PROTECTED]
Jef (home mailto:[EMAIL PROTECTED])
http://moinejf.free.fr/
------------------------------
From: Josef Moellers <[EMAIL PROTECTED]>
Subject: Re: Bootsector Question
Date: Tue, 31 Oct 2000 09:40:24 +0100
@cisco.com wrote:
> =
> Hi,
> =
> I am trying to write a boot sector which does nothing but print a
> string. It does not actually boot anything, it only has that 0xAA55
> signature at the end of the sector. For some reason it does not seem to=
> work. The system recognizes that this is a bootsector but does not prin=
t
Try to get the LILO source code and see how they do it.
Apparently, the boot code is loaded to address 0x7c00, but afair the CS
register is set to 0 and IP is set to 0x7c00.
Again, look into how LILO is generated.
-- =
Josef M=F6llers (Pinguinpfleger bei FSC)
If failure had no penalty success would not be a prize (T. Pratchett)
------------------------------
From: Josef Moellers <[EMAIL PROTECTED]>
Subject: Re: visual process management tool for linux
Date: Tue, 31 Oct 2000 09:42:02 +0100
plato wrote:
> =
> i'm developing a visual process management tool for linux and i have so=
me
> questions:
> =
> 1. how can i get the owner of a process whose pid i have? i use the
> /proc/"pid"/stat file to retrieve information about the process and i d=
on't
> want to have to open /proc/"pid"/status too just to get the user id. so=
If that's the place where the uid is stored, then you have no choice.
> please advise. also i want to know how to get the username of a user wh=
ose
> uid i have.
man getpwuid
The other questions, I can't help you with.
-- =
Josef M=F6llers (Pinguinpfleger bei FSC)
If failure had no penalty success would not be a prize (T. Pratchett)
------------------------------
From: Josef Moellers <[EMAIL PROTECTED]>
Subject: Re: source code..
Date: Tue, 31 Oct 2000 09:51:28 +0100
plato wrote:
> =
> can anyone provide me with the source code for ps or top (process manag=
ement
> tools on linux)?
It should come with your distribution.
top and ps are both in the ps rpm.
-- =
Josef M=F6llers (Pinguinpfleger bei FSC)
If failure had no penalty success would not be a prize (T. Pratchett)
------------------------------
From: Borries Demeler <[EMAIL PROTECTED]>
Subject: Linux Software RAID problems
Date: Tue, 31 Oct 2000 06:17:06 -0600
Reply-To: [EMAIL PROTECTED]
I'm having a devil of a time trying to get Software RAID to
work, but no matter what I try, I can't get it to work. I am trying to
run RAID-0 on 7 identical 1Gig SCSI drives, here is my scenario:
1. Recompiled kernel (2.2.17, raidtools 0.90), with the following
options:
CONFIG_BLK_DEV_MD=y
CONFIG_MD_LINEAR=y
CONFIG_MD_STRIPED=y
CONFIG_MD_MIRRORING=y
CONFIG_MD_RAID5=y
CONFIG_MD_BOOT=y
Also tried:
CONFIG_BLK_DEV_MD=y
CONFIG_MD_LINEAR=m
CONFIG_MD_STRIPED=m
CONFIG_MD_BOOT=m
2. deleted all partitions on each drive, and recreated a single
partition
of type "fd" spanning the entire disk on each drive.
3. Set up /etc/raidtab:
raiddev /dev/md0
raid-level 0
nr-raid-disks 7
persistent-superblock 1
chunk-size 8 (also tried 4)
device /dev/sdc1
raid-disk 0
device /dev/sdd1
raid-disk 1
device /dev/sde1
raid-disk 2
device /dev/sdf1
raid-disk 3
device /dev/sdg1
raid-disk 4
device /dev/sdh1
raid-disk 5
device /dev/sdi1
raid-disk 6
After loading the modules, I got:
/proc/mdstat:
Personalities : [2 raid0]
read_ahead not set
md0 : inactive
md1 : inactive
md2 : inactive
md3 : inactive
When running monolithically, I get:
Personalities : [1 linear] [2 raid0] [3 raid1] [4 raid5]
read_ahead not set
md0 : inactive
md1 : inactive
md2 : inactive
md3 : inactive
When running mkraid /dev/md0, I get:
mkraid /dev/md0
handling MD device /dev/md0
analyzing super-block
disk 0: /dev/sdc1, 1027056kB, raid superblock at 1026944kB
disk 1: /dev/sdd1, 1027056kB, raid superblock at 1026944kB
disk 2: /dev/sde1, 1027056kB, raid superblock at 1026944kB
disk 3: /dev/sdf1, 1027056kB, raid superblock at 1026944kB
disk 4: /dev/sdg1, 1027056kB, raid superblock at 1026944kB
disk 5: /dev/sdh1, 1027056kB, raid superblock at 1026944kB
disk 6: /dev/sdi1, 1027056kB, raid superblock at 1026944kB
mkraid: aborted, see the syslog and /proc/mdstat for potential clues.
Well, no info is written to /var/log/syslog, and I don't know why it is
aborting.
I started debugging mkraid to see where the error comes from, and it
boils down to a failed ioctl call, since I am not a system programmer,
I really don't know where to go from there. Here is what I have come up
with so far: I traced the problem to a failed ioctl call in line 46:
ret = ioctl(file, SET_ARRAY_INFO, (unsigned long)&cfg->array.param);
Here are the parameters:
file: 4, SET_ARRAY_INFO: 1078462755, &cfg->array.param: 134547136 ioctl
returned -1 in line 46: Invalid argument (printing out strerror(errno))
called in makeOneRaid in line 225 (I think they are supposed to be long
int's).
Not knowing much about the ioctl call, I can't interpret the int values
and tell what's wrong about them. Do you have any further clues? Maybe
I am missing something really obvious - hopefully?
Thanks for any suggestions you may be able to offer, -Borries
P.S. If you could copy your answer to [EMAIL PROTECTED], I
would really appreciate it
------------------------------
From: [EMAIL PROTECTED] ()
Subject: Compress RAM filesystem question
Date: 31 Oct 2000 10:01:20 GMT
hi Sir
I have a question about the very new filesystem , compress RAM filesystem.
Could it be possible to make a cramdisk as a root filesystem ?
Does anyone have the experence about this ?
Thank you very much...
------------------------------
From: Kasper Dupont <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.hardware
Subject: Re: Advansys SCSI gives kernel oops
Date: Tue, 31 Oct 2000 14:47:32 +0100
Philip Armstrong wrote:
>
[...]
>
> You could try putting the oops through ksymoops and posting it to
> linux-kernel. But it's more likely to be a hardware problem. Is the
> scsi bus terminated? Have you tried each drive individually?
>
> Something is probably corrupting filesystem data and feeding duff data
> to the kernel.
>
[...]
Neither the suggested hardware problem nor
corrupt filesystem data should cause an oops.
But since theese things are hard to test and
since they don't happen that frequently a
kernel bug might be the explanation.
--
Kasper Dupont
------------------------------
From: Kasper Dupont <[EMAIL PROTECTED]>
Subject: Re: Linux and PXE
Date: Tue, 31 Oct 2000 15:02:46 +0100
Andi Kleen wrote:
>
> Kasper Dupont <[EMAIL PROTECTED]> writes:
>
> > Andi Kleen wrote:
> > >
> > [...]
> > >
> > > Don't try. It'll crash and burn. APM is a special case and only
> > > works because APM is spec'ed for protected mode calls and the call
> > > code does some careful segment switching for it.
> > >
> > > The only way to call BIOS code is via the vm86 mode, but even that
> > > is quite tricky and requires considerable setup.
> > >
> > > -Andi
> >
> > That call I was mentioning is done in real
> > mode. If the CPU is in real mode and the
> > first 2KB is untouched i cannot see how
> > anything can go wrong. What can go wrong?
>
> Hardware is in a state the BIOS does not expect it to. To make the BIOS work
> you need a quite good virtual machine, e.g. as in dosemu (which even has
> to emulate most BIOS calls because they're hopeless)
>
> -Andi
I have looked a little bit further into this.
I found two sources of problems:
1. The interrupt vectors might have been
changed before Linux is started, that
for instance happens if you boot Linux
using LOADLIN, the interrupt vectors
will be pointing to DOS code which has
been overwritten.
2. The hardware is in some strange state.
Problem 1 can be solved either by using a
loader without this problem like LILO. Or
by suplying replacement code, or by not
using the interrupts.
Problem 2 can be solved by seting the
hardware into the right state. The IRQ
controller can be done with 10 port writes,
the timer can be done with less. And
graphics hardware with can be done with a
BIOS call. This is possible, you just have
to be carefull not to forget something.
--
Kasper Dupont
------------------------------
From: [EMAIL PROTECTED] (Richard Zidlicky)
Subject: Re: basic question(s) on libc5 vs. libc6
Date: 31 Oct 2000 14:28:35 GMT
In <[EMAIL PROTECTED]> [EMAIL PROTECTED] (Christopher
Browne) writes:
>In our last episode (Tue, 17 Oct 2000 01:26:24 GMT),
>the artist formerly known as Johan Kullstam said:
>>[EMAIL PROTECTED] (B'ichela) writes:
>>
>>> On Mon, 16 Oct 2000 05:36:12 -0000, [EMAIL PROTECTED]
>>> <[EMAIL PROTECTED]> wrote:
>>> >If you have 30 processes linked to libc5 and 40 processes linked to
>>> >libc6 you have the libraries taking up at most the space of both
>>> >just once. That is, as long as everything is shared. We're talking
>>> >about less than a meg of memory for libc5, and that isn't a problem
>>> >at least on today's machines of 64 meg and larger. Of course if you
>>> >are still running on that old 8 meg 386, that's another issue.
>>> Being one of those people who still uses a 486 DX2/66 with
>>> 20mb of ram as well as two 486 DX/33 8mb client machines. bigger libs
>>> hurt my system badly. thats why I never moved up from kernel 2.0.38 on
>>> slackware 3.9. I don't have the memory to throw around. How big is
>>> libc5 vs libc6 anyway?
>>
>>on the gripping hand, libc5 is dead and has been dead for something
>>like two years now. this means no development, no bug fixes, not even
>>security fixes afaik.
>Yes, and while it may not be of immediate interest here, libc5 solely
>runs on IA-32. It _may_ have worked on Alpha, for a brief period, but
>that may be apocryphal. And there are quite a lot of apps needing to run
>on architectures other than IA-32.
libc also run on linux-m68k for quite some time, as did libc4
Bye
Richard
------------------------------
From: Kasper Dupont <[EMAIL PROTECTED]>
Subject: Re: Linux and PXE
Date: Tue, 31 Oct 2000 15:22:37 +0100
[EMAIL PROTECTED] wrote:
>
> In my scenario, PXE is allowed to boot before the hard disk. So, if I
> allow reset to happen, the PXE code will always run first, and then
> download the stuff off the network, and the hard disk code will never
> get executed. My main problem, is how to tell PXE not to run the next
> time.
>
[...]
I don't know exactly how this PXE thing works, but here
are some ideas:
If the PXE modifies the CPU state or some other hardware
state that must be restored. I.e. the CPU must be in
real mode the timer must be 18.2 Hz the IRQ controllers
must use 0x08-0x0f and 0x70-0x77 etc.
If the PXE modifies the interrupt vectors theese must be
restored, if the PXE uses some kind of OS it might be
necesarry to get some code executed before that to save
the interrupt vector table.
After that you must somehow continue the standard boot
process. I don't know exactly where in the boot process
the PXE starts, but if it happens in the periode where
int 18h and 19h is usable the following piece of code
should do it:
CLI
XOR AX,AX
MOV DS,AX
MOV SS,AX
MOV ES,AX
MOV SP,7C00
STI
MOV AX,0201
MOV BX,7C00
MOV CX,0001
MOV DX,0080
INT 13
JMP 0:7C00
This code does the same as int 19h would do if drive C
was the only drive. This piece of code is similar to
what I previously posted. There are one thing that
must be remembered, if the code is located within the
range 7B00-7E00 it could be overwritten by the stack
or the MBR loaded from the harddisk, in that case it
must move itself to another location. Taking a look on
the standard MBR code could help with some inspiration,
it is so small that it is feasible to disasemble and
understand.
It could be that int 18h or int 19h would do the trick,
but it might do something other than expected.
--
Kasper Dupont
------------------------------
From: Kasper Dupont <[EMAIL PROTECTED]>
Subject: Re: memory usage realloc()
Date: Tue, 31 Oct 2000 15:32:28 +0100
[EMAIL PROTECTED] wrote:
>
[...]
>
> I don't agree with you, because if the older memory is freed
> automatically, why it's still possible to access it, store value in it?
>
> Or it's because Linux will take some time to really "free" the memory,
> not right after the free() call?
>
> thanks!
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Maybee you don't agree, but that is what the ansi C
standard says. When you access memory that has been
freed you are breaking the rules. The system will
not hit you every time you break the rules, if you
want to be hit every time you break a rule there
are tools you can use.
A simple tool is electric fence which you can use
simply by using a -lefence option when compiling.
Another more advanced tool is purify, but I don't
know if it is available for Linux.
Using theese tools is good when debuging it will
help find bugs like the one you are having. They
are however not usefull when the program finally
is to be used.
--
Kasper Dupont
------------------------------
From: Kasper Dupont <[EMAIL PROTECTED]>
Subject: Re: looking for
Date: Tue, 31 Oct 2000 15:44:16 +0100
Karl Heyes wrote:
[...]
>
> > * system programming ( how to us the ROM BIOS interrupts for
> > example).
>
> limited access, none for non-root user.
>
[...]
ROM BIOS interrupts does not exist when runing Linux.
They are only used inside the kernel and that is only
for APM and some obscure drivers, that should be
rewritten as soon as posible.
--
Kasper Dupont
------------------------------
From: Kasper Dupont <[EMAIL PROTECTED]>
Subject: Re: using /linuxrc
Date: Tue, 31 Oct 2000 15:51:54 +0100
Peter Pointner wrote:
>
[...]
>
> My /linuxrc does not execute init. init never gets started, I simply don't
> need it for this embedded system.
>
> Peter
It would probably be a better idea not to
use the initrd feature. Instead you should
just use your ramdisk as root and rename
your linuxrc to /sbin/init.
Or perhaps even better use init and modify
/etc/inittab so it just calls your program.
You could then make use of the respawn
feature. Of course if your diskspace is
extremly thight that might not work.
--
Kasper Dupont
------------------------------
From: "Alan Po" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development.apps,comp.os.linux.questions
Subject: Can I create a floppy with a simple Linux?
Date: Tue, 31 Oct 2000 23:06:22 +0800
Dear All
I want to create a simple Linux which boot from a floopy. For this Linux, I
only need a shell and simple login. No need to run any other application. Is
it possible?
Please give me some advice. Thanks a lot
Alan Po
[EMAIL PROTECTED]
------------------------------
From: "Alan Po" <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.development.apps,comp.os.linux.misc,comp.os.linux.questions
Subject: Where can find the source code for the bash or ash?
Date: Tue, 31 Oct 2000 23:13:23 +0800
Dear all
Where can I find the source code for the bash? When the bash start? Can I
select another shell at the boot time?
Thanks a lot.
Alan Po
------------------------------
From: Kasper Dupont <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development.apps
Subject: Re: About Embedded Linux and RAM disk
Date: Tue, 31 Oct 2000 16:19:30 +0100
root wrote:
>
> Dear sir
>
> I have tried to develop an Embedded Linux by using Red Hat EDK. However,
> this tool have a lot of problem. The most important thing is how to
> build a floppy which put a tiny linux into it. As studying the other
> small linux, they usually a RAM disk. Where can I get some information
> about creating a floppy with a small linux (not a distribution, by
> manual)? How to create a RAM disk on my machine?
>
> Please give me some advices and thanks a lot.
>
> Alan Po
> [EMAIL PROTECTED]
I think there is a howto on the subject.
Take a look in /usr/doc/HOWTO.
Quickstart:
You can make a ramdisk with the command
mke2fs /dev/ramXX
where XX is a number in the range 0-15.
You can mount the device as normal with
mount /dev/ramXX /mnt/ramdisk
if you have an empty directory named
/mnt/ramdisk.
You can copy the files you need onto
this media. The most important files are
/dev/console and /sbin/init.
The console is needed to get output to
whatever your console is. It is a char
special file so it takes up practically
no diskspace. The init file is the program
being started by the kernel. The one used
normally reads /etc/inittab to know what
to start, it then watches programs stoping
and respawn them it /etc/inittab tells it
to.
When the ramdisk is ready umount it. You
can then compress it with this command:
gzip </dev/ram9 >ramdiskfile.gz
--
Kasper Dupont
------------------------------
From: [EMAIL PROTECTED] (Donovan Rebbechi)
Crossposted-To:
comp.os.linux.development.apps,comp.os.linux.misc,comp.os.linux.questions
Subject: Re: Where can find the source code for the bash or ash?
Date: 31 Oct 2000 15:21:33 GMT
On Tue, 31 Oct 2000 23:13:23 +0800, Alan Po wrote:
>Dear all
>
>Where can I find the source code for the bash?
http://www.gnu.org
> When the bash start? Can I
When you log in.
>select another shell at the boot time?
after you login, use
chsh
--
Donovan
------------------------------
From: Josef Moellers <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.development.apps,comp.os.linux.misc,comp.os.linux.questions
Subject: Re: Where can find the source code for the bash or ash?
Date: Tue, 31 Oct 2000 16:39:27 +0100
Donovan Rebbechi wrote:
> On Tue, 31 Oct 2000 23:13:23 +0800, Alan Po wrote:
[ ... ]
> >select another shell at the boot time?
> =
> after you login, use
> chsh
As an alternative, you can ask your system administrator to change your
entry in the password file (that's where your default shell name is
stored).
There is also the "chsh" command which will ask for your own password
and will allow you to set a new shell for your own account.
-- =
Josef M=F6llers (Pinguinpfleger bei FSC)
If failure had no penalty success would not be a prize (T. Pratchett)
------------------------------
From: Kasper Dupont <[EMAIL PROTECTED]>
Subject: Re: Bootsector Question
Date: Tue, 31 Oct 2000 16:37:25 +0100
@cisco.com wrote:
>
> Hi,
>
> I am trying to write a boot sector which does nothing but print a
> string. It does not actually boot anything, it only has that 0xAA55
> signature at the end of the sector. For some reason it does not seem to
> work. The system recognizes that this is a bootsector but does not print
>
> the string.. Can someone please help me with
> this. I have been spending quite sometime on this as i am not very
> familiar with assembly language. The code
> is pasted below.
>
> I compile this with gcc -c file.s command, and from the resulting object
>
> file, i seperate the code segment
> machine instructions and copy to the floppy. I did a objdump -d on the
> resultnig. file.o file and compared the
> bytes with the one in the floppy and looks like they are same. So, i am
> confident that i am seperating the machine instructions properly from
> the .o file. Please reply to [EMAIL PROTECTED]
>
> Thanks in advance,
> Sarat
>
> .text
> .globl boot
>
> BOOTSEG = 0x7C0
> boot:
> /* This instruction sets the CS to 0x7c00 and EIP to start
> label. Atleast thats what i feel */
> ljmp $BOOTSEG, $start
> start:
> /* set up es register */
> mov $BOOTSEG, %ax
> mov %ax, %es
>
> /* read the current cursor position */
> movb $0x03, %ah
> xor %bh, %bh
> int $0x10
>
> /* %dh, %dl are set by now. write the string now */
> mov $0x1301, %ax
> mov $0x0007, %bx
> mov $0x9, %cx
> mov $msg, %bp
> int $0x10
> msg:
> .ascii "\r\nHello\r\n"
> .org 510
> .word 0xAA55
The boot sector is loaded at 0:7C00, and the
BIOS jumps to that code. 7C0:0 is another
valid address for the same code, but you don't
have to do any jumping on your own.
But the main problem probably is that gcc output
code for 32bit protected mode, you should add
.code16 in the start of the source code.
--
Kasper Dupont
------------------------------
From: [EMAIL PROTECTED] (Bart De Schuymer)
Subject: after compiling kernel 2.4.0-test8 booting won't work
Date: Tue, 31 Oct 2000 15:46:17 GMT
Hello,
My default kernel is the one delivered by Redhat 7.0...
I have recompiled my kernel with the latest linux sourcecode
(downloaded it).
I put the bZimage under /boot and adjusted /etc/lilo.conf and executed
lilo.
in menuconfig I chose everything from firewall and net stuff and chose
all scsi drivers (as I have a scsi hard disk and don't know the
properties). I don't believe I have forgotten to include something.
When I boot and choose this new kernel I get the usual
loading linux .............
uncompressing linux... done.
But then it hangs...
I looked at the version numbers and these are lower:
insmod : 2.3.14 instead of 2.3.15
kbdrate : 2.10m instead of 2.10o
pppd : 2.3.11 instead of 2.4.0
Maybe this is the problem? If so, where do I find the updates?
Thanks,
Bart
------------------------------
From: Kasper Dupont <[EMAIL PROTECTED]>
Subject: Re: visual process management tool for linux
Date: Tue, 31 Oct 2000 16:46:47 +0100
plato wrote:
>
> i'm developing a visual process management tool for linux and i have some
> questions:
There is some library named proclib which might
help you, but I don't know much about it.
>
> 1. how can i get the owner of a process whose pid i have? i use the
> /proc/"pid"/stat file to retrieve information about the process and i don't
> want to have to open /proc/"pid"/status too just to get the user id. so
> please advise. also i want to know how to get the username of a user whose
> uid i have.
You can check the userid of the /proc/<pid> directory.
>
> 2. this is a gtk+ question. i need to know what signals are sent for a right
> mouse button click. i've looked everywhere and i can't seem to find anything
> useful.
>
> 3. how do i convert jiffies to any practical time unit (seconds, for
> instance)?
Divide by the HZ constant for the current kernel.
Proclib finds that by reading /proc/uptime and
/proc/stat, it then divides the uptime meassured
in jiffies by the number of timer interrupts.
>
> please someone answer quickly as this is very urgent..
>
> thanks all.
--
Kasper Dupont
------------------------------
From: Kasper Dupont <[EMAIL PROTECTED]>
Subject: Re: mouse block
Date: Tue, 31 Oct 2000 16:59:59 +0100
Chen Yung-Mu wrote:
>
> Hi all ,
> We can usr mouse to block some word or command to copy post .
> Does it use a buffer to storage those word or command when we block
> somethimg ?
> If I want get those word or command in the buffer , how can I do ?
> I know it is something about gpm . But I don't know which function call
> can get this buffer and I
> can read it .
I think the buffer is actually stored in the kernel,
gpm I think just calls some ioctl on the tty. I don't
think reading and writing this buffer is supported,
but you could probably open eg. /dev/tty63 and write
to the tty and cut it, similar you could paste the
buffer to that tty and read it. That is an ugly way
to do it, but I don't know any other solution.
--
Kasper Dupont
------------------------------
From: Kasper Dupont <[EMAIL PROTECTED]>
Subject: Re: Multiple groups per file
Date: Tue, 31 Oct 2000 16:55:36 +0100
Jeff Walters wrote:
>
> Robert Redelmeier <[EMAIL PROTECTED]> wrote:
> > 'Scuse my ignorance, but why would you want multiple groups
> > per file? Can't you just create new groups that are the
> > appropriate union sets of users? I don't know if /etc/group
> > will accept group names to make this easier. (groups of groups)
>
> > -- Robert
>
> Multiple groups per file would let you create one group with read-only
> and another with read-write on the same file. Create a union set and
> you still have to decide if they all get read-only or all read-write.
>
> ACL's basically are trying to do the same thing. They were good on
> VMS, but seem like overkill when you're just trying to set up three
> simple permission bits. The current Unix model does 99% of what you
> want except allowing more than one "group" of people unique
> permissions on the same file.
>
> --
> Message of the Message:
> It is now pitch dark. If you proceed, you will likely fall into a pit.
Perhaps this idea might help you:
Create two groups readers and writers
where writers is a subset of readers.
Make a directory owned by readers
with permitions drwxr-x---, in that
directory make another directory
owned by writers with permitions
drwxrwxr-x.
If you don't want to type the full
path every time use a symbolic
link.
This idea might be extended and
automated to some extend.
--
Kasper Dupont
------------------------------
From: Kasper Dupont <[EMAIL PROTECTED]>
Subject: Re: System.map problem!
Date: Tue, 31 Oct 2000 16:51:22 +0100
John Hall wrote:
>
> This is probably pretty simple;
>
> 2 things:
>
> First; to overcome lilo limitations, and to "protect" your kernel, RedHat
Actually it is BIOS limitations.
> cleverly has your system boot from a small [probably 25 megs or so]
> partition. This partition has to be at the beginning of the hard disk. The
> boot partition is mounted in /boot when you're booting up, but then it is
> likely unmounted so you can't accidentally make changes to it or delete it.
Is it really unmounted? That sounds like a stupid idea.
Remounting read only on the other hand might be a good
idea, but as long as you don't login as root even that
wouldn't be necesarry.
> Make sure when you're copying these files to /boot _when it's mounted_ and
> not just the "boot" folder in your root partition. Look in /etc/fstab to see
> how /boot is mounted. [obviously the first thing you should do is type mount
> by itself to see if anything is mounted into /boot]
>
[...]
--
Kasper Dupont
------------------------------
** 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
******************************
