r3 - 2004-10-29 - 12:38:50 - RobDayYou are here: NTP >  Dev Web > BitKeeperNotes > BkCheckOutEdit
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.8p15 was released on 23 June 2020. It addresses 1 medium-severity security issue in ntpd, and provides 13 non-security bugfixes over 4.2.8p13.

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.
In some cases, just the act of cloning a repository will also check out all of its files, so the rest of this section won't apply (that's the case with NTP repositories, for example). If not, you can selectively check out the files you want to examine with one of a number of bk commands. (Keep in mind that you can still query some of a file's properties without actually checking it out -- more on that shortly.)

Assuming we're still working with a copy of the linux-2.5 kernel source repo, and assuming you don't want to make any editing changes just yet (that comes later), here are some read-only checkout variations (check out bk helptool for more options for these commands):

 $ ls SCCS/                      # just to see what's available

 $ bk co Makefile                # check out read-only version of Makefile
 $ bk co                         # check out all files in this directory
 $ bk -r co                      # recursively check out from here down
 $ bk -r co -q                   # do it quietly (works with all of the above)

In simple cases, you can use the alternative bk get as well. Neither of these commands will change any of the contents of the SCCS/ directory in terms of locking or recording the read-only check out operation.

When you're finished examining a file or number of files, you can remove their gfiles with some variation of:

 $ bk clean
 $ bk unedit
both of which have options to operate on a single file, multiple files, recursively, quietly and so on.

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: 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-2022 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