cho...@jtan.com wrote:
> It seems that the OpenBSD devs and/or project "support" only an
> installation which has not not taken advantage of any of the optional
> non-extras (primarily: not installing sets) the installer has to
> offer. I understand and agree with the reasons for this but I
cho...@jtan.com wrote:
> Patronisation aside, your computer's storage is a lot cheaper than the
> mental effort required to deal with a system that's non-standard but
> only by having a few bits wasted by their _complete lack of use_.
well said.
On 9/17/19 12:23 PM, Marc Espie wrote:
> On Tue, Sep 17, 2019 at 02:31:59PM -, Stuart Henderson wrote:
>> (To be clear, I think installing a restricted subset of the OS for
>> security reasons is pointless here, but can be really helpful when you
>> have to deal with limited space in
On Tue, Sep 17, 2019 at 02:31:59PM -, Stuart Henderson wrote:
> (To be clear, I think installing a restricted subset of the OS for
> security reasons is pointless here, but can be really helpful when you
> have to deal with limited space in partitions - and those just saying
> "storage is
>> | > Where sysupgrade ? reboot the machine, see your disks overflow. Boom
>> machine
>> | > kaput.
Disk overflow -> boom can happen anyway even if you had installed all sets
previously.
>> | The problem boils down to: how does sysupgrade, or any other tool, know
>> | which sets have been
Paul de Weerd writes:
> On Tue, Sep 17, 2019 at 03:14:22PM +0200, Marc Espie wrote:
> | On Tue, Sep 17, 2019 at 01:48:19PM +0200, Paul de Weerd wrote:
> | > On Tue, Sep 17, 2019 at 01:27:23PM +0200, Marc Espie wrote:
> | > | > By having each set install a specific file in a well-known location.
>
On Tue, Sep 17, 2019 at 03:14:22PM +0200, Marc Espie wrote:
| On Tue, Sep 17, 2019 at 01:48:19PM +0200, Paul de Weerd wrote:
| > On Tue, Sep 17, 2019 at 01:27:23PM +0200, Marc Espie wrote:
| > | > By having each set install a specific file in a well-known location.
| > | > Before sysupgrade I
On Tue, Sep 17, 2019 at 01:48:19PM +0200, Paul de Weerd wrote:
> On Tue, Sep 17, 2019 at 01:27:23PM +0200, Marc Espie wrote:
> | > By having each set install a specific file in a well-known location.
> | > Before sysupgrade I wrote my own script to upgrade machines, this uses
> | >
On Tue, Sep 17, 2019 at 01:27:23PM +0200, Marc Espie wrote:
| > By having each set install a specific file in a well-known location.
| > Before sysupgrade I wrote my own script to upgrade machines, this uses
| > /var/db/sets/{base,comp,game,man,xbase,xfont,xserve,xshare} to
| > determine what has
On Tue, Sep 17, 2019 at 01:08:45PM +0200, Florian Obser wrote:
> On Tue, Sep 17, 2019 at 09:43:20AM +0200, Marc Espie wrote:
> > I'm a bit surprised nobody looked at instrumenting what sets are actually
> > installed on a machine during install/manual upgrade and cloning that
> > into sysupgrade
On Tue, Sep 17, 2019 at 09:01:47AM +0100, cho...@jtan.com wrote:
> Marc Espie writes:
> > I'm a bit surprised nobody looked at instrumenting what sets are actually
> > installed on a machine during install/manual upgrade and cloning that
> > into sysupgrade to avoid this kind of surprise...
>
>
On Tue, Sep 17, 2019 at 01:15:06PM +0200, Paul de Weerd wrote:
> On Tue, Sep 17, 2019 at 09:39:00AM +0100, cho...@jtan.com wrote:
> | Marc Espie writes:
> | > On Tue, Sep 17, 2019 at 09:01:47AM +0100, cho...@jtan.com wrote:
> | > > Marc Espie writes:
> | > > > I'm a bit surprised nobody looked at
On Tue, Sep 17, 2019 at 09:39:00AM +0100, cho...@jtan.com wrote:
| Marc Espie writes:
| > On Tue, Sep 17, 2019 at 09:01:47AM +0100, cho...@jtan.com wrote:
| > > Marc Espie writes:
| > > > I'm a bit surprised nobody looked at instrumenting what sets are
actually
| > > > installed on a machine
On Tue, Sep 17, 2019 at 09:43:20AM +0200, Marc Espie wrote:
> I'm a bit surprised nobody looked at instrumenting what sets are actually
> installed on a machine during install/manual upgrade and cloning that
> into sysupgrade to avoid this kind of surprise...
>
Yeah, I think sysupgrade was a
Marc Espie writes:
> On Tue, Sep 17, 2019 at 09:01:47AM +0100, cho...@jtan.com wrote:
> > Marc Espie writes:
> > > I'm a bit surprised nobody looked at instrumenting what sets are actually
> > > installed on a machine during install/manual upgrade and cloning that
> > > into sysupgrade to avoid
On Tue, Sep 17, 2019 at 09:01:47AM +0100, cho...@jtan.com wrote:
> Marc Espie writes:
> > I'm a bit surprised nobody looked at instrumenting what sets are actually
> > installed on a machine during install/manual upgrade and cloning that
> > into sysupgrade to avoid this kind of surprise...
>
>
In particular, installing OpenBSD requires the following steps:
1) Partition and format the disc.
2) Untar a bunch of stuff (or in the case of /bsd*, copy).
3) Install the bootloader.
That's _it_. The few other tasks performed by the installer, like
installing /etc/hostname.*, KARL and
Marc Espie writes:
> I'm a bit surprised nobody looked at instrumenting what sets are actually
> installed on a machine during install/manual upgrade and cloning that
> into sysupgrade to avoid this kind of surprise...
I mentioned the possibility wrt. syspatch but it was rejected in favour
of
On Sun, Sep 15, 2019 at 08:02:05AM +0200, Marcus MERIGHI wrote:
> Morning Judah!
>
> koche...@hotmail.com (Judah Kocher), 2019.09.15 (Sun) 05:12 (CEST):
> > I ran it and found too late that it installed all the x*, Comp and Game
> > sets, which were not part of the original install.
>
> My reasoning behind NOT installing the X, Comp and Game sets have
> little
> to do with saving space, although I am using an 8GB SSD. I learned in my
> research that one of the most fundamental ways to improve network/system
> security is to minimize the attack surface by not installing
Judah Kocher writes:
> My router is headless. I have never run into an issue where I have
> needed anything from the X sets
Apparently you just did.
> Therefore it seems like sound logic to not have those
> bits and bytes present on the system so any
> mis-configurations/bugs/vulnerabilities
Thanks for the replies and ideas.
I was introduced to OpenBSD after an acquaintance had their home router
compromised in 2016 and I started looking into network
hardening/security. In my research trying to find the best firewall that
didn't require purchasing commercial hardware/licensing I
On 2019-09-15, Judah Kocher wrote:
> Thanks to the OpenBSD team for their awesome software!
>
> I have been running an Openbsd router for a few years now, mostly
> following current. Today I decided to try out sysupgrade rather than
> going through the usual manual process. I've read up on it a
Marcus MERIGHI writes:
> please do *not* copy/paste/run this command!
> something along these lines for the sets you did not want:
>
> $ ftp -MVo- $( tzf - | xargs rm
>
> you are aware that it is recommended to run with all sets?
Despite previous posts requesting assistance with not doing so,
Morning Judah!
koche...@hotmail.com (Judah Kocher), 2019.09.15 (Sun) 05:12 (CEST):
> I ran it and found too late that it installed all the x*, Comp and Game
> sets, which were not part of the original install. Unfortunately this
> overfilled my /usr partition and I'm getting errors on boot.
>
Thanks to the OpenBSD team for their awesome software!
I have been running an Openbsd router for a few years now, mostly
following current. Today I decided to try out sysupgrade rather than
going through the usual manual process. I've read up on it a few times
and it seemed pretty
26 matches
Mail list logo
