You should format your messages in ascii to send to this list.
> I know PIII can support 64G physical memory. In FreeBSD how can I visit
> such range memory(4G-64G) ?
You can't. Those memory ranges are strictly off-limits to non-US
citizens.
--
... every activity meets with opposition, ever
Chirag Kantharia wrote:
>
> On Wed, Aug 01, 2001 at 11:25:40PM -0700, Terry Lambert wrote:
> | Uh, st_size is an off_t, which is a signed 64 bit value,
> | not an unsigned 32 bit vale...
>
> why should it be `signed' 64 bit and not unsigned?
Return value for lseek is off_t. -1 indicates error
What may be interesting as a comparison -
We are starting the process of upgrading our nameservers, which were
installed approximately 2 years ago. Their OS has not been touched,
except for a few security patches since then, and they are still
running 3.1-STABLE. We have recently brought a thir
Chirag Kantharia wrote:
| On Wed, Aug 01, 2001 at 11:25:40PM -0700, Terry Lambert wrote:
| | Uh, st_size is an off_t, which is a signed 64 bit value,
| | not an unsigned 32 bit vale...
|
| why should it be `signed' 64 bit and not unsigned?
So that things like lseek(2) can return -1 as an error
On Wed, Aug 01, 2001 at 11:25:40PM -0700, Terry Lambert wrote:
| Uh, st_size is an off_t, which is a signed 64 bit value,
| not an unsigned 32 bit vale...
why should it be `signed' 64 bit and not unsigned?
chyrag.
--
Chirag Kantharia, slashetc.net/chyrag/
To Unsubscribe: send mail to [EMAIL
Joseph Gleason wrote:
> Alright, I made a mistake. But I did read the man page. Where does it say
> off_t is 64bits?
The same place it says char is 8 bits, short is 16 bits, and int
and long are 32 bits: in your assumptions.
It might be useful (for some definitions of "useful") to have a
man p
> In message <[EMAIL PROTECTED]>, "Eugene L. Vorokov" wr
> ites:
> >fault virtual address = 0x60c0ff00
>
> I missed the beginning of this thread, but this looks like a problem
> that was fixed just before 4.3-RELEASE. What version of FreeBSD
> are you running?
It's 4.2-RELEASE. But I had simil
> craig wrote:
>
>
> I know PIII can support 64G physical memory. In FreeBSD how can I visit such
> range memory(4G-64G) ?
The short answer is "you can't".
The longer answer is that you end up having to window it using
segmentation; if you are familiar with the 4k window on video
memory in the
Joseph Gleason wrote:
>
> In FreeBSD, how can I determine the size of a file in C++ when the file is
> greater than 4gb?
>
> Currently, I use stat() and use st_size. That is limited to 4gb (32bit
> unsigned int)
Uh, st_size is an off_t, which is a signed 64 bit value,
not an unsigned 32 bit va
On Thu, Aug 02, 2001 at 08:53:38AM +0800, craig wrote:
>
> I know PIII can support 64G physical memory. In FreeBSD how can I
> visit such range memory(4G-64G) ?
You can't, right now.
Kris
PGP signature
On Wed, Aug 01, 2001 at 10:31:22PM -0400, Joseph Gleason wrote:
> Alright, I made a mistake. But I did read the man page. Where does it say
> off_t is 64bits?
>
> My mistake was not digging through the include files enough to see what was
> going on.
off_t st_size; /
Kent Stewart wrote:
>
> Jim Bryant wrote:
> >
> > Joseph Gleason wrote:
> > >
> > > - Original Message -
> > > From: "Alex Zepeda" <[EMAIL PROTECTED]>
> > > To: "Joseph Gleason" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> > > Sent: Wednesday, August 01, 2001 21:45
> > > Subject: Re: Findin
On Wed, Aug 01, 2001 at 05:18:40PM +, Paul Halliday wrote:
> heh.. freebsd usb sucks.
> I have a handspring and a fujifilm finepix40i that are just sitting here
> collecting dust.
>
>
> From 3.4 - 4.3 S I have tried every available means, packages, patches
> to get either of them working
Jim Bryant wrote:
>
> Joseph Gleason wrote:
> >
> > - Original Message -
> > From: "Alex Zepeda" <[EMAIL PROTECTED]>
> > To: "Joseph Gleason" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> > Sent: Wednesday, August 01, 2001 21:45
> > Subject: Re: Finding filesizes in C++ for files greater t
Joseph Gleason wrote:
>
> - Original Message -
> From: "Alex Zepeda" <[EMAIL PROTECTED]>
> To: "Joseph Gleason" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Sent: Wednesday, August 01, 2001 21:45
> Subject: Re: Finding filesizes in C++ for files greater than 4gb
>
> > On Wed, Aug 01, 2001
> :Alright, I made a mistake. But I did read the man page. Where does it
say
> :off_t is 64bits?
> :
> :My mistake was not digging through the include files enough to see what
was
> :going on.
> :
>
> The types(5) manpage will tell you this.
>
Ahh, thank you. I was not aware that existed.
On Wed, 1 Aug 2001, Joseph Gleason wrote:
:
:- Original Message -
:From: "Alex Zepeda" <[EMAIL PROTECTED]>
:> On Wed, Aug 01, 2001 at 09:34:43PM -0400, Joseph Gleason wrote:
:>
:> > In FreeBSD, how can I determine the size of a file in C++ when the file
:is
:> > greater than 4gb?
:> >
:>
Hi,
A function available from libalias, the
PKT_ALIAS_PUNCH_FW one is currently not implemented in ppp. Maybe somebody could
implement it in ppp. It's definitly not much work, so I request if somebody
could do it.
greets
Dennis
- Original Message -
From: "Alex Zepeda" <[EMAIL PROTECTED]>
To: "Joseph Gleason" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, August 01, 2001 21:45
Subject: Re: Finding filesizes in C++ for files greater than 4gb
> On Wed, Aug 01, 2001 at 09:34:43PM -0400, Joseph Gleason w
On Wed, Aug 01, 2001 at 09:34:43PM -0400, Joseph Gleason wrote:
> In FreeBSD, how can I determine the size of a file in C++ when the file is
> greater than 4gb?
>
> Currently, I use stat() and use st_size. That is limited to 4gb (32bit
> unsigned int)
You're wrong. Read the man page. No soup
On 02-Aug-2001 Joseph Gleason wrote:
> Currently, I use stat() and use st_size. That is limited to 4gb (32bit
> unsigned int)
>
> I could use st_blocks, but that wouldn't give me the exact size.
>
> (st_blocks -1) * 512 + (st_size % 512)
>
> This would make sense, but in tests st_bloc
On 02-Aug-01 Joseph Gleason wrote:
> In FreeBSD, how can I determine the size of a file in C++ when the file is
> greater than 4gb?
>
> Currently, I use stat() and use st_size. That is limited to 4gb (32bit
> unsigned int)
struct stat {
...
off_t st_size; /* fi
* Joseph Gleason <[EMAIL PROTECTED]> [010801 20:35] wrote:
> In FreeBSD, how can I determine the size of a file in C++ when the file is
> greater than 4gb?
>
> Currently, I use stat() and use st_size. That is limited to 4gb (32bit
> unsigned int)
No it's not:
struct stat {
dev_t
In FreeBSD, how can I determine the size of a file in C++ when the file is
greater than 4gb?
Currently, I use stat() and use st_size. That is limited to 4gb (32bit
unsigned int)
I could use st_blocks, but that wouldn't give me the exact size.
(st_blocks -1) * 512 + (st_size % 512)
This would
I know PIII can support 64G physical memory. In FreeBSD how
can I visit such range memory(4G-64G) ?
[EMAIL PROTECTED]
Frederique Rijsdijk wrote:
> Is it possible to connect a digital camera with a USB interface
> (FujiFinePix1400 in this case) to a FreeBSD (3.4-S) host to download
> the images?
>
> Thanks,
>
heh.. freebsd usb sucks.
I have a handspring and a fujifilm finepix40i that are just sitting here
c
On 01-Aug-01 Eugene L. Vorokov wrote:
>> Can you compile a debug kernel please and repeat this? That way you will
>> have
>> debug symbols so that you can get more useful information out of gdb.
>> You'll
>> have to get a new crashdump with the debug kernel running however.
>
> Maybe it's offt
Peter Pentchev <[EMAIL PROTECTED]> writes:
> Or rather, do not try this while syslogd is running.
>
> src/sys/kern/subr_log.c defines the operation of the /dev/klog
> device, and there is an upper limit on the number of processes
> that can simultaneously open the log device - the limit is one.
>
> I was wondering whether someone could shed some light on this for me: I've i
> nstalled FreeBSD 4.3, Debian Linux 2.2r2 and windows 98 on my laptop. Everyt
> hing is fine except that after using FreeBSD if I try to go into windows, the
> system locks up. If I turn the power off and back on a
no, as long as your swap device is big enough to hold all of RAM it will
work..
you are supposed to use your normal swap device.
it reads it off and saves it elsewhere as teh first thing it does after
booting, before you've had a chance to start swapping..
On Wed, 1 Aug 2001, Eugene L. Vorokov
On Mon, Jul 30, 2001 at 02:35:21PM -0700, Kris Kennaway wrote:
> On Mon, Jul 30, 2001 at 11:50:18AM -0700, Hans Zaunere wrote:
> > Hello,
> >
> > I'm looking to access kernel messages directly from
> > the kernel, and not through syslog if I can help it.
>
> Look at how syslogd does it.
Or rath
...
> > According to my calculation, pte=0xbfcc0001 and *pte will yield
> > 0x2FF,0xC0,0x1 as indexes to the page directory table, page table and
> > an offset. My page directory table is like this (starting at physical
> > address 0x2C2000):
> >
> > indexpage_table_base_address; p
FreeBSD can not allocate from the PQ_CACHE queue in an interrupt
context. Can anyone explain it to me why this is the case?
Thanks,
-Zhihui
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
My laptop, a Toshiba Tecra 8100 with a 12 GB, evenly divided in two partitions
runs with none of the problems described.
I run Windows 98 on the first partition (dev/ad0s) and FreeBSD on the second
(dev/ad0s2*). Could it be a version problem ? XFree 4.0.1 and FreeBSD 5.0
(current) is what I hav
>I was wondering whether someone could shed some light on this for me: I've installed
>FreeBSD 4.3, Debian Linux 2.2r2 and windows 98 on my laptop. Everything is fine
>except
>that after using FreeBSD if I try to go into windows, the system locks up. If I turn
>the power off and back on after
I was wondering whether someone could shed some light on this for me: I've installed
FreeBSD 4.3, Debian Linux 2.2r2 and windows 98 on my laptop. Everything is fine
except that after using FreeBSD if I try to go into windows, the system locks up. If
I turn the power off and back on after att
Is it possible to connect a digital camera with a USB interface
(FujiFinePix1400 in this case) to a FreeBSD (3.4-S) host to download
the images?
Thanks,
-- Frederique
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Hello,
here's my crash dump, something related to mbufs. If more information is
needed, tell me what to do, I'll provide it. This usually happens (but not
always) when someone is downloading something huge from ftp server on this
machine.
Regards,
Eugene
vel@bugz:/home/vel # uname -r
4.2-RELE
On Wed, Aug 01, 2001 at 12:31:12PM +0400, Eugene L. Vorokov wrote:
> > you just call config with '-g' option. and compile the kernel in normal
> > way. The freebsd handbook discusses this in more detail.
>
> Yet another issue, I have run config -g, then make depend, make and
> make install.debu
Michael VanLoon <[EMAIL PROTECTED]> writes:
> Thanks that's just exactly the information I was looking for. :-)
>
> I'm slow grunging through the code and man pages that take this apart.
>
> As far as UNPv1 I assume you're referring to Stevens' "Unix Network
> Programming"? If I'm not mistaken
On Wed, 1 Aug 2001, Eugene L. Vorokov wrote:
> Yet another issue, I have run config -g, then make depend, make and
> make install.debug. But my /kernel is still about 2mb long, which probably
> means it's not really debug kernel. However I see kernel.debug in the
> compile directory which is abo
As previously discussed. This is the conservative route, of course. I did
not want to get into creating new VOP_SETATTR interfaces.
PR kern/29355
http://www.freebsd.org/cgi/query-pr.cgi?pr=29355
J
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body o
> you just call config with '-g' option. and compile the kernel in normal
> way. The freebsd handbook discusses this in more detail.
Yet another issue, I have run config -g, then make depend, make and
make install.debug. But my /kernel is still about 2mb long, which probably
means it's not real
the code as follows (at least it works in my case) :
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
/* IP */
#include
#include
#include
#include
/* OSI */
#include
#include
#include
#include
#include
#include
#include
#include
Originally posted to -net but no replies,
maybe some here could help me out? tia, Andy
-Original Message-
To: [EMAIL PROTECTED]
Subject: ioctl and fxp/tl drivers
Hi all
This maybe a dumb question but a bit
stumped at the mo. When I make an
ioctl call to the fxp or tl drivers
thus:
if
Michael VanLoon wrote:
>
> > From: Chris Faulhaber [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, July 31, 2001 3:56 PM
> >
> > On Tue, Jul 31, 2001 at 03:56:40PM -0700, Michael VanLoon wrote:
> > > Please point me to a more appropriate forum if there is
> > one. I'm kinda out
> > > of my depth o
"Eugene L. Vorokov" wrote:
>
> > Can you compile a debug kernel please and repeat this? That way you will have
> > debug symbols so that you can get more useful information out of gdb. You'll
> > have to get a new crashdump with the debug kernel running however.
>
> Maybe it's offtopic a bit,
On Wed, 1 Aug 2001, Eugene L. Vorokov wrote:
:> > Maybe it's offtopic a bit, but can you please give exact instructions of how
:> > to compile debug kernel ? My machine crashes sometimes too, I tried to compile
:> > debug kernel, but it seemed not so easy and I gave up due to lack of time. Or
:>
Weiguang SHI wrote:
> I need your help to understand this.
> In machdep.c,
>
>1451 /*
>1452 * map page 1 R/W into the kernel page table so we can use
> it
>1453 * as a buffer. The kernel will unmap this page later.
>1454 */
>1455 pte
> > Maybe it's offtopic a bit, but can you please give exact instructions of how
> > to compile debug kernel ? My machine crashes sometimes too, I tried to compile
> > debug kernel, but it seemed not so easy and I gave up due to lack of time. Or
> > is there any URL with a good explanation ?
>
>
50 matches
Mail list logo
