The problem appears to be here:
> wdc2 at pcmcia0 function 0 "TRANSCEND, TS8GCF133, " port 0x340/16: irq 3
> wd1 at wdc2 channel 0 drive 0:
> wd1: 1-sector PIO, LBA48, 7647MB, 15662304 sectors
> wd1(wdc2:0:0): using BIOS timings
> a: 1060.6M 64 4.2BSD 2048 16384
Hi All,
The installation program on my Intel P5/80MB RAM machine works fine up
to 'Relinking to create unique kernel...', during which the system
either reboots or eventually prints a kernel panic message. If 80MB is
not enough under normal circumstances then it's not worth debugging.
Hey there,
I'll repaste my entire Tmux config to see if you would want to copy and paste a
few options that might be useful, again, check out 'gotbletu's videos on Tmux
since you might learn a few more things you never knew:
`# Set Default Terminal Emulator:
set -g default-terminal "urxvt"
#
Thank you Claudio for pointing me in the right direction.
My testing pf.conf seems to work as expected:
- vlan1002:network can ping vlan1003:network only
- vlan1003:network can't ping vlan1002:network
- there is no routing between other vlans
set block-policy drop
set loginterface egress
set
This is current/amd64 on a PC (dmesg below).
Two of my big disks show errors after a resume from zzz.
Here is a snippet of the error messages (full log below):
ahci_get_err_ccb but SACT 8000 != 0?
ahci_get_err_ccb but SACT 0004 != 0?
ahci_get_err_ccb but SACT 0020 != 0?
Thank you everyone for your helpful responses.
Initially I was trying to synchonize with keyboard shortcuts on my
Macbook (i.e., use Vim + Tmux similarly across all operating systems),
but it proved unfruitful due to complications around remapping the
Command key on MacOS. I was also trying to
On Wed, Jul 14, 2021 at 11:38:15AM +0200, Tom K wrote:
>
> > > but why? If I reboot the other node, the system become MASTER.
> >
> > That is because the other system stops sending carp announcements
> > when you reboot it. This is unrelated to the demote counter. The demote
> > counter only
but why? If I reboot the other node, the system become MASTER.
That is because the other system stops sending carp announcements
when you reboot it. This is unrelated to the demote counter. The demote
counter only matters as long as another carp MASTER remains visible.
A forced failover like
On Wed, Jul 14, 2021 at 08:28:09AM +0200, Tom K wrote:
> JP,
>
> but why? If I reboot the other node, the system become MASTER.
That is because the other system stops sending carp announcements
when you reboot it. This is unrelated to the demote counter. The demote
counter only matters as long
JP,
but why? If I reboot the other node, the system become MASTER. At this
time, no other system has more recent rule states and the 2nd system
comes back, the 1st will fall to BACKUP although it has no adskew
settings and demotecount still on 33.
I'm very confused about this issue.
Am
10 matches
Mail list logo
