The last time I followed the FAQ compiling kernels was on single processor
machines. I just installed OpenBSD on my daily driver dual core Intel
box. The kernel, userland, and xenocara compiles ran fine as usual. Then I
realized DOH! I was running the sp kernel since I never had a machine where
I n
On Sun, Dec 09, 2012 at 10:04:04AM +, John Long wrote:
| The last time I followed the FAQ compiling kernels was on single processor
| machines. I just installed OpenBSD on my daily driver dual core Intel
| box. The kernel, userland, and xenocara compiles ran fine as usual. Then I
| realized DOH
Thanks Paul. In that case I guess it would be simpler to do the sp kernel
first since the make install causes it to get booted. Then when I do the mp
kernel and install it everything will be ready to build the rest with the mp
kernel.
/jl
On Sun, Dec 09, 2012 at 11:45:03AM +0100, Paul de Weerd wr
On Sun, Dec 09, 2012 at 10:58:09AM +, John Long wrote:
| Thanks Paul. In that case I guess it would be simpler to do the sp kernel
| first since the make install causes it to get booted. Then when I do the mp
| kernel and install it everything will be ready to build the rest with the mp
| kerne
On Fri, Dec 7, 2012 at 4:24 PM, Chris Cappuccio wrote:
> Maximo Pech [mak...@gmail.com] wrote:
>> I said I can't code that.
>
> If you already knew the answer was "write it", then you asked the wrong
> question.
>
>> I know that gnupg is in the ports tree, but it
>> just seems strange to me that i
On Sun, Dec 09, 2012 at 12:21:34PM +0100, Paul de Weerd wrote:
> On Sun, Dec 09, 2012 at 10:58:09AM +, John Long wrote:
> | Thanks Paul. In that case I guess it would be simpler to do the sp kernel
> | first since the make install causes it to get booted. Then when I do the mp
> | kernel and in
On Fri, Dec 07, 2012 at 02:58:59PM -0800, Constantine A. Murenin wrote:
> On 11 January 2011 11:18, wrote:
> > The trick with /etc/boot.conf does work; this should transform the
> > cd48.iso install cd into a 'serial' one:
> >
> > $ echo 'set tty com0' > /tmp/boot.conf
> > $ growisofs -M cd48.iso
Hi,
I want to install OpenBSD 5.2 amd64 with PXE so I downloaded the latest bsd.rd
and pxeboot file from:
ftp://ftp.openbsd.org/pub/OpenBSD/5.2/amd64/
and put it on my TFTP/DHCP server but when I boot this specific files I get the
installer for OpenBSD 5.1 and not 5.2. Is this intentional? or
Nico Kadel-Garcia [nka...@gmail.com] wrote:
>
> SSH is the gold standard: OpenSSH is the popular and effective
> freeware version, which did solve a number of issues. The early
> history of SSH is interesting, and covered reasonably well at
> http://docstore.mik.ua/orelly/networking_2ndEd/ssh/ch01
On 12/09/12 06:50, Nico Kadel-Garcia wrote:
> On Fri, Dec 7, 2012 at 4:24 PM, Chris Cappuccio wrote:
,,,
>> OpenSSH and OpenBSD IPsec represent the OpenBSD solutions to the quality and
>> licensing problems in those areas. OpenSSH is still the gold standard,
>> OCF/IPsec,
>> maybe not. PGP worked
On 12/09/12 11:17, ML mail wrote:
> Hi,
>
> I want to install OpenBSD 5.2 amd64 with PXE so I downloaded the
> latest bsd.rd and pxeboot file from:
>
> ftp://ftp.openbsd.org/pub/OpenBSD/5.2/amd64/
>
> and put it on my TFTP/DHCP server but when I boot this specific files
> I get the installer for
Ah, you are right! It is indeed the RAMDISK for OpenBSD 5.2... I was using
symlinks on my TFTP server to point to the latest version of OpenBSD but it
looks like that somehow, although I changed the symlink to the latest version
(5.2 directory) TFTP was still serving the old symbolink link to the o
12 matches
Mail list logo
