Linux-Development-Sys Digest #107, Volume #8 Mon, 28 Aug 00 17:13:16 EDT
Contents:
Re: root password ("Alexei Sinitsyn")
Re: "Best" x86 Linux C/C++ compiler?? (Marco van de Voort)
Re: kernel compiles root device as (3,65); boots for (3,41) (M. Buchenrieder)
"xtime" and "jiffies" (Marco Fabiani)
Q: SMP question (Holger Eitzenberger)
Re: programming nvidia on linux (Wolfgang Draxinger)
Re: SMP question ("Tristan Wibberley")
Re: where is "make" in linux ("Paul D. Smith")
Re: Any substitution for _msize( ) (Rimas)
Re: Any substitution for _msize( ) (Kaz Kylheku)
Re: Any substitution for _msize( ) (Kaz Kylheku)
Re: Q: SMP question (Kaz Kylheku)
lilo options ("Christos Karayiannis")
Re: purify and memory managers (James R. Van Zandt)
Re: lilo options ("Jan Welti")
Re: where is "make" in linux
Re: lilo options ("Christos Karayiannis")
Re: lilo options ("Christos Karayiannis")
lilo options ("Christos Karayiannis")
----------------------------------------------------------------------------
From: "Alexei Sinitsyn" <[EMAIL PROTECTED]>
Subject: Re: root password
Date: Mon, 28 Aug 2000 12:23:55 +0400
> 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
------------------------------
From: [EMAIL PROTECTED] (Marco van de Voort)
Subject: Re: "Best" x86 Linux C/C++ compiler??
Date: 28 Aug 2000 08:48:48 GMT
>>In article <[EMAIL PROTECTED]>, Martin von Loewis wrote:
>>>"H.W. Stockman" <[EMAIL PROTECTED]> writes:
>>>
>>>> I'd truly like to see comparable performance.
>>>
>>>I believe at the moment, there is no other choice but gcc on
>>>Linux. With some effort, you may be able to find a copy of lcc, but I
>>>have no idea which would perform better.
>>>
>>>There is also The Portland Group CC, http://www.pgroup.com; I don't
>>>have any performance information on that compiler, either.
>>
>>Afaik C++ buider will follow in Q1 next year.
>
>Keep in mind that Linux is an operating system kernel that runs on IA-32,
>IA-64, Alpha, Sparc, PowerPC, PA-RISC, StrongARM, MIPS, and other
>architectures.
Yup.
>A compiler that cannot generate code for at least that set of platforms
>is crippled, only really applicable to specially targeted embedded
>applications.
No. It can be used to create applications too. Afaik, it is even specially
targeted at such development.
------------------------------
Crossposted-To: comp.os.linux.misc
From: [EMAIL PROTECTED] (M. Buchenrieder)
Subject: Re: kernel compiles root device as (3,65); boots for (3,41)
Date: Mon, 28 Aug 2000 06:49:28 GMT
[Note FollowUp-To: header]
xavian anderson macpherson <[EMAIL PROTECTED]> writes:
>i didn't make up the fact about suse using a different filesystem location
>method.
Please show me where I accused you of doing so.
>THAT WAS ACTUALLY TOLD TO ME BY A SUSE SUPPORT PERSON, AS BEING
>(WHAT I CONSIDERED AN ILLEGITMATE)
You could read that in the SuSE manual as well. But that's not
the point here. Fact is, there is no such thing as an "accepted
industry standard" as far as file system locations are concerned.
There _is_, however, the FSSTND - which SuSE actually does better
conform with than RedHat does.
>reason for not allowing you to use yast
>for installing rpm's from other ftp sites.
This is pointless. YAST is a SuSE-specific tool for use with
their distribution. Whether or not you may be able to use it
with RPMs from different sources does depend from the RPM
you're trying to install. And even if it doesn't work, you
could still be using "rpm" to install it. Duh.
>the fact is, that it shouldn't
>make any difference if your using the same filesystem. so if you don't
>like my remarks, speak to suse.
Your remarks don't make much sense. Speaking to SuSE about a problem
that is simply a lack of common sense on your part won't help much.
>the fact is that they use different case/spellings for packages that
>everyone else seems to have agreed on.
Nobody agreed on anything. If the name of a package is the same in
2 or more distributions, this is just by chance. There is absolutely
no guarantee that a package is supposed to contain the exact same
contents in different distributions - nor being named the same.
[...]
>(if suse's packaging were no different than anyone else's, you would see
>their recent packages posted right along with everyone else's. they're
>not. only the old ones! i often find redhat, linux-mandrake and kondura's
>all on the same page.)
?
Sorry, I can't parse this.
>this results in software not being easily or properly upgraded when you
>want to change from an i386 to i586 package.
Rubbish. You deinstall the old one, and install the new one. I've
been upgrading Linux systems for years now; and the worst error I
ever encountered was that sometimes not all the packages were
installed correctly due to library problems. But the missing packages
were easily to be added after checking the resulting logfiles.
>there is absolutely no
>justification for this. if the packages produced by suse were not
>proprietary, why else would they make it so difficult to change their
>system.
They don't. I've been using SuSE since 4.1, continually upgrading
about once a year. No problem.
[...]
>i installed some packages last wednesday. i noticed some buggy results.
Possible. Depends from what you installed - and what you missed.
>so i turned off my computer and went to bed.
Smart.
[...]
>fortunately i had contacted a
>packager for linux-mandrake the day before, and we traded phone numbers.
>if i had not have done this, i would have never figured out how to fix what
>had happened, because i couldn't get my ethernet card to be registered by
>the system. this meant that i couldn't get any help from the internet.
>this guy spent 4 hours and 47 minutes on the phone with me on friday
>night.
You could have rebuilt the whole system (not that this would have
been needed) within one hour.
>we finanly got most the system back to where i could work with it.
>but many of the things that he thought should be there, weren't. they were
>either in different locations, or didn't exist at all. so what were you
>saying about my angst with suse?
Nothing. You can't expect to have a RedHat packager knowing the
FSSTND - which they don't follow. This is like asking a Chrysler
technician for to repair your Dodge. He will be able to find the
engine and the tires, but not more.
>i recently reinstalled the suse base.rpm, which is the equivalent to the
>standard basesystem.rpm.
You should never have to do this, unless you manually messed
up the base system by installing different versions of the same
programs and/or libraries. If you did, then you're on your own.
YAST (or Debian's packet manager or...) can only deal with the
set of preconfigured packages that the distributor had placed
together and compiled with the appropriate libraries. If you
start fiddling around with RPMs or packages from
third party sources, then you do have to take the appropriate steps
to make them conforming to your system's layout - which includes
fixing the paths and compiling against the available library
version (in case of program sources).
>in the process of reinstalling this base.rpm,
>yast removed the package grep which i had installed to satisfy the
>dependecies of some other non-suse packages.
[...]
You actually messed up the dependencies. What did you expect?
Michael
P.S.: This does have nothing to do with colds - please
respect the FollowUp-To: header.
--
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.
------------------------------
From: Marco Fabiani <[EMAIL PROTECTED]>
Subject: "xtime" and "jiffies"
Date: Mon, 28 Aug 2000 13:23:48 +0200
Hello,
if I understood good the global xtime and jiffies variables contains the
current
time but with two different measurement. The first one with "struct
timeval" and the second one meauseres the time in "jiffies". Is it true?
How can I convert a "struct timeval" variable in "jiffies"?
How can I yield the difference between two "struct timeval" variables?
I need to do this inside a kernel module.
Thanks.
marco
------------------------------
From: [EMAIL PROTECTED] (Holger Eitzenberger)
Subject: Q: SMP question
Date: 28 Aug 2000 13:18:19 GMT
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? My coleague is pretty sure that a process on
Linux always runs on the same CPU.
Holger
------------------------------
From: Wolfgang Draxinger <[EMAIL PROTECTED]>
Crossposted-To:
alt.comp.periphs.videocards.nvidia.programming,alt.comp.periphs.videocards.nvidia,comp.os.linux.development.apps,comp.os.linux.x
Subject: Re: programming nvidia on linux
Date: Mon, 28 Aug 2000 15:33:22 +0200
Stephen Perez schrieb:
> Hi. I am wondering if anyone out there has an example piece of code that
> does all the low-level stuff to change graphics modes, color a pixel on the
> screen, and return to text mode(from a linux console). I could and have
> looked at the nvidia drivers that come with X but I would really like a more
> minimal/simple example than a full blown driver(they rely on X for too many
> things-making it difficult to trace). Also, I don't want to use X(or install
> it for that matter), I just want to do some simple rendering using my nvidia
> TNT2 card. Anyway, just wondering.
>
> Thanks in advance. Please email me directly.
>
> Stephen
I assume you don't want to use the accelerator.
try svgalib. There are some excelent tutorials.
C.U.
------------------------------
From: "Tristan Wibberley" <[EMAIL PROTECTED]>
Subject: Re: SMP question
Date: Mon, 28 Aug 2000 14:53:20 +0100
Holger Eitzenberger wrote in message ...
>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? My coleague is pretty sure that a process on
>Linux always runs on the same CPU.
The operating system knows and decides. Processes will be put onto a
processor by the Linux kernel to try to make the system go as fast as it
can - it will often put them onto the same processor to keep the data
already in the cache useful but it may put them on a different processor.
The process itself can't know in advance which processor it will be on.
--
Tristan Wibberley
------------------------------
From: "Paul D. Smith" <[EMAIL PROTECTED]>
Subject: Re: where is "make" in linux
Date: 28 Aug 2000 10:07:07 -0400
Reply-To: [EMAIL PROTECTED]
%% <[EMAIL PROTECTED]> writes:
c> Thank you for the help. Could you further explain what to do with
c> the source code?
Compile it.
Instructions are included in the distribution. See the README and
INSTALL files.
--
===============================================================================
Paul D. Smith <[EMAIL PROTECTED]> Find some GNU make tips at:
http://www.gnu.org http://www.paulandlesley.org/gmake/
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
------------------------------
From: Rimas <[EMAIL PROTECTED]>
Subject: Re: Any substitution for _msize( )
Date: Mon, 28 Aug 2000 15:42:09 +0200
[EMAIL PROTECTED] wrote:
>
> Hi Friends,
> I am new to Linux 'C' Programming. Well can anyone Please
> tell me how can we find the size of a block malloced in my program. In
> NT environment I am using _msize() to find the size. I searched thru
> the system calls in Linux but could not find any such function.
>
system calls are irrevelant since heap is implemented in user-space.
Better look at
size_t malloc_usable_size (void*)
in /usr/include/malloc.h
--
Rimas
------------------------------
From: [EMAIL PROTECTED] (Kaz Kylheku)
Subject: Re: Any substitution for _msize( )
Reply-To: [EMAIL PROTECTED]
Date: Mon, 28 Aug 2000 14:35:28 GMT
On Mon, 28 Aug 2000 06:46:18 GMT, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
>Hi Friends,
> I am new to Linux 'C' Programming. Well can anyone Please
>tell me how can we find the size of a block malloced in my program. In
>NT environment I am using _msize() to find the size.
There is no function in ANSI C or POSIX for doing this. You are relying on a
non-portable MSVC extension that you should get rid of. IMHO, it does nothing
useful. In all my years of C programming, I have never come across the need for
a function that reports how big a malloced object is. To determine the size of
a dynamic array, one would make make the size field part of its representation.
Note that _msize doesn't report back the same value that the program specified
in the allocation request, but rather it can report the actual size of the
allocated object, which could be larger. So it doesn't properly answer
the question ``how big is the object that I allocated''.
--
Any hyperlinks appearing in this article were inserted by the unscrupulous
operators of a Usenet-to-web gateway, without obtaining the proper permission
of the author, who does not endorse any of the linked-to products or services.
------------------------------
From: [EMAIL PROTECTED] (Kaz Kylheku)
Subject: Re: Any substitution for _msize( )
Reply-To: [EMAIL PROTECTED]
Date: Mon, 28 Aug 2000 14:41:24 GMT
On Mon, 28 Aug 2000 15:42:09 +0200, Rimas <[EMAIL PROTECTED]> wrote:
>[EMAIL PROTECTED] wrote:
>>
>> Hi Friends,
>> I am new to Linux 'C' Programming. Well can anyone Please
>> tell me how can we find the size of a block malloced in my program. In
>> NT environment I am using _msize() to find the size. I searched thru
>> the system calls in Linux but could not find any such function.
>>
>
>system calls are irrevelant since heap is implemented in user-space.
>
>Better look at
>
>size_t malloc_usable_size (void*)
Better not. It's not a portable function, and is not discussed in any
glibc documentation. At least _msize is described in MSDN, so it is
a documented extension.
For all you know, it could disappear from some future release of the library.
--
Any hyperlinks appearing in this article were inserted by the unscrupulous
operators of a Usenet-to-web gateway, without obtaining the proper permission
of the author, who does not endorse any of the linked-to products or services.
------------------------------
From: [EMAIL PROTECTED] (Kaz Kylheku)
Subject: Re: Q: SMP question
Reply-To: [EMAIL PROTECTED]
Date: Mon, 28 Aug 2000 14:44:10 GMT
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: "Christos Karayiannis" <[EMAIL PROTECTED]>
Subject: lilo options
Date: Mon, 28 Aug 2000 19:09:05 +0300
Hi there,
Althought when running /sbin/lilo I see:
added newlinux *
added linux
added dos
only linux appears when I press TAB during the booting. Also what is the
star (*) at the first image?
CK
------------------------------
From: [EMAIL PROTECTED] (James R. Van Zandt)
Subject: Re: purify and memory managers
Date: 28 Aug 2000 12:25:32 -0400
In article <[EMAIL PROTECTED]>,
Paul D. Smith <[EMAIL PROTECTED]> wrote:
>There are a few tools available on Linux for C; I'm not sure about C++.
>You can use dmalloc, which is an old standard. Also, there are patches
>to GCC to allow it to do array bounds checking, which can be useful.
>
>None of these are as easy to use as Purify; since Purify instruments
>your object code you only need to _link_ with it; all the .o's, etc. can
>be compiled normally. Dmalloc et. al. require you to recompile all your
>files to get the best coverage (only very basic coverage is available by
>just linking the dmalloc library).
Electric Fence (efence) works without relinking, by putting a special
shared library at the beginning of the relevant search path.
- Jim Van Zandt
------------------------------
From: "Jan Welti" <[EMAIL PROTECTED]>
Subject: Re: lilo options
Date: Mon, 28 Aug 2000 19:29:06 +0300
The star means that it is the default option.
Why don't you send your /etc/lilo.conf here.
--
The Rules Have Changed...Get Paid to Surf the Web!
http://www.alladvantage.com/go.asp?refid=IRU461
"Christos Karayiannis" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Hi there,
>
> Althought when running /sbin/lilo I see:
>
> added newlinux *
> added linux
> added dos
>
> only linux appears when I press TAB during the booting. Also what is the
> star (*) at the first image?
>
> CK
>
>
------------------------------
From: <[EMAIL PROTECTED]>
Subject: Re: where is "make" in linux
Date: Mon, 28 Aug 2000 17:29:14 GMT
Thanks for everybody's help.
Being an entry level user, I end up reinstall the latest version of RedHat,
which solved the problem.
Regards,
jesse
chengen wrote:
>
> When I try "make menuconfig", I got error message "hash: make: command
not
> found". I also use `find / -name "make"' to search for it, but it returns
> nothing. Could someone please tell me where I can get the "make" command?
> Thanks a lot.
> -jesse
>
> --
> Posted via CNET Help.com
> http://www.help.com/
--
Posted via CNET Help.com
http://www.help.com/
------------------------------
From: "Christos Karayiannis" <[EMAIL PROTECTED]>
Subject: Re: lilo options
Date: Mon, 28 Aug 2000 23:16:29 +0300
Jan Welti asked me to see my /etc/lilo.conf so here it is. As I said the
problem is that only linux comes out during booting which is the original
but second in order in my lilo.conf (the other two labels are newlinux an
expiremental that I put first in the lilo.conf file and dos).
boot=/dev/hda6
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
image=/boot/zImage
label=newlinux
root=/dev/hda6
read-only
image=/boot/vmlinuz-2.0.36-0.7
label=linux
root=/dev/hda6
read-only
other=/dev/hda1
label=dos
table=/dev/hda
------------------------------
From: "Christos Karayiannis" <[EMAIL PROTECTED]>
Subject: Re: lilo options
Date: Mon, 28 Aug 2000 23:18:47 +0300
Jan Welti asked me to see my /etc/lilo.conf so here it is. As I said the
problem is that only linux comes out during booting which is the original
but second in order in my lilo.conf (the other two labels are newlinux an
expiremental that I put first in the lilo.conf file and dos).
boot=/dev/hda6
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
image=/boot/zImage
label=newlinux
root=/dev/hda6
read-only
image=/boot/vmlinuz-2.0.36-0.7
label=linux
root=/dev/hda6
read-only
other=/dev/hda1
label=dos
table=/dev/hda
CK
------------------------------
From: "Christos Karayiannis" <[EMAIL PROTECTED]>
Subject: lilo options
Date: Mon, 28 Aug 2000 23:21:26 +0300
Jan Welti asked me to see my /etc/lilo.conf so here it is. As I said the
problem is that only linux comes out during booting which is the original
but second in order in my lilo.conf (the other two labels are newlinux an
expiremental that I put first in the lilo.conf file and dos).
boot=/dev/hda6
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
image=/boot/zImage
label=newlinux
root=/dev/hda6
read-only
image=/boot/vmlinuz-2.0.36-0.7
label=linux
root=/dev/hda6
read-only
other=/dev/hda1
label=dos
table=/dev/hda
------------------------------
** 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
******************************
