r5 - 2004-11-05 - 10:41:36 - RobDayYou are here: NTP >  Dev Web > BitKeeperNotes > BkClone
NTP users are strongly urged to take immediate action to ensure that their NTP daemons are not susceptible to being used in distributed denial-of-service (DDoS) attacks. Please also take this opportunity to defeat denial-of-service attacks by implementing Ingress and Egress filtering through BCP38.

ntp-4.2.8p13 was released on 07 March 2019. It addresses 1 medium-severity security issue in ntpd, and provides 17 non-security bugfixes and 1 other improvements over 4.2.8p12.

Please see the NTP Security Notice for vulnerability and mitigation details.

Are you using Autokey in production? If so, please contact Harlan - he's got some questions for you.
Your first step in working with a remote repository is to "clone" a copy of it to your local system with, say:
 $ bk clone http://linux.bkbits.net:8080/linux-2.5 mykernel
The above will clone that bk repository into the directory named, in your case, mykernel. By default, the directory name will match the repository name, so it's your choice if you want to use a different name.

Once this is done, you can enter your new directory with:

 $ cd mykernel
and you'll notice that there are (typically, but not always) no visible files -- everything is initially stored in SCCS directories, and you'll need to "check out" or "edit" files to get at them. More on that shortly.

There are a number of ways you can identify a remote repository; check under bk helptool url for the possibilities.

Advanced: If you're feeling ambitious, you can clone a specific snapshot of a remote repo using the -r option, with one of these possibilities:

 -r<cset rev number>
 -r<cset key>
 -r<tag name>

But, for now, you'll probably just want the default, most recent version.

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r5 < r4 < r3 < r2 < r1 | More topic actions
 
SSL security by CAcert
Get the CAcert Root Certificate
This site is powered by the TWiki collaboration platform
IPv6 Ready
Copyright & 1999-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Ideas, requests, problems regarding the site? Send feedback