Re: META: Does this list have no moderators?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sat, 4 Jun 2016 22:26:45 +0100 Gareth Nelsonwrote: > I'm sure we're all aware of the individual i'm thinking of when I say > their posts are both inappropriate and annoying. > > The individual in question should be referred privately to mental > health services, but they should also be prohibited from posting > further to this list. > > Thoughts? > Don' like wut UC? Press "N" for Next. Dhu - -- Je suis Canadien. Ce n'est pas Francais ou Anglaise. C'est une esp`ece de sauvage: ne obliviscaris, vix ea nostra voco;-) http://babayaga.neotext.ca/PublicKeys/Duncan_Patton_a_Campbell_pubkey.txt iF4EAREIAAYFAldYvlUACgkQiY6AzzR1lzy/ywEArraDE1brSY4pcIV9XU41yuWN AapejG4tIl6Nz9sKweEA/iI47LicKJAJ3fJ66VjrcZXd8/rNiA1c0P5B58vJZl0n =tfq0 -END PGP SIGNATURE-
Re: /usr/ and wxallowed
> Sorry, no, I should have been clearer. Man, so much confusion in this thread. All are mixed in usage: partition, mount point, filesystem, mount options, etc. Aren't they different anymore? I was reading about wx_ stuff since I will install a new snapshots, but this thread is too damn unclear. Sorry.
Re: /usr/ and wxallowed
> >> You can add it at any point. It just means that binaries in /usr > >> which do PROT_WRITE|PROT_EXEC mappings will succeed (with a warning, > >> of course). > >> > >> Over time, these semantics will probably change. > > > > If you would like the protection then I don't see any need to reinstall > > btw. > > > > I'm guessing (could be wrong) /usr isn't huge (so won't take ages) but > > it's dead easy to gain the protection by using cp -Rp /usr to /home/usr > > > > Then simply delete the /usr in disklabel and create a /usr > > and /usr/local and copy back /home/usr to /usr and /home/usr/local > > to /usr/local because cp is static and in the / root fs so you don't > > even need to reboot, of course you would have to consider running > > programs read requirements on those filesystems. > > > > So you are talking about moving /usr from its own filesystem to /. > Careful with that. If you follow the auto disklabel defaults, / is > usually max 1GB and after a couple of upgrades /usr can easily get > too big for that (new libraries, new perl versions, etc). I would > rather take longer to do a dump/repartition/restore (or do some > other carving up/rejiggling of partitions) rather than leave a > timebomb for my future self, updates with too little space for > /usr are not very funny. Sorry, no, I should have been clearer. Yeah, I meant creating two partitions in the previous /usr location with disklabel and not in the root filesystem. Sorry if anyone did otherwise but I assume it wouldn't fit. -- KISSIS - Keep It Simple So It's Securable
Re: FOSS tools for flashing motherboard BIOS?
On 2016-06-06, Alan Coreywrote: > The hard drive I stick in when I want some operating systems on one > has XP Pro and OpenBSD 5.2. OpenBSD 5.2 doesn't have libpci even in > ports so that rules out flashrom unless I want to try to build libpci > from sources (or a distfile). It was added in 4.0, it's in the pciutils port. But you won't be able to use it with flashrom without the patch that's in the flashrom port. > So, I guess I should look at BiosDisk too. Afaict BiosDisk is a way to generate a disk image with freedos on, to run the vendor's flash tool. You still need a way to boot that image. > On 6/6/16, Alan Corey wrote: >> OK, so that's why it wasn't in pbrowser yet. Running in single user >> mode sounds like a pain. Less of a pain than some options.. >> Also the install puts the man page in /usr/local/share/man/man8 It puts it in ${MANDIR}/man8, if you're not using the port then it's up to you to set MANDIR how you want during 'make install'. Anyway I wouldn't recommend flashrom on a machine with an EC that it reports as unsupported unless either you have confirmation that it works from somebody else and/or you have an alternative way to restore the flash. I'm not willing to say more than "it worked on my APU2".
Re: No slip anymore?
Hello, You may try to get a linux/other BSD distro including slip or add slip from sources over an openBSD installation. or use pppd from ip networking as mentionned. > > From: Roderick> Sent: Wed Jun 08 08:20:15 CEST 2016 > To: > Subject: Re: No slip anymore? > > > On Sat, 4 Jun 2016, Chris Cappuccio wrote: > > > I think modern computers, even on sticks, generally come with wireless and/or > > ethernet interfaces? > > The Lenovo Stick has Wlan (and Bluetooth). But it is an exageration to > use it to comunicate with a very old laptop (without wlan) immediately > near it. The more power consumption, the more heat in the small stick. > > > But don't fear, if you only have a serial port, you can > > still use pppd for IP networking. > > Yes, it is an alternative, but slip is not only simple for dealing > with its commands, but a very simple protocoll (see for example minix > man page). I wonder why its prensense in OpenBSD was considered a problem. > > Rodrigo. > Cordialement Francois Pussault 10 chemin de négo saoumos apt 202 - bat 2 31300 Toulouse +33 6 17 230 820 +33 5 34 365 269 fpussa...@contactoffice.fr
Re: No slip anymore?
On Wed, 08 Jun 2016, Roderickwrote: > If you have a very old laptop with a comfortable keyboard, then > minix is a good alternative to use the laptop for example as a > typewriter (and much more than that). Does your typewriter with 32 MB of RAM have Ethernet? I remember occasionally browsing the interwebs on one, as late as 2006.
Re: Joining bridge(4) changes broadcast?
On 08/06/16(Wed) 14:52, Masao Uebayashi wrote: > This is suboptimal with respect to performance, but "correctly work-around" > the problem, that is, bpf against an bridge'ed interface receives duplicate > frames. (It happens for not only broadcast but also unicast.) No way. > > diff --git a/sys/net/if.c b/sys/net/if.c > index 9b53bf1..5209281 100644 > --- a/sys/net/if.c > +++ b/sys/net/if.c > @@ -568,7 +568,8 @@ if_enqueue(struct ifnet *ifp, struct mbuf *m) > unsigned short mflags; > > #if NBRIDGE > 0 > - if (ifp->if_bridgeport && (m->m_flags & M_PROTO1) == 0) { > + /* Loop prevention. */ > + if (ifp->if_bridgeport != NULL && (m->m_flags & M_PROTO1) == 0) { > KERNEL_LOCK(); > error = bridge_output(ifp, m, NULL, NULL); > KERNEL_UNLOCK(); > @@ -618,7 +619,13 @@ if_input(struct ifnet *ifp, struct mbuf_list *ml) > if_bpf = ifp->if_bpf; > if (if_bpf) { > MBUF_LIST_FOREACH(ml, m) > - if (bpf_mtap_ether(if_bpf, m, BPF_DIRECTION_IN) != 0) > + if ( > +#if NBRIDGE > 0 > + /* Loop prevention. */ > + !(ifp->if_bridgeport != NULL && > + (m->m_flags & M_PROTO1) != 0) && > +#endif > + bpf_mtap_ether(if_bpf, m, BPF_DIRECTION_IN) != 0) > m->m_flags |= M_FILDROP; > } > #endif
Re: No slip anymore?
On Wed, 8 Jun 2016, Theo de Raadt wrote: now please go back to minix. Small memory footprint (kernel is 600 kB; full OS is 25 MB). If you have a very old laptop with a comfortable keyboard, then minix is a good alternative to use the laptop for example as a typewriter (and much more than that). And I find slip for connecting the old laptop to other computers, for example running OpenBSD, to make file transfer, also because of its simplicity, the right protocol. Secure connections are not always everything. I would not underestimate minix only because it has not the same goals or quality standards than OpenBSD. Rodrigo.
Re: No slip anymore?
> > But don't fear, if you only have a serial port, you can > > still use pppd for IP networking. > > Yes, it is an alternative, but slip is not only simple for dealing > with its commands, but a very simple protocoll (see for example minix > man page). I wonder why its prensense in OpenBSD was considered a problem. because. now please go back to minix.
Re: No slip anymore?
On Sat, 4 Jun 2016, Chris Cappuccio wrote: I think modern computers, even on sticks, generally come with wireless and/or ethernet interfaces? The Lenovo Stick has Wlan (and Bluetooth). But it is an exageration to use it to comunicate with a very old laptop (without wlan) immediately near it. The more power consumption, the more heat in the small stick. But don't fear, if you only have a serial port, you can still use pppd for IP networking. Yes, it is an alternative, but slip is not only simple for dealing with its commands, but a very simple protocoll (see for example minix man page). I wonder why its prensense in OpenBSD was considered a problem. Rodrigo.
Re: Joining bridge(4) changes broadcast?
This is suboptimal with respect to performance, but "correctly work-around" the problem, that is, bpf against an bridge'ed interface receives duplicate frames. (It happens for not only broadcast but also unicast.) diff --git a/sys/net/if.c b/sys/net/if.c index 9b53bf1..5209281 100644 --- a/sys/net/if.c +++ b/sys/net/if.c @@ -568,7 +568,8 @@ if_enqueue(struct ifnet *ifp, struct mbuf *m) unsigned short mflags; #if NBRIDGE > 0 - if (ifp->if_bridgeport && (m->m_flags & M_PROTO1) == 0) { + /* Loop prevention. */ + if (ifp->if_bridgeport != NULL && (m->m_flags & M_PROTO1) == 0) { KERNEL_LOCK(); error = bridge_output(ifp, m, NULL, NULL); KERNEL_UNLOCK(); @@ -618,7 +619,13 @@ if_input(struct ifnet *ifp, struct mbuf_list *ml) if_bpf = ifp->if_bpf; if (if_bpf) { MBUF_LIST_FOREACH(ml, m) - if (bpf_mtap_ether(if_bpf, m, BPF_DIRECTION_IN) != 0) + if ( +#if NBRIDGE > 0 + /* Loop prevention. */ + !(ifp->if_bridgeport != NULL && + (m->m_flags & M_PROTO1) != 0) && +#endif + bpf_mtap_ether(if_bpf, m, BPF_DIRECTION_IN) != 0) m->m_flags |= M_FILDROP; } #endif