Talk:DragonFly BSD
| This is the talk page for discussing improvements to the DragonFly BSD article. This is not a forum for general discussion of the article's subject. |
Article policies
|
| Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
Archives: 1Auto-archiving period: 91 days  |
 | DragonFly BSD has been listed as one of the Engineering and technology good articles under the good article criteria. If you can improve it further, please do so. If it no longer meets these criteria, you can reassess it. | |||||||||
| ||||||||||
| This article is rated GA-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||
| |||||||||||||||||||||||||
.svg){kind=logo}
Clarification
edit@Bkouhi: I have hard time clarifying DragonFly BSD §§ Virtual kernel, HAMMER file system, and Application snapshots, as the text appears to be already very clear to me. Probably you could request clairification here, so that I could understand, what exactly seems unclear to you. — Dmitrij D. Czarkoff (talk•track) 07:29, 2 June 2014 (UTC)
- Many thanks for clarification, I removed those "clarification needed" tags, the text now looks smooth and clear to me, as you said, "Virtual kernel" and "Application snapshots" sections are already clear and I think HAMMER's docs clearly describes what "configurable file system history" means. Thank you very much. -- Bkouhi (talk) 09:54, 2 June 2014 (UTC)
TCP SACK?!?
editOne of the feature listed for 1.2 is "TCP SACK" -- something I've never heard of, so I wonder if that's just a misspelled "STACK". 76.147.42.136 (talk) 04:07, 26 April 2024 (UTC)
- it's not a misspelling of "STACK", it's short for selective acknowledgement. Guy Harris (talk) 05:43, 26 April 2024 (UTC)
Release history is backwards
editRelease history contains a table and a graphical timeline down the left border. In the state that the article loads as, the contents of this table are all backwards such that when reading down the page the earliest row encountered describes the latest version released and the latest row encountered describes the earliest version released. This looks absolutely extraordinary. The column headers can be clicked to sort and clicking Date does sort the table into chronological order but the graphical timeline to the left remains backwards and becomes desynchronised from the contents of the table. Just in case I was missing some emerging trend in right-to-left or bottom-to-top text flow I went ahead and checked:
and every one of these begins with the original version and concludes with the current version (the same way a log file or a book flows), while this article begins with the current version and concludes with the original version. I find this bizarre but there may be a legitimate reason for it -- perhaps linked with the graphical timeline. I would like to reorder the table for accessibility and consistency reasons. I'll leave it a couple of weeks to hear why it has developed this way in this specific article. 165.228.217.140 (talk) 23:48, 10 September 2024 (UTC)