Booting from a flash card

2005-05-24 Thread Jamie Ostrowski


   I've got a Ricoh (Ricoh RL5C475 PCI-CardBus Bridge) with a 1Gb PCMCIA
Compact Flash card. I'd like to install FreeBSD on the flash card and to
be able to boot with the flash. The problem I am running into is that my
BIOS doesn't recognize the flash card as a boot device.

   Is there any way to run with a FreeBSD system (4.11) off of a flash
card rather than a hard drive? Any way to boot up with the flash card?


   Thanks,

- Jamie







The Moon is Waning Gibbous (99% of Full)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Missing libraries when making c-client

2005-03-26 Thread Jamie Ostrowski
>
>
>I am having some trouble installing imap from source. I am building a
> machine for my boss who *insists* that I cannot use anything from the
> ports collection on the machine, so I can't use the imap port.
>
>The build is failing, and it seems as though it can't find some openssl
> include files, judging from the errors I am getting.
>
>This is on a stock 4.11 system. When I untar the imap-2004c1 source, I
> read the readme doc, and I ran
>
> make bsf
>
> since it is a FreeBSD install. It will not compile, though. Here is where
> it is failing:


Here is something higher up in the make output that looks like it may be a
clue:

Building with SSL
ln -s ssl_unix.c osdepssl.c
echo -I/usr/local/ssl/include -I/usr/local/ssl/include/openssl
-DSSL_CERT_DIRECTORY=\"/usr/local/ssl/certs\"
-DSSL_KEY_DIRECTORY=\"/usr/local/ssl/certs\" >> OSCFLAGS
echo "  ssl_onceonlyinit ();" >> linkage.c
echo -L/usr/local/ssl/lib -lssl -lcrypto  >> LDFLAGS


It seems to be setting info in the files OSCFLAGS and LDFLAGS to
/usr/local/ssl, and I don't have any /usr/local/ssl directory, and I am
unsure how this can be corrected properly.







>
> Building with SSL and plaintext passwords disabled unless SSL/TLS
> echo "  mail_parameters (NIL,SET_DISABLEPLAINTEXT,(void *) 2);" >>
> linkage.c
> cat osdepbas.c osdepckp.c osdeplog.c osdepssl.c > osdep.c
> Building OS-dependent module
> If you get No such file error messages for files x509.h, ssl.h,
> pem.h, buffer.h, bio.h, and crypto.h, that means that OpenSSL
> is not installed on your system. Either install OpenSSL first
> or build with command: make bsf SSLTYPE=none
> `cat CCTYPE` -c `cat CFLAGS` `cat OSCFLAGS` -c osdep.c
> osdep.c:138: x509.h: No such file or directory
> osdep.c:139: ssl.h: No such file or directory
> osdep.c:141: pem.h: No such file or directory
> osdep.c:142: buffer.h: No such file or directory
> osdep.c:143: bio.h: No such file or directory
> osdep.c:144: crypto.h: No such file or directory
>
>
>   etc etc etc...
>
>
> In the Makefile, under the "bsf" target, we see that the path to the stock
> openssl libraries in FreeBSD is declared:
>
> bsf bso:an
> $(BUILD) BUILDTYPE=$@ \
> SPECIALS="GSSDIR=/usr SSLDIR=/usr SSLINCLUDE=/usr/include/openssl
> SSLCERTS=/etc/ssl/certs SSLKEYS=/etc/ssl/private LOCKPGM=/usr/sbin/mlock"
>
>
>
>...and an ls of /usr/include/openssl does include x509.h, ssl.h, pem.h,
> etc.
>
> Does anyone have any explanation for why it isn't finding those files?
> Any direction I can go from here? I would rather not build an additional
> openssl package from a source tree as I would like to just use what is on
> the system. It would make things cleaner (fewer moving parts) when
> cvsupping and building world, etc. I would prefer to use the native
> libraries.
>
>
>Thanks,
>
>- Jamie
>
>
>
>
>
> The Moon is Waning Gibbous (100% of Full)
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>

The Moon is Waning Gibbous (100% of Full)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Missing libraries when making c-client

2005-03-26 Thread Jamie Ostrowski


   Greetings,


   I am having some trouble installing imap from source. I am building a
machine for my boss who *insists* that I cannot use anything from the
ports collection on the machine, so I can't use the imap port.

   The build is failing, and it seems as though it can't find some openssl
include files, judging from the errors I am getting.

   This is on a stock 4.11 system. When I untar the imap-2004c1 source, I
read the readme doc, and I ran

make bsf

since it is a FreeBSD install. It will not compile, though. Here is where
it is failing:

Building with SSL and plaintext passwords disabled unless SSL/TLS
echo "  mail_parameters (NIL,SET_DISABLEPLAINTEXT,(void *) 2);" >>
linkage.c
cat osdepbas.c osdepckp.c osdeplog.c osdepssl.c > osdep.c
Building OS-dependent module
If you get No such file error messages for files x509.h, ssl.h,
pem.h, buffer.h, bio.h, and crypto.h, that means that OpenSSL
is not installed on your system. Either install OpenSSL first
or build with command: make bsf SSLTYPE=none
`cat CCTYPE` -c `cat CFLAGS` `cat OSCFLAGS` -c osdep.c
osdep.c:138: x509.h: No such file or directory
osdep.c:139: ssl.h: No such file or directory
osdep.c:141: pem.h: No such file or directory
osdep.c:142: buffer.h: No such file or directory
osdep.c:143: bio.h: No such file or directory
osdep.c:144: crypto.h: No such file or directory


  etc etc etc...


In the Makefile, under the "bsf" target, we see that the path to the stock
openssl libraries in FreeBSD is declared:

bsf bso:an
$(BUILD) BUILDTYPE=$@ \
SPECIALS="GSSDIR=/usr SSLDIR=/usr SSLINCLUDE=/usr/include/openssl
SSLCERTS=/etc/ssl/certs SSLKEYS=/etc/ssl/private LOCKPGM=/usr/sbin/mlock"



   ...and an ls of /usr/include/openssl does include x509.h, ssl.h, pem.h,
etc.

Does anyone have any explanation for why it isn't finding those files?
Any direction I can go from here? I would rather not build an additional
openssl package from a source tree as I would like to just use what is on
the system. It would make things cleaner (fewer moving parts) when
cvsupping and building world, etc. I would prefer to use the native
libraries.


   Thanks,

   - Jamie





The Moon is Waning Gibbous (100% of Full)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Unexpected resolver behavior

2005-02-17 Thread Jamie Ostrowski



I'm running 4.10-p5 on my workstation at home, and I can't understand
why I cannot get www.foo.com to resolve to an IP I am specifying in
/etc/hosts (I want to over-ride the IP returned by the nameserver I query
by default).


in /etc/hosts:

199.xx.xx.24www.foo.com.


in /etc/host.conf:

# $FreeBSD: src/etc/host.conf,v 1.6 1999/08/27 23:23:41 peter Exp $
# First try the /etc/hosts file
/etc/hosts
# Now try the nameserver next.
bind
# If you have YP/NIS configured, uncom


(I have no nsswitch.conf file in /etc)


But when I try to resolve www.foo.com from the command line, I am getting
the IP address from the nameserver from the outside world rather than the
IP from /etc/hosts. I am not running a local named on this machine,
either. Any ideas?



- Jamie










The Moon is Waxing Gibbous (71% of Full)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Current Release level

2004-11-18 Thread Jamie Ostrowski


   Does anyone know where the current patchlevel for FreeBSD Release is
posted? By this, I mean, I know that Release was just recently incremented
from 4.10-RELEASE-p3 to 4.10-RELEASE-p4 due to the fetch.c security
advisory. (I am assuming that the 'p' stands for patchlevel or something
similiar). But what if I had missed the announcement, or perhaps
there are other modifications not security related. Where do I go to find
out what the current "patchlevel" is for the RELEASE branch?


   - Jamie





The Moon is Waxing Crescent (44% of Full)
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Problem with 4 port Intel nic

2004-11-01 Thread Jamie Ostrowski


I'm having trouble getting a 4 port nic to work in a machine I'm
building. It is using the (4) dc driver and I've got miibus and dc options
enabled in my kernel configuration (I'm still running with GENERIC). This
is FreeBSD 4.10 REL p3.


The machine comes up okay, and I can configure ports dc0 and dc1 on
the NIC, but when I try to configure ports dc2 or dc3 with an IP, the
machine locks up hard, and I can do nothing.


It looks like it may be an IRQ conflict. Here is my dmesg output when
the kernel detects the card:

   http://www.gnulife.org/dmesg.txt


   It looks like ports 0 and 2 are both sharing irq 4 and 1 and 3 are
sharing irq7. Is there a problem with this? If so, any idea how I can get
around it? Thanks!


- Jamie








The Moon is Waning Gibbous (80% of Full)
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: make buildworld failing [ SOLVED ]

2004-10-28 Thread Jamie Ostrowski
On Thu, 28 Oct 2004, Jamie wrote:

>
>
>
> I am upgrading my system from 4.4 REL to 4.10 REL. I cvsupped my
> source tree over, and after I've got the new source tree, when I go to run
> make buildworld, it compiles for quite a while, but then eventually it
> fails:
>
>
>
> objcopy -S -O binary boot2.out boot2.bin
> btxld -v -E 0x1000 -f bin -b
> /usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr  -o
> boot2.ld -P 1 boot2.bin
> btxld: /usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx: Not a BTX
> kernel
> *** Error code 1
>
> Stop in /usr/src/sys/boot/i386/boot2.
> *** Error code 1
>
> Stop in /usr/src/sys/boot/i386.
> *** Error code 1
>
> Stop in /usr/src/sys/boot.
> *** Error code 1
>
> Stop in /usr/src/sys.
> *** Error code 1
>
> Stop in /usr/src.
> *** Error code 1
>
> Stop in /usr/src.
> *** Error code 1
>
> Stop in /usr/src.
>
>
>
>   I scratched my head, and then ran 'make cleandir' a couple of times.
> Then I tried make buildworld again, and the same error comes up. I suppose
> I could try pulling down the whole source tree again, maybe a file is
> truncated, but before I do that, I wonder if anyone else may have anything
> I can try. Thanks,
>
>
>- Jamie
>


 As it turns out, the path to the m4 compiler was in /usr/local/bin/.
Creating a link from /usr/bin/m4 to /usr/local/bin/m4 solved the problem.


- Jamie



>
>
>
>
>
>
> The Moon is Full
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>

The Moon is Waning Gibbous (100% of Full)
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"