From: "Dag-Erling Smørgrav" [mailto:[EMAIL PROTECTED]
> "Darren Pilgrim" <[EMAIL PROTECTED]> writes:
> > GEOM doesn't automatically read the partition table and create the
> > slice device [...]
>
> Yes, it does. When the umassX provider shows up, GEOM immediately
> tastes it and creates geoms f
"Darren Pilgrim" <[EMAIL PROTECTED]> writes:
> Attached as named above. The logs show the da0 DISK class in the GEOM
> config, but no MBR class entry.
Take a closer look at geom-logs. It shows a slew of CAM errors.
There's something wrong with your fob, or possibly (but not likely)
with the USB
On Thu, Jun 09, 2005 at 05:42:16PM -0400, Aziz Kezzou wrote:
> Hi all,
> I am trying to figure out from the kernel source code (FreeBSD 5.3)
> how can I perform a routing lookup in a KLD module.
> Since I am short in time, if anyone knows how do to do this I would
> appreciate. Any pointers to the
> -Original Message-
> From: "Dag-Erling Smørgrav" [mailto:[EMAIL PROTECTED]
> Sent: Friday, June 10, 2005 12:16 AM
> To: Darren Pilgrim
> Cc: freebsd-hackers@freebsd.org
> Subject: Re: Determining disk device and kicking GEOM when
> doing automatic mounting of umass devices
>
>
> "Da
"Darren Pilgrim" <[EMAIL PROTECTED]> writes:
> So yeah I gueuss my fob is busted or funky. The CAM errors are "just" the
> drive saying there's no media present, so maybe the device doesn't support
> the commands necessary to report disk capacity? Is there a way to educate
> CAM about this so the
test
--
place ur advertise here
pgpaXBCa8WZRV.pgp
Description: PGP signature
On 6/8/05, Scott Long <[EMAIL PROTECTED]> wrote:
> Ivan Voras wrote:
> > Scott Long wrote:
> >
> >> Again, I'm not exactly sure how a generic mechanism can handle the
> >> distinction of data vs. metadata vs. journal data. Also, what you
> >
> >
> > I don't care about the distinction at this level
I received no reply on this question at questions mailing list, so I try
asking this here. Hope I'm not asking this in completely wrong list.
In recent discussion in OpenWatcom lists it was noticed that at least
certain addressing modes of assembler ENTER instruction causes a crash
when used in
>I received no reply on this question at questions mailing list, so I try
>
>asking this here. Hope I'm not asking this in completely wrong list.
>
>In recent discussion in OpenWatcom lists it was noticed that at least
>certain addressing modes of assembler ENTER instruction causes a crash
>when u
Hi,
Reko Turja wrote:
I received no reply on this question at questions mailing list, so I try
asking this here. Hope I'm not asking this in completely wrong list.
In recent discussion in OpenWatcom lists it was noticed that at least
certain addressing modes of assembler ENTER instruction caus
On Jun 8, 2005, at 11:35 PM, Dag-Erling Smørgrav wrote:
Chad David <[EMAIL PROTECTED]> writes:
My company built a tool a few years back for creating a bootable cdrom
based on a running host FreeBSD 3/4 system, which promptly got
shelved and
forgotten.I recently had to update it for FreeBSD 5
On May 29, 2005, at 11:42 PM, Erich Dollansky wrote:
Hi,
Hervé Kergourlay wrote:
xorgconfig
I launch this tools but I 'm not sure of the screen resolution
details, vertical refresh rate, horizontal sync rate, ...
I fill the answers with standard values
Do not do this. You must have the deta
Hey everybody,
I have a feeling that I'm missing something really obvious, but I'm having
trouble understanding why the following program:
#include
#include
int main (int argc, char * argv[])
{
void * ptr = malloc(65536);
size_t i;
for (i = 0; i < 65536; i++)
{
In the last episode (Jun 10), Mike Hunter said:
> I have a feeling that I'm missing something really obvious, but I'm
> having trouble understanding why the following program:
>
> int main (int argc, char * argv[])
> {
> void * ptr = malloc(65536);
>
> Never prints anything but "0"'s.
The
Hey everybody,
I was playing around in ports and came across xroach. Cool program :)
The only problem is that it runs too fast; you can't see the roaches
because they scurry under your windows too quickly.
Is there a general-purpose approach to this kind of problem in the FBSD
world? I can see
On Fri, 10 Jun 2005, Mike Hunter wrote:
> Hey everybody,
>
> I was playing around in ports and came across xroach. Cool program :)
> The only problem is that it runs too fast; you can't see the roaches
> because they scurry under your windows too quickly.
>
> Is there a general-purpose approach
At 3:40 PM -0700 6/10/05, Mike Hunter wrote:
Hey everybody,
I have a feeling that I'm missing something really obvious, but
I'm having trouble understanding why the following program:
Never prints anything but "0"'s.
Kernel generally clears out memory in the background. See also
the man p
You think that is bad, try running 'rain' on an xterm!
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
___
freebsd-hackers@freebsd.org
On 2005-06-10 15:44, Mike Hunter <[EMAIL PROTECTED]> wrote:
> Hey everybody,
> I was playing around in ports and came across xroach. Cool program :)
> The only problem is that it runs too fast; you can't see the roaches
> because they scurry under your windows too quickly.
A port patch would fix
On Fri, Jun 10, 2005 at 03:44:15PM -0700 I heard the voice of
Mike Hunter, and lo! it spake thus:
>
> Is there a general-purpose approach to this kind of problem in the
> FBSD world? I can see myself writing a C program called `slow` that
> would take argv[1] as the factor ( > 1) by which argv[2]
Hello.
I have installed FreeBSD 5.4 on a ASUS S5200N. Runs very nice!
However I still need to install Wifi. I saw that Intel(R) PRO/Wireless
2200BG is not supported by wlan FreeBSD driver (reading through the man
pages). Then I found that I could use the NDIS driver added on FreeBSD
5.3 to ach
--- Neo-Vortex <[EMAIL PROTECTED]> wrote:
>
>
> On Fri, 10 Jun 2005, Mike Hunter wrote:
>
> > Hey everybody,
> >
> > I was playing around in ports and came across
> xroach. Cool program :)
> > The only problem is that it runs too fast; you
> can't see the roaches
> > because they scurry unde
22 matches
Mail list logo
