home.social

Search

280 results for “BastilleBSD”

  1. SYNOPSIS
    bastille clone [-alx] TARGET NEW_NAME IP

    The bastille clone sub-command will create an exact duplicate of the targeted jail, giving it the specified NEW_NAME and IP address.

    EXAMPLES
    Clone myjail to newjail:
    # bastille clone myjail newjail 10.23.3.4/24

    Clone myjail to newjail with DHCP (VNET only):
    # bastille clone myjail newjail DHCP

    Clone myjail to newjail while running, with debug mode:
    # bastille clone -xl myjail newjail 10.23.3.4/24

  2. I'm pleased to report that I've just submitted the final capstone paper for my master's degree in cybersecurity!

  3. The bastille convert sub-command will convert a thin jail to a thick jail if only the TARGET argument is given.

    If a TARGET and RELEASE is specified, it will convert the jail into a custom release. The jail will remain intact, and you will have a duplicate of it to use a a release base for any new jails.

    EXAMPLES
    Convert myjail from thin to thick:
    # bastille convert myjail

    Create myrelease from myjail:
    # bastille convert myjail myrelease

  4. Ugh. I rebooted my FreeBSD server server (runs some #bastilleBSD jails and a bhyve linux vm) and now the bhyve vm isn’t on the network. Somehow I had something working but not matching what was in rc.conf and no clue what it was. :(

  5. NAME
    bastille jcp – Copy file(s)/directorie(s) from jail to jail(s).

    SYNOPSIS
    bastille jcp [-qx] SOURCE_JAIL JAIL_PATH DESTINATION_JAIL JAIL_PATH

    DESCRIPTION
    The bastille jcp sub-command will copy files and directories from a single jail to any targeted jail(s).

    -q, --quiet : Suppress output.

    -x, --debug : Enable debug mode.

    EXAMPLES
    Copy /etc/resolv.conf from myjail to yourjail:
    # bastille jcp myjail /etc/resolv.conf yourjail /etc

  6. NAME
    bastille rcp – Copy file(s)/directorie(s) from jail to host.

    SYNOPSIS
    bastille rcp [-qx] TARGET JAIL_PATH HOST_PATH

    DESCRIPTION
    The bastille rcp sub-command will copy JAIL_PATH to HOST_PATH from inside TARGET.

    -q, --quiet : Suppress output.

    -x, --debug : Enable debug mode.

    EXAMPLES
    Copy /etc/resolv.conf.custom to host:
    # bastille rcp myjail /etc/resolv.custom /jailstuff/etc

    Copy /etc to host quietly:
    # bastille rcp -q myjail /etc /jailstuff/etc

  7. From `man bastille-restart`:

    EXAMPLES
    Restart all jails, ignoring stopped jail:
    > bastille restart -i all

    Restart all jails, but only if boot=on:
    > bastille restart -b all

    Restart all jails with a 5 second delay between each one:
    > bastille restart -d 5 all

  8. Let's do something different today.

    Join me for a live-stream of a beautiful desert sunset.

    I'm currently exploring wild places in the American Southwest (Arizona), and sharing some of it with you.

    Current location: Kofa National Wildlife Refuge

    youtube.com/@chrisacrossameric

    Take a few minutes for yourself, slow down, and consider joining. See you there. 😎

  9. NAME
    bastille service – Manage services within jail(s).

    SYNOPSIS
    bastille service [-ax] TARGET SERVICE ARGS

    DESCRIPTION
    The bastille service sub-command can manage services in jails.

    -a, --auto
    Auto mode. Start/stop jail(s) if required.

    -x, --debug
    Enable debug mode.

    EXAMPLES
    Start nginx in myjail:
    > bastille service myjail nginx start

    Stop caddy in myjail:
    > bastille service myjail caddy stop

  10. @BastilleBSD My finds so far, all names of prisons:
    - `Bastille`, obviously
    - `folsom`, which seems to refer to Folsom State Prison
    - `azkaban`, duh

    I'm not sure what the user `ishmael` refers to though, prison-wise

    #nerdsniping people into reading documentation, bravo :)

  11. @BastilleBSD My finds so far, all names of prisons:
    - `Bastille`, obviously
    - `folsom`, which seems to refer to Folsom State Prison
    - `azkaban`, duh

    I'm not sure what the user `ishmael` refers to though, prison-wise

    #nerdsniping people into reading documentation, bravo :)

  12. @BastilleBSD My finds so far, all names of prisons:
    - `Bastille`, obviously
    - `folsom`, which seems to refer to Folsom State Prison
    - `azkaban`, duh

    I'm not sure what the user `ishmael` refers to though, prison-wise

    #nerdsniping people into reading documentation, bravo :)

  13. @BastilleBSD My finds so far, all names of prisons:
    - `Bastille`, obviously
    - `folsom`, which seems to refer to Folsom State Prison
    - `azkaban`, duh

    I'm not sure what the user `ishmael` refers to though, prison-wise

    people into reading documentation, bravo :)

  14. @BastilleBSD My finds so far, all names of prisons:
    - `Bastille`, obviously
    - `folsom`, which seems to refer to Folsom State Prison
    - `azkaban`, duh

    I'm not sure what the user `ishmael` refers to though, prison-wise

    #nerdsniping people into reading documentation, bravo :)

  15. Did you know that there are historical and literary "easter eggs" in the Bastille documentation?

    I can't provide any clues without giving them away, but after eight years I'm starting to think they're too clever.

  16. Another sneak preview of the in-progress BastilleBSD web interface, powered by the new BastilleBSD API.

    The Resources page provides you with a quick overview of the available hardware resources and allows you to manage CPU, MEM and DISK based limits.

    What do you think about the Resources page?

    Note: these previews are still subject to change before release.

  17. 2026 continues to be a good year for BastilleBSD!

    We've onboarded our third training cohort this month, API development continues to mature and the UI is nearly ready for wider testing.

    Let us know here if you'd like to help beta test the API and web interface on your Bastille hosts.

    #2026

  18. Want to contribute to Rocinante?

    It's an open-source project, and new contributors are always welcome. Check out the GitHub repository to get started.

    github.com/BastilleBSD/rocinan

  19. Want to contribute to Rocinante?

    It's an open-source project, and new contributors are always welcome. Check out the GitHub repository to get started.

    github.com/BastilleBSD/rocinan

    #FreeBSD #Rocinante #OpenSource #Contribute #Automation

  20. Want to contribute to Rocinante?

    It's an open-source project, and new contributors are always welcome. Check out the GitHub repository to get started.

    github.com/BastilleBSD/rocinan

    #FreeBSD #Rocinante #OpenSource #Contribute #Automation

  21. Want to contribute to Rocinante?

    It's an open-source project, and new contributors are always welcome. Check out the GitHub repository to get started.

    github.com/BastilleBSD/rocinan

    #FreeBSD #Rocinante #OpenSource #Contribute #Automation

  22. Want to contribute to Rocinante?

    It's an open-source project, and new contributors are always welcome. Check out the GitHub repository to get started.

    github.com/BastilleBSD/rocinan

    #FreeBSD #Rocinante #OpenSource #Contribute #Automation

  23. Our FreeBSD training is not just for beginners.

    Our courses also include advanced topics like network performance tuning, security hardening, and ZFS administration.

    Email [email protected] for details and scheduling.

  24. > man bastille-import


    If the RELEASE argument is specified, Bastille will import the jail using that release.

    **EXAMPLES**

    Import myjail_DATE.txz:
    > bastille import myjail_DATE.txz

    Import myjail_DATE.gz under 15.0-RELEASE:
    > bastille import myjail_DATE.txz 15.0-RELEASE

    Import myjail_DATE.gz under 15.0-RELEASE from non-default location:
    > bastille import /my/custom/folder/myjail_DATE.txz 15.0-RELEASE

  25. Ready to level up your FreeBSD knowledge? Our comprehensive training courses cover everything from the basics to advanced system administration.

    Email [email protected] for more details.

  26. We're aware of an issue with the Rocinante documentation being inaccessible due to a domain expiring. We're moving some things around and will get it fixed soon.

  27. We're aware of an issue with the Rocinante documentation being inaccessible due to a domain expiring. We're moving some things around and will get it fixed soon.

    #FreeBSD #BastilleBSD #Rocinante

  28. We're aware of an issue with the Rocinante documentation being inaccessible due to a domain expiring. We're moving some things around and will get it fixed soon.

    #FreeBSD #BastilleBSD #Rocinante

  29. We're aware of an issue with the Rocinante documentation being inaccessible due to a domain expiring. We're moving some things around and will get it fixed soon.

    #FreeBSD #BastilleBSD #Rocinante

  30. We're aware of an issue with the Rocinante documentation being inaccessible due to a domain expiring. We're moving some things around and will get it fixed soon.

    #FreeBSD #BastilleBSD #Rocinante