headers
Rick Barter | 1 Jul 2003 01:07
Picon

Sendmail Bermuda Triangle ... I can't send any mail

I'm running OpenBSD 3.3 and can't seem to get any mail to go anywhere;
even locally.

===========================
Here's the situation:
===========================
Machine 1 = apollo
Machine 2 = zeus

I have a router doing NAT for my internal network and forwarding http
requests to apollo.

I am not running BIND.  I am using /etc/hosts and /etc/resolv.conf
files.

apollo can send email to itself and through my router to other
addresses on the Internet, but cannot seem to get any mail to zeus.

zeus cannot seem to send any mail to itself or anyone else.

Neither can receive email from outside.  This is okay for now.  I
think it has something to do with the fact that I use RoadRunner and
they block incoming packets on port 25.

I don't get errors or returned mail from either machine.  This leads
me to believe that zeus isn't doing anything with the messages.

I can ping and ssh from apollo to zeus and vice versa.  I can browse
the web from either machine.
(Continue reading)

Permalink | Reply | 4 comments |
headers
Chuck Yerkes | 1 Jul 2003 01:13

Re: Install INTEL C-Compiler and rebuild the COMPLETE System

Quoting Henning Brauer (lists-openbsd <at> bsws.de):
> On Mon, Jun 30, 2003 at 06:24:45PM -0400, Chuck Yerkes wrote:
> > Quoting Henning Brauer (lists-openbsd <at> bsws.de):
> > > On Mon, Jun 30, 2003 at 02:13:00PM -0600, Peter Valchev wrote:
> > > > > > gcc 2.95.3 code is in most cases slightly slower than gcc 3.x code, 
> > > > > > and intel code is even faster.
> > > > > > compile times with gcc 2.95.3 are by magnitudes shorter than with 
> > > > > > gcc 3.x and the intel compilers are even slower.
> > > > > Frankly, I don't care how long it takes to compile usually.
> > > > > I dealt with multi-day gcc bootstraps on Sparc 1's and 2's.
> > > > > Emacs used to be a several hour build.
> > > > > That's what other windows are for.
> > > > Other windows???  Other machines and CPUs too, what's your point?
> > > > It takes my VLC vax around 2 weeks to do a make build, I don't want to
> > > > imagine how long it will take using gcc3.
> > And is this vax still running out of geek-macho or is it running
> > for a practical reason
> 
> I have a Sun IPX running productive, because, well, it's up to the 
> task, perfectly reliable and I see no reason to change it.

Me too.  Except the SPARC 10 uses the same amount of power and
makes the same amount of head.
I build for the Sun4Cs on a 166MHz Sparc 10.
It takes less time and I get the binaries I need.

> I have a Pentium 60 running productive, because, well, it's up to the 
> task, perfectly reliable and I see no reason to change it. And I need 
> the ISA slot in it.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Peter Valchev | 1 Jul 2003 01:08

Re: Install INTEL C-Compiler and rebuild the COMPLETE System

> And is this vax still running out of geek-macho or is it running
> for a practical reason

I am using it, and have discovered & fixed numerous issues in OpenBSD
and in the OpenBSD ports tree by using this machine.  Why there?  See
below

> I have less tolerance for complaints about "my 12 year old (or even
> 5 year old)" machine takes too long to build.  Perhaps this would

Your tolerance is irrelevant here, I am not sure if you realise that.

> be a motivation to get cross compiling to work - imagine the Sun
> 4c build being done on a 3GHz Xeon.  OTOH, it's rare, outside of
> embedded systems, to *really* need cross compiling.

cross-compiling is a joke. then you end up with broken stuff that you
ship, just look at NetBSD.  we're not going to go that way, even if it
means "supporting" less architectures, we will at least support them.
building on a particular architecture is like a regression test, as i
said already

> If you're running BSD on a fully depreciated machine like a VAX
> and it's not because you are bound to hardware attached to it, then
> you'll likely save the money you spend on electricity and cooling
> by getting a new box.

The VLC is 1/4 the size of a sparc pizza box, a lot less weight (when I
got mine, I carried it for 15 blocks under my arm without feeling it)
and it has a VERY small power supply.  Saving electricity would actually
(Continue reading)

Permalink | Reply | 3 comments |
headers
Ryan | 1 Jul 2003 01:37

Partition Size Suggestions

Hi, I'm building a pf firewall using OpenBSD 3.3. The machine specs are:
Pentium 166, 128mb ram, and 1.6gb hard drive. This machine will just be
used as a firewall that will be up all the time. All 1.6gb will be used
for OpenBSD. I'm wondering how I should split the separate filesystems
up. Also, where should I place the log files? Thanks.

Ryan
Permalink | Reply | 11 comments |
headers
Chris Palmer | 1 Jul 2003 01:56

Re: Partition Size Suggestions

Ryan writes:

> Hi, I'm building a pf firewall using OpenBSD 3.3. The machine specs
> are: Pentium 166, 128mb ram, and 1.6gb hard drive. This machine will
> just be used as a firewall that will be up all the time. All 1.6gb
> will be used for OpenBSD. I'm wondering how I should split the
> separate filesystems up. Also, where should I place the log files?
> Thanks.

1. 128 - 256MB for swap and the rest for /.

2. 128 - 256MB swap, minimum needed for / and the rest for /var (to hold
logs).

More than 128MB swap may be overkill for a firewall. Personally I would
go for (1), for greatest flexibility.

And of course, unless you're actually going to read the logs, that's a
moot point. Usually places that need to keep logs for legal reasons or
such rotate them to offline storage (tape, CD, et c.) on a regular
basis.
Permalink | Reply | 1 comment |
headers
Jesse Kempf | 1 Jul 2003 02:01
Picon
Favicon

Re: Partition Size Suggestions


On Mon, 30 Jun 2003 18:37:42 -0500
"Ryan" <ryan <at> packetwatch.net> wrote:

> I'm wondering how I should split the separate filesystems up.
Probably by using the partitioning software that comes with the installer would.
> Also, where should I place the log files?
/var/log, maybe?
Permalink | Reply | 0 comments |
headers
Chuck Yerkes | 1 Jul 2003 02:24

Re: Partition Size Suggestions

Quoting Ryan (ryan <at> packetwatch.net):
> Hi, I'm building a pf firewall using OpenBSD 3.3. The machine specs are:
> Pentium 166, 128mb ram, and 1.6gb hard drive. This machine will just be
> used as a firewall that will be up all the time. All 1.6gb will be used
> for OpenBSD. I'm wondering how I should split the separate filesystems
> up. Also, where should I place the log files? Thanks.

I tend towards:

a: /   = ~50MB (or 100)
         I can mount / readonly with an mfs dev populated via rc
         room for a couple kernels
b: swap= 300MB  (generic rule of thumb of 2x RAM.  You'll likely never swap.)
d: /var= 200-500MB or so
         Mounted rw, nosuid, noexec, nodev  (yes, noexec > nosuid)
g: /usr= ~300-400MB  (room for base + local stuff within reason).
         Mounted readonly.  About always.
h: /home= 100MB or so.
         mounted rw, nosuid, nodev, perhaps noexec.
/tmp = mfs (limited via -s to 50mb), nosuid,noexec,nodev

Note:
  If it's rw, you can't execute
  If it's got executables, it's readonly.

/home won't hold much.  .files for admins, maybe a place to run stuff
up to.

The extra room can go to /var or /home as you want.
(Continue reading)

Permalink | Reply | 1 comment |
headers
qrw | 1 Jul 2003 02:52
Favicon

Proper way to backup (not tar)?

I've discovered that I may have been backing my OpenBSD systems up in not 
quite the right way.  Yesterday (while the system wasn't being used), I 
tried to upgrade the OpenBSD 3.2 system to 3.3.  I made a backup before 
using my usual method of tar'ing everything and putting them on a CD or 2.  
But it turned out that 3.3 isn't going to work for us right now, so I had 
to restore the 3.2 system. 

I reinstalled 3.2 and then just untar'ed everything.  But, not everything 
restored exactly.  It's up and running and I've gotten rid of most of the 
error messages.  But there are still a few little funny things happening.  
For example I can't use "su -r" to become root.  And it looking at it, it 
looks like the permissions are different in /usr/libexec/auth. 

I read the FAQ and see that there are instructions for backing up to tape 
using dump and restore.  Should I be using dump and restore instead of tar 
to do backups? 

Thanks 
  -Scott
Permalink | Reply | 2 comments |
headers
Peter Valchev | 1 Jul 2003 03:04
Picon
Favicon

1U or 2U fast P4 still wanted

The project still needs this.  Faster than the current machine, with
more PCI slots, and room for at least 3 disks... probably has to be 2U.
To make it clear, we don't want a slower or the same speed box...

This is to replace the current machine, which builds the release
packages and ports snapshots all the time - it is an important
infrastructure box.  What we have right now is a P3 1GHz 1U machine,
with pci64 slots which takes registered DIMMs.  The problem we have is,
that we need at least one pci32 slot to be able to plug a serial card
into, in order to connect the other machines to it.  Something faster
may be nice as well, considering all this machine does, is compile
software continuously.
Permalink | Reply | 0 comments |
headers
Chuck Yerkes | 1 Jul 2003 03:06

Re: Install INTEL C-Compiler and rebuild the COMPLETE System

Quoting Peter Valchev (pvalchev <at> sightly.net):
> > And is this vax still running out of geek-macho or is it running
> > for a practical reason
> I am using it, and have discovered & fixed numerous issues in OpenBSD
> and in the OpenBSD ports tree by using this machine.  Why there?  See
> below
You are confusing cause and effect.  See below (bottom).

> cross-compiling is a joke. then you end up with broken stuff that you
> ship, just look at NetBSD.  we're not going to go that way, even if it
> means "supporting" less architectures, we will at least support them.
> building on a particular architecture is like a regression test, as i
> said already

So rather than use regression tests, you hope that a port might trigger
problems?  Computer scientology.

> The VLC is 1/4 the size of a sparc pizza box, a lot less weight (when I
> got mine, I carried it for 15 blocks under my arm without feeling it)
> and it has a VERY small power supply.  Saving electricity would actually
> be a good reason for using it...

Hmmm, I've been carrying a 12W Soekris to/from work.  It fits in my
motorcycle jacket pocket.  Does that make me more of a man?  No.
(but I still build for it on a 2 CPU 2GHz Intel box).  (and no,
you don't see the letters OpenBSD in that paragraph, but that's for
reasons of hardware support).
It may be faster than your VAX and it lasts something like 4 days on
a small UPS.
(Continue reading)

Permalink | Reply | 2 comments |

Gmane