> At 9:52 PM -0700 7/15/99, Matthew Dillon wrote:
> >:> ... How many programmers bother to even *clear* errno before
> >:> making these calls (since some system calls do not set errno
> >:
> >:> if it already non-zero).
> In message
> "Brian F. Feldman" writes:
> : You can always use off_t with "%qd", (int64_t)foo.
>
> But that isn't portbale. %qd is a bsdism. %lld and %llu are the
> latest C standards way to say that.
If you're that fixed on portability, "%lux%08ulx", (long)foo>>32,
(long)foo is alwa
> Does anyone know an inexpensive algorithm (O(1)) to go from an number to
> the next (lower or higher) power of two.
>
> 1 -> 1
> 2,3 -> 2
> 4,5,6,7 -> 4
> 8,9,10,11,12,13,14,15 -> 8
> etc.
>
> So %1101 should become either %1 or %
> On Fri, Aug 27, 1999 at 08:45:31PM -0400, Sergey Babkin wrote:
> > Thomas David Rivers wrote:
> >
> > > Microsoft needs a "business quality" version of Windows,
> > > which it claims is Windows/2000. That version of Windows
> > > could benefit from a 64-bit port, if for marketing only; but
> I'm looking at cleaning up a few compile nits and I'm wondering what the
> officially approved way of silencing "may not be used" warnings:
>
> int
> foo(int flag)
> {
> int j;
>
> if (flag)
> j = 1;
>
> /*
> * This noop statement is enough to
> > I wanted t know where the environment strings i bsd were stored after a
> > program execs another one.
extern char **environ;
> At the top of memory. You can access them by the standard (but
> undocumented) method:
>
> int main (int argc, char *argv [], char *envp [])
>
> envp is a point
> > This is of course correct except for the `undocumented' claim. The
> > `envp' has been documented as the third argument to main() since the
> > Pharaons (well, not quite ;). Apparently AT&T UNIX even has a
> > (documented) five-parameter main().
>
> This is news to me. Can you point to the d
> I know about envp.
>
> What I want to know is the exact position of these variables on the stack.
>
> and if anywhere I can find some data, on the exact compisoition of the
> stcak, then it will be very helpful.
>
> references of books and websites wil be most helpful.
Basically, i386 BSD ke
> I've got some prototype code in place which supports the context
> switching part of this. It's pretty simple right now, as I'm trying
> to keep changes to a minimum.
>
> What I've done is simply added the dr0-dr3,dr6,dr7 registers to
> 'struct pcb' in /usr/src/sys/i386/include/pcb.h. In cpu_
> Why not put the kernel in a different address space? IIRC there's no
> absolute requirement for the kernel and userland to be in the same
> address space, and that way we would have 4 GB for each.
Wouldn't that make system calls that need to share data between kernel
and user spaces hopelessl
> we already use the gs register for SMP now..
> what about the fs register?
> I vaguely remember that the different segments could be used to achieve
> this (%fs points to user space or something)
... as I've suggested a few days ago, and was told to shut up with a (rather
irrelevant) referen
> jul...@whistle.com (Julian Elischer) writes:
>
> > we already use the gs register for SMP now..
> > what about the fs register?
> > I vaguely remember that the different segments could be used to achieve
> > this (%fs points to user space or something)
>
> You can't extend the address spac
that all binary attachments should be
stripped from freebsd-hackers mail. I believe it is still a very good idea,
and patches tend to be posted as text anyway.
Pat.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Patryk ZadarnowskiUniversit
object files are expressive speech
> or functional tools coming on. :)
Definitely expressive speech. Which makes GCC a creative, intelligent
creature, doesn't it? ;)
Pat.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Patryk Zadarnowski
hink POSIX deals with the wchar_t issue at all (someone correct me if
I'm wrong.)
Pat.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Patryk ZadarnowskiUniversity of New South Wales
<[EMAIL PROTECTED]> School of Computer Sci
, is far from it. Rather, it's
simply another reasonably-well structured kernel. With 300+ system
calls in the nucleus, the NT kernel handles just about everything
except for major GUI tasks.
Pat.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Patryk Zadarnow
On Sun, 17 Dec 2000, Tony Finch <[EMAIL PROTECTED]> wrote:
> Patryk Zadarnowski <[EMAIL PROTECTED]> wrote:
>>
>> Now that I think of it, there aren't many commercial microkernel
>> systems out there with the possible exception of QNX and lots of
>> l
ter power supply
2. get a quieter fans
3. get a good new drives: they're quiet.
4. get used to the noise.
I have three computers running 24/7 in my bedroom, and after some swapping
of power supplies, the noise is perfectly bearable.
Pat.
-=-=-=-=-=-=-=-=-=-=-=
> I know about envp.
>
> What I want to know is the exact position of these variables on the stack.
>
> and if anywhere I can find some data, on the exact compisoition of the
> stcak, then it will be very helpful.
>
> references of books and websites wil be most helpful.
Basically, i386 BSD k
> I've got some prototype code in place which supports the context
> switching part of this. It's pretty simple right now, as I'm trying
> to keep changes to a minimum.
>
> What I've done is simply added the dr0-dr3,dr6,dr7 registers to
> 'struct pcb' in /usr/src/sys/i386/include/pcb.h. In cpu
> [EMAIL PROTECTED] (Julian Elischer) writes:
>
> > we already use the gs register for SMP now..
> > what about the fs register?
> > I vaguely remember that the different segments could be used to achieve
> > this (%fs points to user space or something)
>
> You can't extend the address spac
> At 9:52 PM -0700 7/15/99, Matthew Dillon wrote:
> >:> ... How many programmers bother to even *clear* errno before
> >:> making these calls (since some system calls do not set errno
> >:
> >:> if it already non-zero).
> In message <[EMAIL PROTECTED]> "Brian F.
>Feldman" writes:
> : You can always use off_t with "%qd", (int64_t)foo.
>
> But that isn't portbale. %qd is a bsdism. %lld and %llu are the
> latest C standards way to say that.
If you're that fixed on portability, "%lux%08ulx", (long)foo>>32,
> Does anyone know an inexpensive algorithm (O(1)) to go from an number to
> the next (lower or higher) power of two.
>
> 1 -> 1
> 2,3 -> 2
> 4,5,6,7 -> 4
> 8,9,10,11,12,13,14,15 -> 8
> etc.
>
> So %1101 should become either %1 or
> On Fri, Aug 27, 1999 at 08:45:31PM -0400, Sergey Babkin wrote:
> > Thomas David Rivers wrote:
> >
> > > Microsoft needs a "business quality" version of Windows,
> > > which it claims is Windows/2000. That version of Windows
> > > could benefit from a 64-bit port, if for marketing only; bu
> I'm looking at cleaning up a few compile nits and I'm wondering what the
> officially approved way of silencing "may not be used" warnings:
>
> int
> foo(int flag)
> {
> int j;
>
> if (flag)
> j = 1;
>
> /*
> * This noop statement is enough t
> On Sat, 25 Sep 1999, Chris Costello wrote:
>
> >Aah! No! I tried that with GNOME once and it drove me insane
> > for about two weeks.
> >
> >Auto-upgrades on ports would be _very_ _very_ bad, especially
> > for those using apache from ports!
>
> that's right. i thought about having
> In the last episode (Oct 29), Lars Gerhard Kuehl said:
> > > Think about it for a second. How big is a pointer?
> >
> > The Intel architecture still supports segmented memory,
> > so the effective maximum pointer size is 48 bit.
The extra 16 bits of the segment don't actually contribute to th
> Hi,
>
> is there any alternative (non-commercial) C compiler to use, or is gcc the
> best?
>
> I have just upgraded my system to -current w/egcs 2.95.2 and I have
> several problems with it, especially when using optimizations (-O2 and
> such)
>
> ok I know there's the good old gcc 2.7.2.3 bu
> On Wed, 5 Jan 2000, Patryk Zadarnowski wrote:
>
> > > Hi,
> > >
> > > is there any alternative (non-commercial) C compiler to use, or is gcc the
> > > best?
> > >
> > > I have just upgraded my system to -current w/egcs 2.95.2 and
> Martin Cracauer <[EMAIL PROTECTED]> wrote in list.freebsd-hackers:
> > You will not be able to use all features of FreeBSD, of course.
> > Calling functions that take long long arguments doesn't work, these
> > should be masked out when compiling struct ansi code. It may get
> > painful quic
> Recently I was tasked to find a way to scale up our MYSQL server, running
> MYSQL3.22.15 on FreeBSD3.3. I've been testing a hardware RAID solution,
> and found that with 6 disks in a RAID5 configuration, the system was only
> perhaps 30% faster than when running on a single disk. [The 6 disks
>
> Just read this article:
>
> http://www.zdnet.com/zdnn/stories/news/0,4586,2440002,00.html
>
> Which leads to my potentially ignorant question: Where is FreeBSD
> w/regards to running on the Itanium (or other 64bit chips)?
Considering the fact that Intel released the IA-64 OS info only on t
> Patryk Zadarnowski wrote:
> > FreeBSD when that happens. In the meantime, the only alternative would be to
> > convince Intel to give someone their IA-64 SimOS, but there's an extermely
> > slim chance of that happening (from talking to someone on the IA-64 team.)
&
> > > > Which leads to my potentially ignorant question: Where is FreeBSD
> > > > w/regards to running on the Itanium (or other 64bit chips)?
> > >
> > > Waiting for somebody at Intel to give us either hardware or simulator
> > > time. Without either of those things, "working on" Itanium support
> "I could have had a PA-8600!"? Today, and not at some vague point in the
> future?
That sort-of misses the point, as I'm taking a research OS perspective, where
IA-64 is trully unique in terms of versitality and a well thought-through
design (especially when it comes to SASOS support!) Beside
>
> > What can one say to that, apart from "I have one right here and it works
> > just fine" - not something you can say about the IA-64. 8)
>
> I'll just reach down and pat my trusty pair of manufactured-in-1993 Alpha
> 3000's on their heads... :)
>
> Oh, forgot... It's not new until Intel
> > You're being just plain silly. It takes about 5 minutes with the
> > manuals to realize just how little AXP and IA-64 have in common: one
> > is a classic superscalar out-of-order design, the other is just about
> > the opposite: a typical explicit-ILP architecture. What makes IA-64
> > grea
> :...
> :and Linux essentially treats hardware page tables as TLBs.
> :
> :The problem with the above approach is duplication of information between
> :Linux page tables and hardware page tables and inefficient use of memory
> :for page tables.
> :
> :I think OSes like FreeBSD which don't have a
> :Kevin Elphinstone did a PhD thesis on TLB structures for 64 bit address spaces
> :and it turns out that hash tables perform quite poorly. I'd suggest GPTs
> :instead, or maybe LPCtrie that Chris Szmajda has been working on here at UNSW.
> :Both have the advantage of supporting multiple page siz
> On Sun, Feb 20, 2000 at 12:42:14PM +1100, Patryk Zadarnowski wrote:
> > One more thing about GPTs (I thought I'll leave that till last. ;)
> > Jochen Liedtke holds a German patent on them, although he will
> > probably be fairly easily convinced to give FreeBSD right
> On Sun, Feb 20, 2000 at 01:48:49PM +1100, Patryk Zadarnowski wrote:
> > > It looks like the hardware has to implement GPTs and know how to
> > > walk them. How can FreeBSD use them without hardware support ?
> >
> > No it doesn't. We've got softw
> On Sun, 20 Feb 2000, Patryk Zadarnowski wrote:
>
> > > On Sun, Feb 20, 2000 at 12:42:14PM +1100, Patryk Zadarnowski wrote:
> > > > One more thing about GPTs (I thought I'll leave that till last. ;)
> > > > Jochen Liedtke holds a German patent o
h pending interrupts, partially
completed DMA transfers and other such state information?
Pat.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Patryk Zadarnowski <[EMAIL PROTECTED]> University of New South Wales
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
I was to download the ISO image over my modem, I'd order a CD
today instead (or enroll at Uni ;)
So I'm supporting uncompressed iso images. 99.99% of those who'd
benefit from the compression would never consider downloading them
anyway, and 99.99% of those who are going to use the
(as it was last avaliable) at http://siliconbreeze.com/TenDRA/. Hope it's of
some help.
Pat.
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Patryk ZadarnowskiUniversity of New South Wales
<[EMAIL PROTEC
heaven. Let me
restate that: I will use it. Currently, if you have a group of ISO
8859-2 users on the system , the ISO 8859-1 people see them as
meaningless junk. I don't even want to think about something like
Arabic.
Pat.
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
ormation in polish in the pre-8859 days, you'd
know why (about five radically different charsets in common use) Besides, if
the alphabet for information interchange doesn't deserve standarising, I don't
know what does.
Pat.
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
he
``other camp'' to the u-kernel guys (like myself.) Hence the ``BSD''
in its name. ;)
Pat.
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Patryk ZadarnowskiUniversity of New South Wales
<[EMAIL PROTECTED]> School of Computer Science and Engineering
-=-=-=-=-=-=-=-=-=-=
49 matches
Mail list logo
