The trick is to get the windows 2000 bootloader load the boot0 program
like it would DOS. Pretend you have Dos on your hard disk and instead of
linking the boot option to command.com, link it to the boot0. This means,
of course, that you have to copy the boot0 file to your Windows partition.
Work
Peter Seebach wrote:
>
> In message <[EMAIL PROTECTED]>, Farooq Mela writes:
> >Of course I realize that allocating memory can fail. That is why I use
> >xmalloc and friends - so that I can avoid having to check for failure
> >each time I want to allocate memory.
>
> That's the problem. You sti
On Thu, Feb 22, 2001 at 01:19:33PM -0600, Michael C . Wu wrote:
> On Thu, Feb 22, 2001 at 07:40:16PM +0100, Torbjorn Kristoffersen scribbled:
> | Hi I'm using 4.2-RELEASE, with a parallel port ZIP drive (100M).
> | Whenever I copy a large file from the zip drive (for example /dev/da0s1),
> | the "
In message <[EMAIL PROTECTED]>, Farooq Mela writes:
>Of course I realize that allocating memory can fail. That is why I use
>xmalloc and friends - so that I can avoid having to check for failure
>each time I want to allocate memory.
That's the problem. You still *NEED* to check. You can't just
Peter Seebach wrote:
> It is a mistake to believe that you "don't have to worry about running
> out of memory". You should always check, every time, and exit as gracefully
> as you can.
>
> -s
Of course I realize that allocating memory can fail. That is why I use
xmalloc and friends - so that
i need help dual booting win200 and freebsd4.2. Win200 is already installed
casue i wanted to use its bootmanager for loading each OS. I know win2k and
load openbsd so figure i wont have any trouble dual booting with freebsd.
Now I cant find any documentation on dual booting win2k and freebsd. I n
In message <[EMAIL PROTECTED]>, Farooq Mela writes:
>How do you guys feel about this?
It is a mistake to believe that you "don't have to worry about running
out of memory". You should always check, every time, and exit as gracefully
as you can.
-s
To Unsubscribe: send mail to [EMAIL PROTECTED]
Hi,
Usually when I write programs, I have functions such as the following:
void *
xmalloc(size_t size)
{
void *p;
if ((p=malloc(size))==NULL) {
fprintf(stderr, "out of memory\n");
exit(1);
}
return(p);
}
void *
xrealloc(void *ptr,
Can somebody clue me in on how Wake On Lan is supposed to work?
Does it require any support at all from the OS, or is it totally a
BIOS thing?
I've built the wake-on-lan program submitted via
http://www.FreeBSD.org/cgi/query-pr.cgi?pr=23151 and, although it
seems to work to bring W2K box out of
> 2) I'm not sure I like the strncmp(.., "md", 2) stuff, as that means that
> it would also match any other device name that might begin with md, which
> potentially might not be provided by the md driver. This is currently (I
> suspect) hypothetical as we don't have any other drivers beginning w
>[redirected to -net]
>
>On Wed, Feb 21, 2001 at 09:50:58AM +, [EMAIL PROTECTED] wrote:
>> >On Mon, Feb 19, 2001 at 08:26:56PM +0100, mouss wrote:
>> > > At 14:25 19/02/01 +0200, [EMAIL PROTECTED] wrote:
>> > > > Hi,
>> > > > I encountered the following problem in the 4.2 version.
>> > > > In
In message <[EMAIL PROTECTED]>, mouss writes:
>Now having free() write to stdout/stderr isn't necessarily a good thing
>for daemons. If the message goes through a socket, it'll be hard to
>debug, which was the original intent.
>
>I suggest having some way so that when a program becomes a daemon,
>
I have a question on how to debug Linux binaries. I have a core
file from the linux binary, but if I use the FreeBSD gdb, it cannot
find the shared libraries in /compat/linux/ If I use the /compat/linux/
/usr/bin/gdb, it says the core file is in the wrong format:
Couldn't fetch registers f
I'm assuming right now you are just setting yyin to the fd for the socket.
What you're gonna want to do is define the macro YY_INPUT (see the man page for
details) so that it calls recv on your socket. and then if it errors you can
have YY_INPUT return as an EOF and your <> rule will work fine.
Hello,
I'm currently writing a small interpreter for a client/server
application.
the Lex and Yacc files seem to be OK, as the tests are running fine (as
long as there is only one client, and the client dos not close its
socket ...)
I still have one problem : the server has a single thread : th
The only comments I really had on this were:
1) Your comment about vnode->name mapping is correct, there is no way to
turn a vnode pointer into an absolute path meaningful to the caller. There
are countless reasons why believing this is possible is a bad idea, and we
keep having to hit people wi
On Thu, Feb 22, 2001 at 07:40:16PM +0100, Torbjorn Kristoffersen scribbled:
| Hi I'm using 4.2-RELEASE, with a parallel port ZIP drive (100M).
| Whenever I copy a large file from the zip drive (for example /dev/da0s1),
| the "cp" process eats 98% of the system resources. What's behind all this?
|
At 18:37 22/02/01 +0200, diman wrote:
>Open AF_UNIX socket to syslogd and then use err_set_file()
>to redirect all err/warn messages to syslogd instead of
>stdin/stdout. That should help you debug daemons.
I agree, but one of the nice things about syslog interface is that it hides
all the socket
Hi I'm using 4.2-RELEASE, with a parallel port ZIP drive (100M).
Whenever I copy a large file from the zip drive (for example /dev/da0s1),
the "cp" process eats 98% of the system resources. What's behind all this?
Is there a way to fix it?
711 root 54 0 280K 168K RUN 0:45 93.87%
FreeBSD supports cardbus in -CURRENT, but I wouldn't expect it to ever
support cardbus in 4.x. If you are daring you can get -CURRENT, but from
what I hear right now, it's not working very well.
=
| Kenneth Culver | Fre
On Thu, 22 Feb 2001, mouss wrote:
> Now having free() write to stdout/stderr isn't necessarily a good thing
> for daemons. If the message goes through a socket, it'll be hard to
> debug, which was the original intent.
>
> I suggest having some way so that when a program becomes a daemon,
> it
Robin Cutshaw wrote:
>
> On Mon, Feb 19, 2001 at 12:21:26PM -0800, Peter Wemm wrote:
> > >
> > > Any ideas as to why it would take almost three times longer to build
> > > on FreeBSD?
> >
> > This is probably a silly question, but you did recompile the kernel for
> > SMP, right?
> >
>
> Actually
Now having free() write to stdout/stderr isn't necessarily a good thing
for daemons. If the message goes through a socket, it'll be hard to
debug, which was the original intent.
I suggest having some way so that when a program becomes a daemon,
it can set some "silent-libc" or "libc messages go t
On Thu, Feb 22, 2001 at 10:32:13AM -0500, Justin McKnight wrote:
> I cant figure out to get freebsd 4.2 to recognize
> and enable my 3com cardbus card?
FreeBSD currently doesn't support cardbus cards.
--
Simon Dick [EMAIL PROTECTED]
"Why do I get this urge
I cant figure out to get freebsd 4.2 to recognize
and enable my 3com cardbus card?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Also, if you do something like:
void *ptr = malloc(size);
...
ptr++;
free() will complain about it.
Make sure you are not modifying ptr after it has been malloc()ed.
On 22-Feb-01 Alfred Perlstein wrote:
> * Madhavi Suram <[EMAIL PROTECTED]> [010222 05:09] wrote:
>>
>
In message <[EMAIL PROTECTED]>, Madhavi S
uram writes:
>
>Hi
>
>I am running a C program in user space on FreeBSD 3.3 release. I got a
>warning like this:
>
> testing in free(): warning: modified (chunk-) pointer.
>
>testing is the name of the executable I am running.
>
>Could anyone tell me
* Madhavi Suram <[EMAIL PROTECTED]> [010222 05:09] wrote:
>
> Hi
>
> I am running a C program in user space on FreeBSD 3.3 release. I got a
> warning like this:
>
> testing in free(): warning: modified (chunk-) pointer.
>
> testing is the name of the executable I am running.
>
> Could a
Hi
I am running a C program in user space on FreeBSD 3.3 release. I got a
warning like this:
testing in free(): warning: modified (chunk-) pointer.
testing is the name of the executable I am running.
Could anyone tell me what this warning means? What may be the effect of
this code wh
Dear All,
>
> This bug does not occur with NetBSD make. I spent a couple of hours
> diffing the sources (there are a lot more differences than I expected)
>
There was some talk on the OpenPackages list about differences in the makes
of the three BSD's. I've only followed the discussion with half
Kees Jan wrote:
> Jason Brazile wrote:
> > This bug does not occur with NetBSD make. I spent a couple of hours
> > diffing the sources (there are a lot more differences than I expected)
>
> There was some talk on the OpenPackages list about differences in the makes
> of the three BSD's. I've only
Robin Cutshaw wrote:
> On Mon, Feb 19, 2001 at 12:21:26PM -0800, Peter Wemm wrote:
> > >
> > > Any ideas as to why it would take almost three times longer to build
> > > on FreeBSD?
> >
> > This is probably a silly question, but you did recompile the kernel for
> > SMP, right?
> >
>
> Actually
* Robin Cutshaw <[EMAIL PROTECTED]> [010221 06:07] wrote:
>
> OK, I set softupdates on the disk/partition that the build source/target
> is on. It made no difference in timing. I then created a memory disk,
> set softupdates on it, and mounted it as /tmp. AMAZINGLY, the build
> went from 2:50
At Thu, 22 Feb 2001 09:41:29 +0100, Jason Brazile wrote:
> There is a person with login name "will" who made a CVS log entry that
> says:
> Assume MAINTAINER. I will be taking the job of merging
> NetBSD/OpenBSD improvements (including :C & :L, among others).
> After that, I'll
In message <[EMAIL PROTECTED]> "Jacques A. Vidrine" writes:
: Likewise if the first member were a more complex data type, but
: nevertheless the same between the different structures.
:
: It seems safe to me, but I can't explain why :-)
It is obfuscated 'C', but it is safe. The standard require
Hello phk and -hackers
With md(4)'s great autounit feature, it's becoming harder to keep
track of md(4) devices. Without autounit, you pretty much knew what
was what since you had to specify the unit number; with autounit,
things like `make release` configure an arbitrary unit without telling
yo
Warner Losh wrote:
> This does sound like a bug in our make :-(.
A quick update:
This bug does not occur with NetBSD make. I spent a couple of hours
diffing the sources (there are a lot more differences than I expected)
to see if there was any one small patch that would make things work for
Free
On Wed, Feb 21, 2001 at 08:53:57AM -0700, Warner Losh wrote:
> The standard requires that (void *) &foo == (void *) &foo->s
Thanks, that is what I was trying to track down but couldn't find it.
I also thought that perhaps a structure has the same requirement
alignments as its first member ... I
On Wed, Feb 21, 2001 at 10:23:30AM +0900, Tomoyuki Murakami wrote:
> --Repost---
> If duplicated, ignore this. thanks.
> ---
> Hi
>
> I have made a patch to up ssh version 2.3.0(FreeBSD-current) to
> recently released OpenSSH 2.5.1.
> Too ro
On Wed, Feb 21, 2001 at 05:13:35PM +0100, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Warner Losh writes:
> >In message <[EMAIL PROTECTED]> "Jacques A. Vidrine" writes:
> >: Likewise if the first member were a more complex data type, but
> >: nevertheless the same between the differ
[redirected to -net]
On Wed, Feb 21, 2001 at 09:50:58AM +, [EMAIL PROTECTED] wrote:
> >On Mon, Feb 19, 2001 at 08:26:56PM +0100, mouss wrote:
> > > At 14:25 19/02/01 +0200, [EMAIL PROTECTED] wrote:
> > > > Hi,
> > > > I encountered the following problem in the 4.2 version.
> > > > In ip_forwa
Sergey Babkin wrote:
> As far as I remember, there is not much special. Just create a
> bootable floppy image and give it as option -b to mkhybrid.
> (I strongly recommend mkhybrid over mkisofs because it tends to make
> defective filesystems in fewer cases).
I hadn't heard of mkhybrid, so inves
On Wed, Feb 21, 2001 at 09:56:08AM -0700, Warner Losh wrote:
> There is some verbage in the structure layout part of the standard
> that makes this a logical conclusion.
>
> However, it is overly tricky code. But then again to do the generic
> sort of thing you want to do, you have to resort to
43 matches
Mail list logo
