https://marc.info/?l=openbsd-tech&m=162652200109398&w=2 I disagree.
while its technically correct with the rfc, in practice, not many OSes
rigidly enforces not using the router option when 121 is present that
I've used.
This is how dhcpleased works in -current:
1) if a client using dhcpleased
Thank you so much! I confirm that this works well and as intended. I
added this statement to my .profile for simplicity.
On 22/05/03 08:49AM, Stuart Henderson wrote:
> On 2022-05-02, ehakanduran wrote:
> > didn't) but I couldn't figure out a way to fix the second problem. Why
> > Ctrl-o doesn't wo
> what did you do exactly? Did you remount / ?
I have to use # mount -uw /
Without / it is against my initial purpose.
Solved.
On Wednesday, May 4, 2022, Stuart Henderson
wrote:
> On 2022-05-04, Marcus MERIGHI wrote:
> > Hello!
> >
> > I need to block http/s traffic, but only for some Host: header values.
> > I.e. domain "xyz.abc" should be reachable, domain "klm.opq" not, both
> > behind the same IP.
> >
> > This rules
Subscribe
--
Atenciosamente,
Fabio Martins
(+5521) 97914-8106 (Signal)
https://www.linkedin.com/in/fabio1337br/
On Wed, May 4, 2022, 20:55 Otto Moerbeek wrote:
>
> what did you do exactly? Did you remount / ?
>
I started with a fresh install of snapshots for amd64.
Original /etc/fstab:
0a4b310a4a014e04.b none swap sw
0a4b310a4a014e04.a / ffs rw 1 1
0a4b310a4a014e04.l /home ffs rw,nodev,nosuid 1 2
0a4b310
On 2022-05-04, Marcus MERIGHI wrote:
> Hello!
>
> I need to block http/s traffic, but only for some Host: header values.
> I.e. domain "xyz.abc" should be reachable, domain "klm.opq" not, both
> behind the same IP.
>
> This rules out blocking with PF.
>
> I looked at relayd(8)/relayd.conf(5) next
On Wed, May 04, 2022 at 08:35:50PM +0300, Mihai Popescu wrote:
> Hello,
>
> I want to map /tmp as a mfs type. I did this in my /etc/fstab:
>
> 0a4b310a4a014e04.b none swap sw
> 0a4b310a4a014e04.a / ffs rw 1 1
> 0a4b310a4a014e04.l /home ffs rw,nodev,nosuid 1 2
> swap /tmp mfs rw,nodev,nosuid,-s=1
Hello,
I want to map /tmp as a mfs type. I did this in my /etc/fstab:
0a4b310a4a014e04.b none swap sw
0a4b310a4a014e04.a / ffs rw 1 1
0a4b310a4a014e04.l /home ffs rw,nodev,nosuid 1 2
swap /tmp mfs rw,nodev,nosuid,-s=1g 0 0
0a4b310a4a014e04.f /usr ffs rw,nodev 1 2
0a4b310a4a014e04.g /usr/X11R6 ffs
How about someone simply (better than I) updating the manual page and
pkg_info output with warnings and clarifications about the intended use
case and risks?
Maybe the man page could say (just as an idea): "Warning: this is intended
to suggest files for removal, that it guesses are obsolete; if yo
On Wed, May 04, 2022 at 09:54:26AM -0600, Theo de Raadt wrote:
> Marc Espie wrote:
>
> > All the horrors stories I've seen in this discussion are related
> > to people trusting it blindly/automatically.
>
> But why wouldn't people trust it?
>
> All the documentation claims it produces a list of
Marc Espie wrote:
> All the horrors stories I've seen in this discussion are related
> to people trusting it blindly/automatically.
But why wouldn't people trust it?
All the documentation claims it produces a list of files that is obsolete.
It says those files are obsolete & unused -- with suc
On Wed, May 04, 2022 at 07:45:32AM -0400, Raul Miller wrote:
> On Wed, May 4, 2022 at 4:15 AM Sebastien Marie wrote:
> > The main problem I am seeing would be maintaining such lists, and it
> > necessary
> > means manual addition to add only "safe" files to remove (no libraries at
> > least).
>
Sebastien Marie wrote:
> a package could use old libraries, and such libraries will not be listed by
> sysclean.
the sysclean manual page claims that it correctly identifies "obsolete
filenames".
Obsolete, adj.
1.no longer produced or used; out of date.
But this is innaccurate. By your
On Wed, May 04, 2022 at 08:03:14AM -0600, Theo de Raadt wrote:
> Sebastien Marie wrote:
>
> > semarie@ spoke about integrating some elements inside the installer when he
> > was
> > about "clean _other things_". It isn't about "stepping back". Even if the
> > installer would clean all it is po
Sebastien Marie wrote:
> semarie@ spoke about integrating some elements inside the installer when he
> was
> about "clean _other things_". It isn't about "stepping back". Even if the
> installer would clean all it is possible to remove safely, I would still use
> a
> program to list librarie
On Wed, May 04, 2022 at 06:20:59AM -0600, Theo de Raadt wrote:
>
> Users are capable of creating linking against older lib*.so.* files.
> Such binaries could be anywhere on-disk, and we should not walk the entire
> disk to find them. Therefore such old libraries should NEVER be deleted.
>
> It i
Harald Dunkel wrote:
> Hi folks,
>
> I think the main problem is pretty easy to describe: OpenBSD loses track
> about what it had installed and cannot clean up its own files on a system
> upgrade.
No, that is incorrect.
Users are capable of creating linking against older lib*.so.* files.
Such
On Wed, May 4, 2022 at 4:15 AM Sebastien Marie wrote:
> The main problem I am seeing would be maintaining such lists, and it necessary
> means manual addition to add only "safe" files to remove (no libraries at
> least).
Conceptually speaking, it's possible to track library dependencies,
and it's
On Wed, May 04, 2022 at 07:42:54AM +0200, Harald Dunkel wrote:
> Hi folks,
>
> I think the main problem is pretty easy to describe: OpenBSD loses track
> about what it had installed and cannot clean up its own files on a system
> upgrade.
technically we are already tracking which files were insta
20 matches
Mail list logo
