Using -CURRENT as of a few hours ago:
---
FreeBSD/i386 bootstrap loader, Revision 1.1
([EMAIL PROTECTED], Sun Aug 10 13:37:08 CEST 2003)
Loading /boot/defaults/loader.conf
Error: stack overflow
\
/boot/kernel/kernel text=0x30ee80 data=0x33f98+0x57160
syms=[0x4+0x3c2d0+0x4+0x4
a11b]
Hit [Enter]
On Fri, 11 Apr 2003, Bruce Evans wrote:
> On Thu, 10 Apr 2003, Lucky Green wrote:
>
> > I compiled a kernel with "options NO_SWAPPING", yet CURRENT still
> > attempts to allocate swap space:
>
> NO_SWAPPING has nothing to do with not allocating swap space. It
> Poul-Henning wrote:
> > Make sure you have rev 1.9 of src/sys/geom/bde/g_bde_crypt.c
> > I hadn't done my math and before that rev gbde would request
> > very large lumps of ram from malloc(9).
For a few hours, I thought that rev 1.9 may have fixed the problem, but
I just received another "ENO
I am seeing a lot of crashes of GBDE, causing "ENOMEM" errors to scroll
rapidly on the console. Whenever this happens, the server becomes
unresponsive to keyboard or any other input and has to be power cycled.
Is there some debug setting that I can set which would help diagnose the
problem further?
I am writing a section for the Handbook on how to use gbde. Currently,
using gbde is a rather manual process. Each time a host reboots, the
admin needs to attach the gbde device(s), enter any required
passphrases, manually fsck the partition, and mount it.
I suspect some subscribers to this mailin
allation. I even flashed in the latest BIOS, but that
had no effect. (The hardware has since been re-tasked and is no longer
available for testing).
--Lucky Green
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I just spent a few days trying to determine why postfix with STARTTLS
enabled is instantly dumping core on my new FreeBSD 5.0 machine.
The problem was caused by a conflict between OpenSSL library versions
0.9.6 and 0.9.7, both of which are installed on the machine. The former
as part of the FreeBS
erboards. <http://people.freebsd.org/~dwhite/ipmi/>, but it seems to
address a slightly different question.
Thanks in advance,
--Lucky Green
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I have a dual PIII Intel L440gx+ (VA Linux) server. I am running CURRENT
cvsupped a few hours ago.
This motherboard provides access to the BIOS via sio1. When booting, the
serial BIOS shows everything that's happening until the point of booting
the kernel (where it seems to switch video modes to h
Miguel wrote:
> Having no swap will prevent you from getting crashdumps in
> case of panic which, if you run 5.0, is not that unusual.
> Besides these days harddrives cost $1/GB, so why not setup
> the swap partition anyway?
I don't want cleartext cryptographic keys to ever touch magnetic media
I am about to set up a FreeBSD 5.0 machine without a swap partition. The
server has 1GB of RAM. Are there any caveats that I need to consider
during installation or configuration?
Thanks,
--Lucky
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the
A few folks have asked me if I knew if there is an how-to that could be
used as a basis for upgrading a STABLE box to 5.0 using not the
procedures in UPGRADING, but rather performing a clean 5.0 install on a
fresh disk followed by restoring whatever is required to make the new
install look like the
I plan to deploy GBDE in an environment in which the absolute maximum of
the system that can reasonably be kept encrypted on disk will be kept
in an encrypted format.
The system has the following requirements:
1) It must remain possible to administer the host over ssh. This
includes rebooting the
Are there any potential draw backs to enabling DRM_LINUX? Or should
DRM_LINUX be enabled whenever one enables COMPAT_LINUX?
This has not been clear to me from reading NOTES.
Thanks,
--Lucky Green
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in t
a machine on which ssh2 is not available would
manually need to enable ssh1 login in their sshd_config file. But I
would argue that permitting ssh1 login into a machine should be a
conscious act taken by the administrator by editing the config file, not
something that a distribution should enable
images somewhere.
It would be very helpful if somebody could provide those of us ready to
start testing with the precise URL to the floppies/ISOs of a particular
build that should be tested.
--Lucky Green, who earlier today installed the HD on which 5.0 will
live.
To Unsubscribe: send mail to
of
FreeBSD and hope the FreeBSD team will consider this change.
Thanks,
--Lucky Green
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
e 5.0 release by, say, January?
I am aware that there is existing FireWire code, I am just wondering by
when you think the integration will likely be done.
Thanks in advance,
--Lucky Green
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
onfig file.
3) Compatibility reducing security is typically not a good thing.
I therefore would like to ask the FreeBSD team to please consider to, in
the default configuration of FreeBSD 5.0, only enable ssh2 for sshd.
Thanks,
--Lucky Green
To Unsubscribe: send mail to [EMAIL PROTECTED]
with &q
19 matches
Mail list logo
