Re: Kerberos
On Sat, 30 Jul 2022, Michael Dinon wrote: > Is it normal to have a Local Kerberos Realm configured on a brand new > MacBook? Wrong mailing list! You must have meant to send the question to freebsd-questi...@freebsd.org. That is where OS X users congregate. Cheers, Predrag
Kerberos
Is it normal to have a Local Kerberos Realm configured on a brand new MacBook? -- Kind regards, Mike
Re: Configuration of static ipv6 router
On 2022-07-28, Nicolas Goy wrote: > > Ok, I think I found the issue. > > The cisco is useing the address fe80:b2b:11fe:161::2 but for some > reason, openbsd doesn't link this. > > I cannot ping fe80:b2b:11fe:161::2%vport0 > > The system is adding fe80::%vport0/64 to the routing table. > > I am not sure, but I think that's the cause. > > I tried to add it to the routing table but it says "file exists". I suggest you send output from the commands which show the current actual state of the system, i.e. netstat -rnfinet6, ifconfig -A, etc. And instead of e.g. "I cannot ping X", show the actual command you typed and what happened. For anyone who might have an idea what's up, it's a lot easier to read these than it is to interpret information from english descriptions, and might give some clues from things which you didn't describe. Also it's much easier to compare this with how things look on a working system. I don't think there's a dmesg in the information scattered in the thread either, sometimes that is useful, which is why it's always requested.
Re: necessity to specify CVSROOT each time cvs is run?
On 2022-07-28, Chris Bennett wrote: > On Thu, Jul 28, 2022 at 08:13:46AM -, Stuart Henderson wrote: >> Either use -d, or set CVSROOT, or replace CVS/Root files with ones >> containing the path to the repo (cvschroot from the cvsutils package >> makes this easy). If your original checkout had been done via anoncvs >> you wouldn't have needed to do this. (Also ports.tar.gz misses some >> files - run "cvs up -Pd" across the whole tree to fetch them). >> > > I already use a script to do cvs for ports. > Right now, it downloads a copy of ports.tar.gz for "just in case cvs > checkout fails". > > Which method would be preferable for the other end (the cvs server)? > > ports.tar.gz then cvs up > or > cvs checkout > > Either method is fine for me, but which method would be preferable? Whichever works best for you ... > I don't get ports.tar.gz from the same server as cvs. > > Does a checkout put less load on the cvs server than running a > comparison with cvs up? Or is the increased data with checkout more > important to eliminate? I never use ports.tar.gz. Either do a cvs checkout directly from anoncvs, or if I'm on a machine with a poor net connection or where I might be offline and still want to access the repo I'll use reposync to get a local copy of the full repo (done via rsync-over-anonymous-ssh) and point CVSROOT there. -- Please keep replies on the mailing list.
Re: Verbose messages from pppoe(4)?
On 2022-07-29, Martin Schröder wrote: > Hi, > I'm using pppoe to connect to my provider via DSL on 7.1. > Since yesterday my connection has been very flaky. > > Is there a way to get more information about the connection state changes > etc.? > Currently I only see the occasional > > /bsd: pppoe0: LCP keepalive timeout > > in /var/log/messages > > I tried the debug setting in/etc/hostname.pppoe0, but that gives much > too much information. I normally point tcpdump at the parent ethernet interface if I'm wanting to see what pppoe is doing. I'd look at stats from the DSL router too. Graphing signal/noise, CRC/FEC errors, etc, can be helpful. -- Please keep replies on the mailing list.
Verbose messages from pppoe(4)?
Hi, I'm using pppoe to connect to my provider via DSL on 7.1. Since yesterday my connection has been very flaky. Is there a way to get more information about the connection state changes etc.? Currently I only see the occasional /bsd: pppoe0: LCP keepalive timeout in /var/log/messages I tried the debug setting in/etc/hostname.pppoe0, but that gives much too much information. Thanks in advance Martin
OpenBSD 7.1 : reorder_kernel: failed
Hello,
I recently used the multiprocessor kernel on my OpenBSD 7.1 computer,
using this command :
cp bsd bsd.sp && cp bsd.mp bsd
Since then, I have this message in /var/log/messages :
Jul 25 20:17:05 server reorder_kernel: failed -- see
/usr/share/relink/kernel/GENERIC.MP/relink.log
Here is the contents of the relink.log file :
(SHA256) /bsd: OK
LD="ld" sh makegap.sh 0x gapdummy.o
ld -T ld.script -X --warn-common -nopie -o newbsd ${SYSTEM_HEAD} vers.o
${OBJS}
ld: error: duplicate symbol: i915_get_bridge_dev
>>> defined at i915_drv.c:106
(/usr/src/sys/dev/pci/drm/i915/i915_drv.c:106)
>>> i915_drv.o:(i915_get_bridge_dev)
>>> defined at i915_dma.c:206
(/usr/src/sys/dev/pci/drm/i915/i915_dma.c:206)
>>> i915_dma.o:(.text+0x0)
*** Error 1 in /usr/share/relink/kernel/GENERIC.MP (Makefile:999
'newbsd': @echo ld -T ld.script -X --warn-common -nopie -o newbsd
'${SYSTEM...)
I did a :
sha256 -h /var/db/kernel.SHA256 /bsd
That did not change anything.
Here is what I have in / :
-rwx-- 2 root wheel 22977229 Jul 20 20:10 bsd
-rwx-- 1 root wheel 15629818 Sep 19 2019 bsd.backup
-rwx-- 2 root wheel 22977229 Jul 20 20:10 bsd.booted
-rw-r--r-- 1 root wheel 22977229 Apr 22 13:40 bsd.mp
-rw--- 1 root wheel 4606368 Apr 22 13:40 bsd.rd
-rw--- 1 root wheel 22863908 Jul 20 20:09 bsd.sp
The computer seems to run fine. I don't know if that error message is
important.
What's you opinion, could you help me with that message ?
Thank you !
Nicolas, Paris
PS : BTW, that's the computer which freezed some time ago. I sent some
messages about that issue in the past. From then, it hasn't freezed
anymore ! Fingers crossed !
Re: doas and args matching
On July 28, 2022 9:06:51 PM GMT+02:00, Chris Narkiewicz wrote: >On Thu, Jul 28, 2022 at 03:08:19PM +0200, Alexander Hall wrote: >> Just leaving out the "args ..." from the config should accomplish that. > >It would allow the user to set any wscons parameters, which is not optimal. > >But either += -= operators or custom shell script can do the job as well. Yup, I was referring to using the (not quoted) lines I wrote a bit up in a custom script. /Alexander > >Best regards, >Chris Narkiewicz
Re: doas and args matching
Maksim Rodin writes: $ /sbin/wsconsctl display.brightness=50 wsconsctl: /dev/ttyC0: Permission denied Did you forget to type "doas" before your command? Gah, apparently so. :-/ i try to be thorough when i check these things, but then i do something like this. Thank you. Chris: There you go - as Alexander said, just don't specify any argument to wsconsctl in /etc/doas.conf. Alexis.
Re: doas and args matching
> $ /sbin/wsconsctl display.brightness=50 wsconsctl: /dev/ttyC0: Permission > denied > Did you forget to type "doas" before your command? On Пт 29 июл 2022 15:38:37, Alexis wrote: > > Alexander Hall writes: > > > > There's a good chance i'm misunderstanding, but doesn't this run > > > into > > > the same issue? Namely, that (as far as i'm aware) it's not possible > > > to specify that a doas-permitted command be allowed to run with > > > arbitrary arguments (or range of arguments), rather than only the > > > arguments specified in doas.conf? > > > > Just leaving out the "args ..." from the config should accomplish that. > > Not on 7.1, unless i'm doing something wrong? > > /etc/doas.conf: > >permit nopass alexis as root cmd /sbin/wsconsctl > > Hence the OP's question, and my suggested kludge. > > > Alexis. > -- С уважением, Родин Максим
