Re: man-dev.freebsd.org

On 17/05/2025 15:21, Tomek CEDRO wrote: … URLs will be invalidated if we switch the sites in current form. … Permalinks, in particular, should remain valid. Thanks

Re: How does one upgrade a poudriere-devel METHOD pkgbase 14.2-RELEASE-p? jail to be a 14.3-RELEASE based one?

Mark Millard writes: > # poudriere jail -l > JAILNAME VERSION OSVERSION ARCH METHOD TIMESTAMP >PATH > release-aarch64 14.2-RELEASE-p1 aarch64 pkgbase 2025-06-06 21:19:04 > /usr/local/poudriere/jails/release-aarch64 > > NOTE: updates within 14.2-RELEASE-p* did

Re: Proposed revision of freebsd.org

On Mon, Jun 2, 2025, at 17:52, devnull wrote: > I loved the proposal! Thanks. :) > But, it might be interesting to remove js dependency. Regarding js, two notes: 1. If you're referring to livereload.js, please ignore that. It's there because my link is to a dev hugo server and that js is a hug

Re: Proposed revision of freebsd.org

I loved the proposal! But, it might be interesting to remove js dependency. On 14/05/25 20:34, Rebecca Cran wrote: I like it! One area that might need some focus is making sure it's accessible for blind or low-vision users.

Re: [Bug 287148] Handbook chapter 22 on ZFS is so outdated it is actually plainly wrong today

On Thu, May 29, 2025, at 10:31, bugzilla-nore...@freebsd.org wrote: > Now I was certain that at least FreeBSD's own docs would of course show how to > create a proper GPT partition to use for ZFS etc. and wanted to drop them a > link to the handbook. > > To my great surprise and dismay the handboo

Re: Updating build and jail manual pages to include missing or obscure information

On 5/22/25 12:27, Lexi Winter wrote: resin-free...@g-cipher.net: Just to share my two cents: I think all available options should be documented in the manual. i'm fine with having 'make world' documented somewhere, although such documentation should probably note that it's been deprecated for

Re: Updating build and jail manual pages to include missing or obscure information

resin-free...@g-cipher.net: > On 5/22/25 09:16, Lexi Winter wrote: > > note that 'make world' already doesn't work unless you're using DESTDIR > > (or you set a special make knob) so it shouldn't be documented as a way > > of upgrading the system in general, e.g. in build(7). > Just to share my tw

Re: Updating build and jail manual pages to include missing or obscure information

Re: Updating build and jail manual pages to include missing or obscure information

Warner Losh: > On Thu, May 22, 2025, 7:40 AM Alexander Ziaee wrote: > > There seems to be a rough consensus that we should remove the world and > > kernel targets. > > I object to removing these. I do agree we should document other methods, > but my spidt sense is this is still in use... note th

Re: Updating build and jail manual pages to include missing or obscure information

On 2025-05-22 02:05 -04:00 EDT, "Dave Cottlehuber" wrote: > On Tue, 20 May 2025, at 21:17, Billiam Crashkopf wrote: >> Hello all, >> >> I recently had a bit of trouble finding the proper make targets to build >> and install the base FreeBSD system from source into an empty directory >> for use i

Re: man-dev.freebsd.org

On Sat, May 17, 2025 at 12:27 AM Alexander Ziaee wrote: > Hello, > I am very interested in man-dev.freebsd.org. It provides a notably more > mobile friendly interface than man.freebsd.org. The pages have not been > updated in several years. I am interested in maintaining this. Hello Alex :-) S

Re: man-dev.freebsd.org

On Sat, May 17, 2025, 12:27 AM Alexander Ziaee wrote: > Hello, > > I am very interested in man-dev.freebsd.org. It provides a notably more > mobile friendly interface than man.freebsd.org. The pages have not been > updated in several years. I am interested in maintaining this. > > Best, > Alex

Re: Proposed revision of freebsd.org

On Wed, May 14, 2025, at 16:34, Rebecca Cran wrote: > I like it! > > One area that might need some focus is making sure it's accessible for blind > or low-vision users. > Thank you for the feedback. And absolutely. Accessibility is a must.

Re: Proposed revision of freebsd.org

I like it! One area that might need some focus is making sure it's accessible for blind or low-vision users. -- Rebecca On 5/14/25 08:46, Mark McBride wrote: Hello, I've been working on mock up of what a revised project front page might look like with feedback from folks on IRC and Disc

Re: Proposed revision of freebsd.org

Thanks for the feedback! On Wed, May 14, 2025, at 10:37, Tomek CEDRO wrote: > - I would keep this "New to FreeBSD" button under "Get Started" and > above releases table :-) I agree with the intent to get new users information. I can make that change easy enough. That said, you raise an importa

Re: Proposed revision of freebsd.org

On Wed, May 14, 2025 at 4:46 PM Mark McBride wrote: > Hello, > I've been working on mock up of what a revised project front page might look > like with feedback from folks on IRC and Discord and I'd like to see if there > is project interest in pursuing it: > > https://freebsd.markmcb.com/ > (..

Re: Proposed revision of freebsd.org

On Wed, May 14, 2025, at 08:06, Sergio Carlavilla wrote: > > The only problems I see are: > - The beastie logo, it's from and old design. > - The other logos, not by the logos itself, the problem is the license of the > logos used. Regarding beastie, I originally didn't include it. There was a

Re: Proposed revision of freebsd.org

On Wed, May 14, 2025, 4:46 PM Mark McBride wrote: > Hello, > > I've been working on mock up of what a revised project front page might > look like with feedback from folks on IRC and Discord and I'd like to see > if there is project interest in pursuing it: > > https://freebsd.markmcb.com/ > > Th

Re: HEADS UP: doc/ slush begins for 14.3R-RELEASE

Le 25.04.2025 12:04, Marc Fonvieille a écrit : > Hello, > > As announced, the doc tree is now in a slush. Please postpone all > non-essential changes until after the doc tree is tagged (currently > scheduled for 9 May, 2025). > > Please note that the slush does not apply to website/ documents. >

Re: [Bug 275685] Jails chapter of the handbook doesn't refer to FreeBSD version 14.0

No problem  Sent from Yahoo Mail for iPhone On Friday, April 18, 2025, 12:50 pm, bugzilla-nore...@freebsd.org wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275685 Benedict Reuschling changed:           What    |Removed                    |Added ---

Re: Moving vinum to docs-archive

On Sun, 13 Apr 2025, 21:02-, Alexander Ziaee wrote: > > On 2025-04-13 16:30 -04:00 EDT, "Jamie Landeg-Jones" > wrote: > > Maxim Konovalov wrote: > > > >> I don't believe that any of our supported versions have vinum as it > >> was removed a decade ago. For those who want to run FreeBSD 10

Re: Moving vinum to docs-archive

On 2025-04-13 16:30 -04:00 EDT, "Jamie Landeg-Jones" wrote: > Maxim Konovalov wrote: > >> I don't believe that any of our supported versions have vinum as it >> was removed a decade ago. For those who want to run FreeBSD 10 or >> earlier we have a VCS for docs. > > Ah, that's fine then. Sorr

Re: Moving vinum to docs-archive

Maxim Konovalov wrote: > I don't believe that any of our supported versions have vinum as it > was removed a decade ago. For those who want to run FreeBSD 10 or > earlier we have a VCS for docs. Ah, that's fine then. Sorry, I thought it had been removed in 15.0. cheers, J

Re: Moving vinum to docs-archive

On Sun, 13 Apr 2025, 08:46+0100, Jamie Landeg-Jones wrote: > Maxim Konovalov wrote: > > > I'd remove it completely. > > I personally don't have a problem with that, but generally speaking, > shouldn't documentation reflect supported releases, not just the > latest release? > > At the very least,

Re: Moving vinum to docs-archive

Hello  Can you explain bit detail regarding specifically and to whom  I need to some advice certain parts especially gates keeping  Many thanks and appreciate for understanding  Sent from Yahoo Mail for iPhone On Sunday, April 13, 2025, 9:46 am, Jamie Landeg-Jones wrote: Maxim Konovalov wr

Re: Moving vinum to docs-archive

Maxim Konovalov wrote: > I'd remove it completely. I personally don't have a problem with that, but generally speaking, shouldn't documentation reflect supported releases, not just the latest release? At the very least, I'd expect the page to mention deprecation and link to the original documen

Re: Moving vinum to docs-archive

> On Sun, 13 Apr 2025, 01:53-, Alexander Ziaee wrote: >> Can we keep the vinum [0] article, but move it to docs-archive? gvinum(8) >> was removed in January, 2025, and vinum(4) was removed in March, 2013. On 2025-04-12 22:44 -04:00 EDT, "Maxim Konovalov" wrote: > I'd remove it completely. I

Re: Moving vinum to docs-archive

I'd remove it completely. On Sun, 13 Apr 2025, 01:53-, Alexander Ziaee wrote: > Hello, > > Can we keep the vinum [0] article, but move it to docs-archive? gvinum(8) was > removed in January, 2025, and vinum(4) was removed in March, 2013. > > [0] https://docs.freebsd.org/en/articles/vinum/ >

Re: Moving vinum to docs-archive

On the gvinum deprecation wiki page it notes: "Need to decide what to do with the vinum article - simply deleting it may be most appropriate " Personally, I see no need to keep the article now that the code and the man page are gone. Best Regards, Jim B. On Sun, 13 Apr 2025 01:53:11 + (UTC)

Re: Translation questions

Hi Mohamad, Yes, the document source in AsciiDoc format are available. Read through the FDP Primer for details. It's all in there. https://docs.freebsd.org/en/books/fdp-primer/ Again, be sure to read through the translation chapters (8, 9, 10) to get a sense of how it all works. Best Regards,

Re: Translation questions

Hello Jim, Thank you so much for your response. This is exactly what I am looking for. I have much experience using the LaTeX for my old Mathematics article, but I found that AsciiDoc should be easier to use, especially for documentation. Are the FreeBSD documents' source (in AsciiDoc format) ava

Re: Translation questions

On Sat, 12 Apr 2025 13:47:08 -0700 Sayed Mohammad Badiezadegan wrote: > Hello, > > This is Mohamad, > > I'm interested in translating the FreeBSD documents to my native > language (Persian). > > I saw the list of your available translations, but the Iran BSD User > Group is not active now, and

Re: Sound manuals

Alexander Ziaee wrote: > On 2025-02-19 09:32 -05:00 EST, "Christos Margiolis" > wrote: > > Alexander Ziaee wrote: > >> I want to do the sound manuals like we do wifi manuals. My snd_uaudio > >> device shows up as uaudio0, like if_re shows up as re0, an

Re: Sound manuals

On 2025-02-19 09:32 -05:00 EST, "Christos Margiolis" wrote: > Alexander Ziaee wrote: >> I want to do the sound manuals like we do wifi manuals. My snd_uaudio >> device shows up as uaudio0, like if_re shows up as re0, and the manual >> is called re, which is shad

Re: Sound manuals

Hello, Alexander Ziaee wrote: > Hello, > > I want to do the sound manuals like we do wifi manuals. My snd_uaudio > device shows up as uaudio0, like if_re shows up as re0, and the manual > is called re, which is shadow mlinked to if_re. To do this nicely, I'd > like to pi

Re: Sound manuals

On Wed, Feb 19, 2025 at 1:09 AM Alexander Ziaee wrote: > Hello, > I want to do the sound manuals like we do wifi manuals. My snd_uaudio device > shows up as uaudio0, like if_re shows up as re0, and the manual is called re, > which is shadow mlinked to if_re. To do this nicely, I&#x

Re: Sound manuals

On Wed, 19 Feb 2025 00:08:59 + (UTC) "Alexander Ziaee" wrote: > Hello, > > I want to do the sound manuals like we do wifi manuals. My snd_uaudio > device shows up as uaudio0, like if_re shows up as re0, and the > manual is called re, which is shadow mlinked to i

Re: HEADS UP: doc/ slush begins for 13.5-RELEASE

Le 31.01.2025 10:27, Marc Fonvieille a écrit : > Hello, > > As announced, the doc tree is now in a slush. Please postpone all > non-essential changes until after the doc tree is tagged (currently > scheduled for 14 February, 2025). > > Please note that the slush does not apply to website/ docume

[UPDATED] Re: [FDP] Generating an Index for PDF Documents

[snip] > > NOTES: > You can tag any kind of text - regular text, text inside [NOTEs], > [TIPs], etc. or text inside listings such as [.programlisting], > [.source], [subs=+quotes] etc. > Nope. It turns out that tagging terms inside listing, messes with the HTML output. See attached example. L

Re: [FDP] Generating an Index for PDF Documents

On Sun, 12 Jan 2025 at 06:49, jpb wrote: > > > Here's a quick summary on how to generate an index for FreeBSD FDP > books, articles, and multi-part documents. Happily, the indexing > tooling is already built into Asciidoctor. > > 1. Decide where you want the index. In my case I added another > "

Re: committers-guide sub-menu in contents?

On Wed, 26 Jun 2024 at 23:38, Bjoern A. Zeeb wrote: > > Hi, > > scrolling through the chapters is hard on the single page thing and when > one clicks on a section, say "5. Git Primer", is there any possibility > to show section contents (subsections) somwhere to make it easier to > navigate inside

Re: Danish translation

On Tue, 26 Nov 2024 13:53:05 +0100 (CET) Thomas Bleses wrote: > Hi there > > Id like to help translating the documentation into danish. Are there > anyone else out there going at it, that hasn't been published to the > translations page? Best regards Thomas Bleses Hello Thomas, Thanks for you

Re: HEADS UP: doc/ slush begins for 14.2-RELEASE

Le 25.10.2024 18:55, Marc Fonvieille a écrit : > HEADS UP: doc/ slush begins for 10.2-RELEASE > > Hello, > > As announced, the doc tree is now in a slush. Please postpone all > non-essential changes until after the doc tree is tagged (currently > scheduled for 8 Novembre, 2024). > > Please note

[Bug 271449] FreeBSD Handbook: re-write 'Creating a FreeBSD Guest' and 'Using ZFS with bhyve Guests'

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271449 --- Comment #3 from Chris Moerz --- (In reply to Pat Maddox from comment #2) Well, that settles that then, I guess. We should probably rewrite the advice to use file backed storage on datasets instead of zvols. I'll put that on my todo li

[Bug 271449] FreeBSD Handbook: re-write 'Creating a FreeBSD Guest' and 'Using ZFS with bhyve Guests'

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271449 --- Comment #2 from Pat Maddox --- There’s an article from Klara comparing the performance: https://klarasystems.com/articles/virtualization-showdown-freebsd-bhyve-linux-kvm/ Specifically the section “Finding the most performant storage co

[Bug 271449] FreeBSD Handbook: re-write 'Creating a FreeBSD Guest' and 'Using ZFS with bhyve Guests'

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271449 Chris Moerz changed: What|Removed |Added CC||free...@ny-central.org --- Comment #

Re: Missing Africa support vendor

Hi there Jim Not right now I'm busy negotiating with the co-owner of my consultancy business with regards to new branding and company renaming. Would it be possible to just pop in a mailto: link for now? Or would it be better to have a webpage to point to? Consultant.com is a domain hosted by th

Re: Missing Africa support vendor

Ross, Do you have a specific website for your business? "consultant.com" appears to be a generic landing page or domain squatter. Please advise, Jim B. On Mon, 4 Nov 2024 09:21:16 +0200 Ross Cameron wrote: > Hi Jim, > > Thanks for your prompt response. > > The most suitable page, as far

Re: Missing Africa support vendor

Hi Jim, Thanks for your prompt response. The most suitable page, as far as I can see, would be the consulting vendors page over on: https://www.freebsd.org/commercial/consult_bycat/ I'm located in: Johannesburg, South Africa I provide a broad range of UNIX Systems consulting services. Everythi

Re: Missing Africa support vendor

On Sun, 3 Nov 2024 21:06:28 +0200 Ross Cameron wrote: > Hi there > > Graham Perrin suggested I email this list to bring Bug 282242 to > your attention. > > The website doesn't list any support vendors for Africa and I happen > to be one. > > ~~ > Regards,... > Ross Cameron > eMail: rwd.came..

Re: [Bug 281675] Links to the bug database broken on main (and other pages).

On Mon, 23 Sep 2024 20:27:17 + bugzilla-nore...@freebsd.org wrote: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281675 > > Bug ID: 281675 >Summary: Links to the bug database broken on main (and > other pages). >Product: Documentation >Ver

Re: I'd like to help translate the documentation into Japanese.

On Sat, Aug 31, 2024, at 15:27, Mutsuhide G. wrote: > Hello. > I'm a beginner user in Japan. > I'd like to help translate the documentation into Japanese. > Is there anything I can do? Hello, The existing Japanese translations [1] were not created using our Weblate instance. [2] However, usi

Re: HEADS UP: doc/ slush begins for 13.4-RELEASE

Le 26.07.2024 08:41, Marc Fonvieille a écrit : > Hello, > > As announced, the doc tree is now in a slush. Please postpone all > non-essential changes until after the doc tree is tagged (currently > scheduled for 9 August, 2024). > > Please note that the slush does not apply to website/ documents

Re: Localized versions of freebsd.org outdated and linked to by google

On Thu, May 23, 2024, at 17:50, Michael Gmelin wrote: >> On 23. May 2024, at 22:08, Lorenzo Salvadore >> wrote: >> >> On Thursday, May 23rd, 2024 at 18:41, Michael Gmelin >> wrote: >> >>> I think this situation needs to be resolved, either by updating these >>> pages by whatever means or

Re: Localized versions of freebsd.org outdated and linked to by google

> On 23. May 2024, at 22:08, Lorenzo Salvadore > wrote: > > On Thursday, May 23rd, 2024 at 18:41, Michael Gmelin > wrote: > >> I think this situation needs to be resolved, either by updating these >> pages by whatever means or by giving up localization - at least for the >> languages we c

Re: Localized versions of freebsd.org outdated and linked to by google

On Thursday, May 23rd, 2024 at 18:41, Michael Gmelin wrote: > I think this situation needs to be resolved, either by updating these > pages by whatever means or by giving up localization - at least for the > languages we cannot support. > > Best > Michael > > -- > Michael Gmelin Hi, Some attemp

Re: Localized versions of freebsd.org outdated and linked to by google

Michael Gmelin wrote: > What I noticed while getting to localized versions is that some of > these pages are really outdated and/or broken, even those central to > the project. Tangentally related, in the past I got caught out by googling the FreeBSD manpage for something, and the google hit wen

Re: HEADS UP: doc/ slush begins for 14.1-RELEASE

Le 26.04.2024 10:55, Marc Fonvieille a écrit : > Hello, > > As announced, the doc tree is now in a slush. Please postpone all > non-essential changes until after the doc tree is tagged (currently > scheduled for 10 May, 2024). > > Please note that the slush does not apply to website/ documents.

Re: Jail handbook path fix

El mié., 13 mar. 2024 13:24, Matthew Phillips escribió: > Hello, I'd love a committer to take a look at this patch: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276668 > > Small fix, the handbook uses `containers/` as part of the path > throughout the guide, but omits it from the section

Re: Question relationship of builting(1) and functions refrenced through .Xr

documentation portion but not manual pages. Kind Regards, Chris From: owner-freebsd-...@freebsd.org on behalf of Alexander Ziaee Date: Friday, March 8, 2024 at 3:29 PM To: freebsd-doc Subject: Re: Question relationship of builting(1) and functions refrenced through .Xr Hi, (Chris Davidson asked

Re: Question relationship of builting(1) and functions refrenced through .Xr

Hi, (Chris Davidson asked) > How does the manual page relationship work > between the builtin(1) manual pages and the > individual .Xr links to other pages Builtin(1) describes shell builtin commands, but the links in this see also section refer to: - pages for valid, discrete programs in the ba

Re: HEADS UP: doc/ slush begins for 13.3-RELEASE

Le 05.02.2024 08:27, Marc Fonvieille a écrit : > Hello, > > As announced, the doc tree is now in a slush. Please postpone all > non-essential changes until after the doc tree is tagged (currently > scheduled for 16 February, 2024). > > Please note that the slush does not apply to website/ docume

[Bug 276737] Missing re-entrant function/s & differences from multiple man pages

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276737 Bug ID: 276737 Summary: Missing re-entrant function/s & differences from multiple man pages Product: Documentation Version: Latest Hardware: Any

RE: Improvements for the future FreeBSD Handbook

But is the current FreeBSD Handbook even the fourth edition?! It doesn't actually state what edition it is. Perhaps its the Five Edition and both the Fourth Edition and Third Edition sections are incorrectly claiming to be the current version??   And this another example of why the FreeBSD Handbo

Re: Clearly explain images

please follow the culture of FreeBSD-doc and fill out bug reports for items you see in need of repair.  This list is normally populated with sparse human chatter and large amounts of bugzilla messages.  Mostly everyone communicates via the bugtracker, hope that helps! On 1/1/24 18:10, Kolusion

RE: Clearly explain images

After reading over my last e-mail, I think the button [Download now] can just be [Download].

Re: Inconsistent use of both flow of wording and terminology

After giving it more thought, I think using the terminology with the flow 'run the command:' is good. 'Running a command', 'running a program' and 'running an app' are not always in the same context. 'run the command' makes the context clearer in this regard.

Re: Systematic broken instructions

Another idea that I think is better is to bring the sudo package into the base system. This would then mean the FreeBSD Handbook wouldn't need to systematically indicate or state the command requires superuser privileges. So instead of the FreeBSD Handbook incorrectly stating to execute this...

RE: Suggestions to improve the FreeBSD handbook

I have given it more thought. If each desktop environment section states a windows system needs to be installed in order to use it, then the mention of a windows system needing to be installed in order to use a desktop environment under section 8.1 Synopsis can be removed because the user will r

Re: Handbook - Chapter 26 - potentially misleading note

On Wed, 18 Oct 2023 at 16:18, Tomasz Kramkowski wrote: > > Hi, > > I was reviewing Chapter 26 of the handbook today in preparation for an > upgrade and I was reading section 26.2.3 "Performing Minor and Major > Version Upgrades" and noticed what may be a mistake. > > After running `freebsd-update

Re:

On Tue, 10 Oct 2023 at 08:05, IJ wrote: > > Hi, > Was browsing through the FreeBSD handbook,under Chapter 7(Network) > 7.4.4.1 Authenticate with WPA2/WPA/Personal,item no 3 should it be password > not passwork right? > Thank you. > > IJ Hi, I'll take a look and if there's a bug I'll fix it. Th

Re: Updating https://www.freebsd.org/administration

Hi! > > > > I have more changes pending for phabric-admin, git-admin and > > > > my gpg key, FYI... Ok, phabric-admin is already fine, but the email list is not sorted in /etc/aliases. git-admin is not the correct list, it's gitadm@, and that is a forward to clusteradm. So no changes required ei

Re: Update my gpg key

Hi! > > Attached. > you can make the commit, the diff is ok :) Done. -- p...@freebsd.org +49 171 3101372 Now what ?

Re: Update my gpg key

On Tue, 3 Oct 2023 at 12:08, Kurt Jaeger wrote: > > Hi! > > Attached. > > -- > p...@freebsd.org +49 171 3101372 Now what ? Hi, you can make the commit, the diff is ok :)

Re: Updating https://www.freebsd.org/administration

On Tue, 3 Oct 2023 at 12:03, Kurt Jaeger wrote: > > Hi! > > > > > > I have this update for the webpage, see attached diff. > > > > > The list of postmasters is taken from the email alias postmaster@. > > > > > > > > > > Would you prefer it as PR on bugs.freebsd.org or as review > > > > > on review

Re: Updating https://www.freebsd.org/administration

Hi! > > > > I have this update for the webpage, see attached diff. > > > > The list of postmasters is taken from the email alias postmaster@. > > > > > > > > Would you prefer it as PR on bugs.freebsd.org or as review > > > > on reviews.freebsd.org or can I just commit this update ? > > > > > Thank

Re: Updating https://www.freebsd.org/administration

On Tue, 3 Oct 2023 at 11:58, Kurt Jaeger wrote: > > Hi! > > > > I have this update for the webpage, see attached diff. > > > The list of postmasters is taken from the email alias postmaster@. > > > > > > Would you prefer it as PR on bugs.freebsd.org or as review > > > on reviews.freebsd.org or can

Re: Updating https://www.freebsd.org/administration

Hi! > > I have this update for the webpage, see attached diff. > > The list of postmasters is taken from the email alias postmaster@. > > > > Would you prefer it as PR on bugs.freebsd.org or as review > > on reviews.freebsd.org or can I just commit this update ? > Thanks for the upgrade, I'm gonn

Re: Updating https://www.freebsd.org/administration

On Tue, 3 Oct 2023 at 11:44, Kurt Jaeger wrote: > > Hi! > > I have this update for the webpage, see attached diff. > The list of postmasters is taken from the email alias postmaster@. > > Would you prefer it as PR on bugs.freebsd.org or as review > on reviews.freebsd.org or can I just commit this

Re: https://www.freebsd.org/commercial/isp/

On Sun, 1 Oct 2023 at 10:18, Mark Linimon wrote: > > fwiw this is another area on the website (like some of the antique stuff in > the FAQ) that is only in the doc build because 20 years ago that was the only > way we could do it. > > IMVHO this all ought to be in the wiki these days. > > mcl M

Re: https://www.freebsd.org/commercial/isp/

fwiw this is another area on the website (like some of the antique stuff in the FAQ) that is only in the doc build because 20 years ago that was the only way we could do it. IMVHO this all ought to be in the wiki these days. mcl

Re: https://www.freebsd.org/commercial/isp/

On Sun, 1 Oct 2023 at 02:04, Dan Langille wrote: > Hello, > > I was going through https://www.freebsd.org/commercial/isp/ and found > some issues I thought warranted this email. > > Hub Hosting Services links to https://hub.org, which just says: not here > > -- > Dan Langille > d...@langille.

Re: HEADS UP: doc/ slush begins for 14.0-RELEASE

Le 10.09.2023 10:33, Marc Fonvieille a écrit : > Hello, > > As announced, the doc tree is now in a slush. Please postpone all > non-essential changes until after the doc tree is tagged (currently > scheduled for 24 September, 2023). > > Please note that the slush does not apply to website/ docum

Re: May I ask whether FreeBSD's pkg binary packages are compiled on machines with the release version or the stable version?

On 14/08/2023 18:16, ykla wrote: Hi, May I ask whether FreeBSD's pkg binary packages are compiled on machines with the release version or the stable version? I forgot where this explanation appeared. I've been searching for a long time and haven't found it. Does anyone know where this exp

Re: May I ask whether FreeBSD's pkg binary packages are compiled on machines with the release version or the stable version?

According to what I’ve read they are compiled with the base RELEASE version, not STABLE or CURRENT. Sent from Proton Mail for iOS On Mon, Aug 14, 2023 at 13:54, Sergio Carlavilla <[carlavi...@freebsd.org](mailto:On Mon, Aug 14, 2023 at 13:54, Sergio Carlavilla < wrote: > On Mon, 14 Aug 2023 a

Re: May I ask whether FreeBSD's pkg binary packages are compiled on machines with the release version or the stable version?

On Tue, Aug 15, 2023 at 01:16:26AM +0800, ykla wrote: > Hi, > > May I ask whether FreeBSD's pkg binary packages are compiled on machines > with the release version or the stable version? > > I forgot where this explanation appeared. I've been searching for a long > time and haven't found it. Does

Re: May I ask whether FreeBSD's pkg binary packages are compiled on machines with the release version or the stable version?

On Mon, 14 Aug 2023 at 19:25, Minsoo Choo wrote: > Hi, > I don't know what version of FreeBSD they use to build packages, but > according to FreeBSD website(https://www.freebsd.org/ports/), both port > collection and package collections support -STABLE and port collection also > supports -CURRENT

Re: May I ask whether FreeBSD's pkg binary packages are compiled on machines with the release version or the stable version?

Hi, I don't know what version of FreeBSD they use to build packages, but according to FreeBSD website(https://www.freebsd.org/ports/), both port collection and package collections support -STABLE and port collection also supports -CURRENT. I hope this can answer your question. Regards, Minsoo --

Re: Has the update procedure changed?

On 08/08/2023 03:50, Robert Huff wrote: … 1) It would be really nice is someone would take a look and make sure these 100% non-contradictory. … Looks by people should, ideally, include: 209744 – Move installation instruction

Re: Phone number spamming from https://www.freebsd.org/releases/1.1.5/SUPPORT.TXT

On 02/05/2022 12:41, Julian H. Stacey wrote: … - my phone number deleted please, … With reference to the 2022 request: . OpenPGP_signature Description: OpenPGP digital signature

[Bug 263958] FreeBSD Handbook: Updating and Upgrading FreeBSD: add info for re-using /usr/obj for builds

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263958 --- Comment #4 from Warner Losh --- Ah yes. 13.x does have a WITH_CLEAN default. WITHOUT_CLEAN is the default on 14 and newer -- You are receiving this mail because: You are the assignee for the bug.

[Bug 263958] FreeBSD Handbook: Updating and Upgrading FreeBSD: add info for re-using /usr/obj for builds

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263958 Warner Losh changed: What|Removed |Added CC||i...@freebsd.org --- Comment #2 from

Re: make lint

> LINT files are no longer created. Someone needs to prod the doc. team. Ooops, should have looked more closely at the email address I was replying to!

Re: make lint

Graham Perrin wrote: > > suggests: > > make lint > > I tried it whilst at /usr/src and at /usr/doc > > In both cases, > > > make: don't know how to make lint. Stop > > … > > What am I missing? LINT files are no longer c

Re: make lint

On 10/06/2023 17:50, Moin Rahman wrote: … What am I missing? I think the documentation is outdated and there is not specific linter target at the moment. The document also refers to XML Docs which we have migrated to asciidoc. Kind regards, Moin Thanks to Moin, and to Jose Luis Duran at

Re: make lint

> On Jun 10, 2023, at 6:40 PM, Graham Perrin wrote: > > > suggests: > > make lint > > I tried it whilst at /usr/src and at /usr/doc > > In both cases, > >> make: don't know how to make lint. Stop >> … > > What am

Re: Where is man.wrapper as used by website/content/en/cgi/man.cgi

On Sat, 27 May 2023 at 21:51, Edward Sanford Sutton, III wrote: > >In trying to troubleshoot tabs replacing spaces on manpages found on > FreeBSD's website. As it isn't an issue in the original manpage, it > seems to be involved in how the webpage versions are created. They > aren't found or c

[Bug 271449] FreeBSD Handbook: re-write 'Creating a FreeBSD Guest' and 'Using ZFS with bhyve Guests'

Summary|re-write 23.6.2 and 23.6.6 |FreeBSD Handbook: re-write ||'Creating a FreeBSD Guest' ||and 'Using ZFS with bhyve ||Guests' S

[Bug 271449] re-write 23.6.2 and 23.6.6

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271449 Bug ID: 271449 Summary: re-write 23.6.2 and 23.6.6 Product: Documentation Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Many

Re: Translating docs to Polish and The FreeBSD Polish Documentation Project problem

Thanks, I'll check it out. sob., 15 kwi 2023 o 04:13 Mark Linimon napisał(a): > > > On 04/13/2023 12:03 PM CDT Qwertiox Game > wrote: > > P.S. What is the condition for receiving @freebsd.org ( > http://freebsd.org) email > > It is better explained in: > > > https://wiki.freebsd.org/BecomingACo

  1   2   3   4   5   6   7   8   9   10   >