Re: Which GPT partion type for eli?
On Sun, Jul 09, 2023 at 10:48:32PM -0400, Yoshihiro Ota wrote: > I've been using freebsd-ufs and freebsd-zfs instead. > But they seem to have some side-effects and not best options. What side effects are you seeing? -- Mason Loring BlissTherewith his sturdie corage soon was quayd, ma...@blisses.org And all his sences were with suddein dread dismayd. signature.asc Description: PGP signature
Freeze during early boot
Hi, all. I'd like to see FreeBSD running on a new class of box I've got here. Not new hardware. These are Atom chips on Micro-ITX motherboards, and are interesting in that they are low-power and have dual gigabit NICs. They're UEFI-only. These boxes seem to not like the FreeBSD 12.1 .iso files as written to USB sticks, but I could boot the installer with an .img. That said, the resulting system as installed seems to freeze in precisely the same place as the .iso-files-written-to-USB froze. I took a photo of the freeze, and then realized that it was the same as when I was trying to boot from the USB stick the first time. I've got a photo of it in the bug I've just opened to complement this email, along with dmesg from NetBSD and Linux: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249226 What's different between the .iso and the .img files, and how might that translate to the installed system, if that's not a red herring? And how might I get these boxes to boot FreeBSD? The boxes don't have build-in storage so I'm installing and booting from USB drives, so making modifications from another system to test things ought to be fairly straightforward. Addendum: To try -current in case it was a known issue, I downloaded the mini-memstick.img, but it freezes in the same place. -- Mason Loring Blissma...@blisses.org They also surf, who only stand on waves. signature.asc Description: PGP signature
Re: Plans for git (was: Please check the current beta git conversions)
On Wed, Sep 02, 2020 at 01:38:09PM -0400, Theron wrote: > After the transition, will FreeBSD base contain the tool for the cloning the > FreeBSD repository (not one of the mirrors?) Just to throw it out there, https://gameoftrees.org/ would be interesting to explore for this. -- Mason Loring Blissma...@blisses.org They also surf, who only stand on waves. signature.asc Description: PGP signature
Re: snapshot iso, memstick.img missing?
On Sat, Nov 08, 2014 at 08:34:17AM +0900, Lundberg, Johannes wrote: > I can't seem to find > FreeBSD-11.0-CURRENT-amd64-20141025-r273635-memstick.img Seconding this, I don't see it here: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/amd64/ISO-IMAGES/11.0/ I was hoping to grab it to try booting my macbook11,1, which wasn't happy with the latest 10-series I tried on it. -- Love is a snowmobile racing across the tundra and then suddenly it flips over, pinning you underneath. At night, the ice weasels come. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On Thu, Oct 23, 2014 at 10:20:20AM +0200, Lars Engels wrote: > Please register with your realname and I can give you the needed rights. A snag... When I click 'Logic' at the top of the page it brings me to the login form, which has a link to https://wiki.freebsd.org/action/newaccount/FrontPage?action=newaccount However, this produces a red error icon and the message "Unknown action newaccount." I'll be happy to sign up once this is resolved, one way or the other. -- Mason Loring Bliss ma...@blisses.orghttp://blisses.org/ "I am a brother of jackals, and a companion of ostriches." (Job 30 : 29) ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On Tue, Oct 21, 2014 at 09:14:07AM +0100, David Chisnall wrote: > I agree that this would be useful, but it requires someone familiar with > both systems to write. Doing this stuff professionally, I could probably come up with equivalences for a number of Unices. What would be a reasonable path to getting write privs on the wiki? > > I bet roughly no one who installs Subversion wants the FreeBSD bug report > > headers baked in by default, > > It's worth noting that the FreeBSD headers don't affect operation. It mostly violates the principle of least surprise and is a cosmetic blemish. I'd suspect that a lot of people use Subversion for their own or their company development, and the default behaviour looks strange. It was certainly surprising to me in any event. A default of not having that turned on but an option to turn it on seems like the most reasonable thing, given that the option is so closely tied to FreeBSD development. > It might be a good idea to move this thread to the -docs mailing list, I will subscribe to that. -- Mason Loring Bliss (( If I have not seen as far as others, it is because ma...@blisses.org )) giants were standing on my shoulders. - Hal Abelson ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On Mon, Oct 20, 2014 at 08:04:14PM -0400, Allan Jude wrote: > > For instance, the page that talks about running buildworld and buildkernel > > have some instructions that are evidently vestigal for root-on-ZFS people. > > Which parts? Nothing about buildworld is really any different when using > ZFS except maybe the way you mount /usr/obj with noatime etc. https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html In this case, after "shutdown now" it suggests turning off a readonly flag that's not on, mounting everything despite nothing being unmounted, and setting the kernel time zone despite that never seeming to be an issue. > Can you be more specific? The documentation team likes to add 'quick start' > sections to the often more complex sections, so that users looking to just > get started can do so, and dig into the more advanced options once they > have it working. Sure. https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-poudriere.html So, coming at it from scratch, the section has a quick description and notes where to find a sample config file. Then it says "It may be convenient to put poudriere datasets in an isolated tree mounted at /poudriere. Defaults for the other configuration values are adequate." However, that's the first appearance of the word "dataset" so I don't know what it is or why I want a root-level mount for it. Section 5.6.1 has an example invocation: poudriere jail -c -j 10amd64 -v 10.0-RELEASE This might not catch everyone, but the formality of the jail name and the version made me think that the jail name has to be of a certain strict form to work. Maybe it doesn't? It's not entirely clear. Then there's another example invocation: poudriere ports -c -p local It's not altogether clear (to me at least) what this is doing as compared with the -c -i -v invocataion. Again, I suspect I can spend enough time reading docs to figure it out, but that completely negates the value of the Handbook as a primary source for information. After these two somewhat opaque examples, we're told "poudriere can build ports with multiple configurations, in multiple jails, and from different port trees" and "The basic configuration shown here puts a single jail-, port-, and set-specific make.conf in /usr/local/etc/poudriere.d." This one definitely got me, as it seems to suggest that things should live in /usr/local/etc/poudriere.d, but it doesn't specify exactly where. I see something now that I think I missed before, which is that the long string "10amd64-local-workstation-pkglist" references bits of text from the first two invocations, but the description of how the string is formulated is somewhat opaque, depending to some extent on the still-undefined "set" which I presume to mean the same thing as "dataset". But, where do I go to find the built packages? I'm guessing at the moment that I'd find them somewhere in /poudriere, but I'm not entirely clear on how different architectures and sets and such are kept distinct... (I spun up a large virtual machine to do a test build and try to observe where things went afterwards, and at that I was still unclear on where, for instance, config options were stored... Anyway, the build exhausted its eight gigs of RAM and the OOM killer made a mess of things, and I haven't had a chance to revisit the process.) It's entirely possible that I'm just old and slow and that this stuff isn't as unclear to me as it seems, but at the very least it's introducing new concepts without defining them and then using them in combinations that don't help the reader to understand how the combinations work. Part of this is inconsistency in formatting - are all the italic bits freeform text that doesn't matter, in the examples? It seems like some of them (FreeBSD version, for example) can't be. Again, a dig through more docs would clarify it, but if that's necessary then this Handbook section seems somewhat inadequate. > One goal is to actually have the version of the ports tree that the most > recent binary packages were built with available, so that users who use > that would have 0 complications from mixing. That would be useful. > Also, there have been some proposed features for pkg to make it aware of > which packages were installed from ports, and when 'pkg upgrade' runs, to > rebuild those packages from ports with the same options, instead of > installing the 'wrong' version from the binary packages, requiring the user > to 'pkg lock' or 'pkg annotate' to avoid that. Hm, I'm as yet unfamiliar with those two commands, but again, that sounds pretty useful. > Binary packages of libdvdcss are not built for legal reasons I figured as much - Debian doesn't ship it at all, for comparison, leaving the user in an even worse position. It was a cause of stress when I also had "don't mix pkgs and ports" emblazoned across my vision. Worth noting is that my world hasn't ended mixing the two, to the point where I'm doing so
Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On Mon, Oct 20, 2014 at 06:21:58PM -0400, Allan Jude wrote: > This thread is supposed to be about how to make it easier for people to > migrate to FreeBSD from Linux. Not a discussion about forums vs mailing > lists vs newsgroups. I'm going to transition from being an avid Debian user who hates web fora to an avid FreeBSD who hates web fora. Anyway, my experience here is useful as I've got to be representative of a number of people making the transition lately. It's been a relatively smooth transition so far, with only a couple bugs and quirks in the way of my doing everything I did with Debian. Two things would be principally useful for people coming from Linux. First, the handbook should be updated and corrected, as it's a good enough resource that I've come to depend upon it, but I've hit snags that seem to not reflect the current state of FreeBSD. For instance, the page that talks about running buildworld and buildkernel have some instructions that are evidently vestigal for root-on-ZFS people. Another example, the documentation of Poudriere is hard to follow, presenting a complex and idealized set-up rather than explaining to a new user what the moving parts are and how it all works. I strongly suspect in that case that people who need the Handbook won't easily follow that, and people who can follow it don't need the Handbook per se, or that level of instruction. Joe Armstrong talks about this process of picking an audience in his forward to the second edition of his Erlang book: https://joearms.github.io/2014/06/26/Background-to-programming-erlang.html The second thing that would be useful would be a series of cheat sheets for various things. This can either be equivalent commands or equivalent systems. Let new folks know that LUKS is GELI and that md-raid1 is gmirror and so forth. Show common package handling commands for various Linux flavours and map them to pkgng and ports. For instance, what's the equivalent of "yum provides"? Or what do I do in place of "apt-cache search" or "zypper up" or similar. Other things in the grab bag... It's generally said that ports and pkgs shouldn't mix, but there are at least a couple instances where it's unavoidable: I bet roughly no one who installs Subversion wants the FreeBSD bug report headers baked in by default, but there they are unless you rebuild from ports with a non-default configuration. If you want to watch DVDs on your FreeBSD workstation, it's necessary to install libdvdcss, but you can't get it from pkgng because it's not there. Again, you must build from ports. I have nothing against ports, but people are warned off of mixing packages and ports when clearly it's necessary sometimes. Oh, here's one. I *was* horrified by ports at first, until someone told me about "make config-recursive". It really makes me wonder why this isn't the default. I remember giving up on FreeBSD when 9.x was new because I had to build X from ports after the FreeBSD breach, and it seemed like the process was going to take a couple days of stuttering stops and starts as random packages I didn't want in some cases popped up between compiles. I learned some mechanism for saying "just take the defaults" but what I know now is that what I really wanted was "make config-recursive". Why, out of curiosity, is it not the default? That would seem better than documenting it harder. Ah, and one more for the grab bag. I strongly suspect that many folks coming from Linux are going to bristle at the notion of using Sendmail. I used to run it so I wasn't terribly bothered by it, but maybe pre-populating rc.conf with obvious bits that people can see and turn off would be nice. OpenBSD has a nice model of populating rc.conf and sysctl.conf fully, and it ends up being a pleasant tool. Those awash in wonder, coming from Linux, can say, "Look, it's all right here!" -- Mason Loring Bliss ma...@blisses.orgEwige Blumenkraft! (if awake 'sleep (aref #(sleep dream) (random 2))) -- Hamlet, Act III, Scene I ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On Sat, Oct 18, 2014 at 02:58:57PM +0900, Tomoaki AOKI wrote: > I think the advantages of the forum are... > > *Well moderated by moderators and anministrators. > *Registering email address is needed, but not disclosed by default. The disadvantages of web fora include: * I can't read things in my very efficient email client. Related: * I have to compose my replies in a web browser edit window. * I need to visit periodically and hope that the site makes it possible for me to attend to unread messages without struggling. I think wikis are useful. I think web fora exist because folks haven't had sufficient exposure to email to make the advantages clear. Not discussed here are newsgroups, which are perhaps ideal for the sorts of topics commonly found on mailing lists, except perhaps that they're not at all centralized. -- Mason Loring Bliss (( "In the drowsy dark cave of the mind dreams ma...@blisses.org )) build their nest with fragments dropped http://blisses.org/ (( from day's caravan." - Rabindranath Tagore ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
