Age | Commit message (Collapse) | Author |
|
configuration to perform a racy behaviour is not wise.
ok natano
|
|
|
|
virtio itself is not PCI, it is a paravirtual bus on top of either PCI
or MMIO (arm). This is the second step of moving the virtio files to
dev/pv. No functional change.
Moving the file is done by removing and adding it again - the old
history can be found in the Attic of sys/dev/pci/vmmci.c.
no objections from sf@ mlarkin@
|
|
virtio itself is not PCI, it is a paravirtual bus on top of either PCI
or MMIO (arm). This is the second step of moving the virtio files to
dev/pv. No functional change.
Moving the file is done by removing and adding it again - the old
history can be found in the Attic of sys/dev/pci/virtiovar.h.
no objections from sf@ mlarkin@
|
|
virtio itself is not PCI, it is a paravirtual bus on top of either PCI
or MMIO (arm). This is the second step of moving the virtio files to
dev/pv. No functional change.
Moving the file is done by removing and adding it again - the old
history can be found in the Attic of sys/dev/pci/virtioreg.h.
no objections from sf@ mlarkin@
|
|
virtio itself is not PCI, it is a paravirtual bus on top of either PCI
or MMIO (arm). This is the second step of moving the virtio files to
dev/pv. No functional change.
Moving the file is done by removing and adding it again - the old
history can be found in the Attic of sys/dev/pci/virtio.c.
no objections from sf@ mlarkin@
|
|
virtio itself is not PCI, it is a paravirtual bus on top of either PCI
or MMIO (arm). This is the second step of moving the virtio files to
dev/pv. No functional change.
Moving the file is done by removing and adding it again - the old
history can be found in the Attic of sys/dev/pci/vioscsireg.h.
no objections from sf@ mlarkin@
|
|
virtio itself is not PCI, it is a paravirtual bus on top of either PCI
or MMIO (arm). This is the second step of moving the virtio files to
dev/pv. No functional change.
Moving the file is done by removing and adding it again - the old
history can be found in the Attic of sys/dev/pci/vioscsi.c.
no objections from sf@ mlarkin@
|
|
virtio itself is not PCI, it is a paravirtual bus on top of either PCI
or MMIO (arm). This is the second step of moving the virtio files to
dev/pv. No functional change.
Moving the file is done by removing and adding it again - the old
history can be found in the Attic of sys/dev/pci/viornd.c.
no objections from sf@ mlarkin@
|
|
virtio itself is not PCI, it is a paravirtual bus on top of either PCI
or MMIO (arm). This is the second step of moving the virtio files to
dev/pv. No functional change.
Moving the file is done by removing and adding it again - the old
history can be found in the Attic of sys/dev/pci/viomb.c.
no objections from sf@ mlarkin@
|
|
virtio itself is not PCI, it is a paravirtual bus on top of either PCI
or MMIO (arm). This is the second step of moving the virtio files to
dev/pv. No functional change.
Moving the file is done by removing and adding it again - the old
history can be found in the Attic of sys/dev/pci/viocon.c.
no objections from sf@ mlarkin@
|
|
virtio itself is not PCI, it is a paravirtual bus on top of either PCI
or MMIO (arm). This is the second step of moving the virtio files to
dev/pv. No functional change.
Moving the file is done by removing and adding it again - the old
history can be found in the Attic of sys/dev/pci/vioblkreg.h.
no objections from sf@ mlarkin@
|
|
virtio itself is not PCI, it is a paravirtual bus on top of either PCI
or MMIO (arm). This is the second step of moving the virtio files to
dev/pv. No functional change.
Moving the file is done by removing and adding it again - the old
history can be found in the Attic of sys/dev/pci/vioblk.c.
no objections from sf@ mlarkin@
|
|
relying on the newstate task to do so. Fixes races of driver code against
mira timeouts leading to crashes in some situations, e.g. occasionally when
changing channels while the interface is up.
ok procter@
|
|
virtio itself is not PCI, it is a paravirtual bus on top of either PCI
or MMIO (arm). This is the second step of moving the virtio files to
dev/pv. No functional change.
Moving the file is done by removing and adding it again - the old
history can be found in the Attic of sys/dev/pci/if_vio.c.
no objections from sf@ mlarkin@
|
|
found. Makes gcc happier. Add __dead to function prototype as we
go by.
ok guenther@
|
|
ok jsing@
|
|
virtio itself is not PCI, it is a paravirtual bus on top of either PCI
or MMIO (arm). This is the first step of moving the virtio files to
dev/pv. No functional change.
arm kernel changes tested by jsg@ and patrick@
no objections from sf@ mlarkin@
|
|
ok jsing@
|
|
and makes gcc unhappy.
In-line the single use #define, eliminate the 256: case and remove
a now unneeded local variable.
ok guenther@
|
|
just use that. uses one less soreceive() loop per packet received.
hints from claudio@
|
|
rectification.
|
|
rectification.
|
|
|
|
matter for constant time, and make the public interface only used
external to the library.
This moves us to a model where the important things are constant time
versions unless you ask for them not to be, rather than the opposite.
I'll continue with this method by method.
Add regress tests for same.
ok jsing@
|
|
|
|
process. This seems to happen when we switch away from a proc
to kill it. We should probably start keeping a 'dummy' table
around.
|
|
give a sensible example for the domain {} section.
ok florian
|
|
ok florian
|
|
revokation works, the fullchain file will be unlinked.
ok florian
|
|
|
|
ok florian
|
|
OK benno
|
|
This way we can still chroot to certdir but the the certificate file
is not fixed to "cert.pem".
Writing of chain.pem and fullchain.pem is currently broken with this.
OK benno
|
|
on the Pine64. While there add a few more usb and pseudo devices.
|
|
|
|
in the way.
OK benno
|
|
OK benno
|
|
should be enclosed in parentheses.
ok deraadt@
|
|
|
|
|
|
OK benno
|
|
|
|
implement new -n option to check and print configuration
ok florian
|
|
fix getopt()
ok florian
|
|
mechanism as armv7. Remove it so no one starts to believe
we would do it that way.
|
|
change command line options:
n -> A new Account key
N -> D new Domain key
With this acme-client has these main usage patterns:
* create new Account Key and Domain Key and get a certificate:
acme-client -A -D www.example.com
* renew certificate:
acme-client www.example.com
* revoke certificate:
acme-client -r www.example.com
ok florian
|
|
- add challengedir option to config file
- remove -C option from command line
ok florian
|
|
start using the configuration file and delete command line arguments:
-a agreement -> agreement url ...
-c certdir -> domain certificate "path"
-f accountkey -> account key "path"
-k domainkey -> domain key "path"
-s authority -> sign with "name"
new argument:
-f configfile
the changes needed to use the new configuration are local to main.c for now.
While the configuration could be passed directly to netproc(), keyproc() etc,
the diff is smaller this way.
This also removes the multidir (-m) mode for now - specify different paths in
each domain {} block instead.
ok florian
|
|
|