mirror of
https://github.com/hanzoai/volume.git
synced 2026-10-30 14:55:30 +00:00
zeekay
b61441f7d7
A fork of Rancher's local-path-provisioner at v0.0.36. The behaviour is unchanged and deliberately so — a directory on the node a pod lands on is the right thing for a disk. What changes is identity. The provisioner answers to hanzo.ai/volume rather than rancher.io/local-path. That is not branding: two provisioners sharing one name race for the same claims, and a stock k3s carries the upstream one, so a cluster running both would settle our storage by chance. Data lives at /var/lib/hanzo/volume, so reading a Hanzo cluster does not mean learning another vendor's directory. Apache-2.0 as published, unaltered, with Rancher's attribution in NOTICE. The README says what this is not: durability. A volume here dies with its node. That is hanzoai/replicate's question, one layer up, and keeping the two apart is what lets the disk stay this simple.
37 lines
680 B
Go
37 lines
680 B
Go
// Copyright 2016 The Go Authors. All rights reserved.
|
|
// Use of this source code is governed by a BSD-style
|
|
// license that can be found in the LICENSE file.
|
|
|
|
// Bluetooth sockets and messages
|
|
|
|
package unix
|
|
|
|
// Bluetooth Protocols
|
|
const (
|
|
BTPROTO_L2CAP = 0
|
|
BTPROTO_HCI = 1
|
|
BTPROTO_SCO = 2
|
|
BTPROTO_RFCOMM = 3
|
|
BTPROTO_BNEP = 4
|
|
BTPROTO_CMTP = 5
|
|
BTPROTO_HIDP = 6
|
|
BTPROTO_AVDTP = 7
|
|
)
|
|
|
|
const (
|
|
HCI_CHANNEL_RAW = 0
|
|
HCI_CHANNEL_USER = 1
|
|
HCI_CHANNEL_MONITOR = 2
|
|
HCI_CHANNEL_CONTROL = 3
|
|
HCI_CHANNEL_LOGGING = 4
|
|
)
|
|
|
|
// Socketoption Level
|
|
const (
|
|
SOL_BLUETOOTH = 0x112
|
|
SOL_HCI = 0x0
|
|
SOL_L2CAP = 0x6
|
|
SOL_RFCOMM = 0x12
|
|
SOL_SCO = 0x11
|
|
)
|