search for: trueos

FreeBSD Community, I'm pleased to announce a CFT for builds of FreeBSD 12-stable and 13-current using "TrueOS-inspired" packaged base. These are stock FreeBSD images which will allow users to perform all updating via the 'pkg' command directly. Rather than trying to answer all questions in this announcement, we've created a FAQ page with more details. Please refer to this page, and let us...

On Tue, April 11, 2017 4:41 pm, Warren Young wrote: > On Apr 11, 2017, at 11:28 AM, Scott Robbins <scottro11 at gmail.com> wrote: >> >> (though they're talking of trying OpenRC) > > Not just talking. TrueOS, ne?? PC-BSD, now runs on OpenRC. > > So let me tell you about how my recent TrueOS server upgrade broke > virtually all of my services on the TrueOS server, roached the X > configuration, and now has the system in an un-upgradeable state, to the > point that it???s looking like I???...

On Tue, Apr 11, 2017 at 12:11:19PM -0400, Jonathan Billings wrote: > I feel like this conversation has reached the "lets just keep > repeating FUD about systemd" stage and probably won't progress in a > useful direction. > > Maybe we should just jump right to the end that we always have each > time this comes up. systemd is the death of linux and you're

On Apr 11, 2017, at 11:28 AM, Scott Robbins <scottro11 at gmail.com> wrote: > > (though they're talking of trying OpenRC) Not just talking. TrueOS, ne? PC-BSD, now runs on OpenRC. So let me tell you about how my recent TrueOS server upgrade broke virtually all of my services on the TrueOS server, roached the X configuration, and now has the system in an un-upgradeable state, to the point that it?s looking like I?ll have to reinstall if I eve...

...ing the surface. The real hard bits come from the way systemd hooks into the whole FreeDesktop infrastructure and vice versa. (e.g. dbus is now inextricably part of systemd, and many FreeDesktop interactions happen via dbus.) This is why the BSDs are either dropping GNOME and KDE (e.g. Lumina in TrueOS) or have badly lagging ports compared to the upstream version. I suspect it?s probably easier to start with C6, then backport as much as is possible without dragging in any systemd stuff, the same way the BSDs are doing. Good luck to y?all. Sincerely. I plan to keep on using C7, warts and all.

...> writes: >>> On Mon, Apr 29, 2019 at 10:09 AM Rodney W. Grimes < >>> freebsd-rwg at gndrsh.dnsmgr.net> wrote: >>> >>>>> >>>>> Correct, this is ZFS only. And it's something we're using specific to >>>> FreeNAS / TrueOS, which is why I didn't originally mention it as apart of >>>> our CFT. >>>> >>>> Then please it is "CFT: FreeNAS/TrueOS pkg base, ZFS only", >>>> calling this FreeBSD pkg base when it is not was wrong, >>>> and miss leading....

...e from the way systemd hooks into the whole >> FreeDesktop infrastructure and vice versa. (e.g. dbus is now >> inextricably part of systemd, and many FreeDesktop interactions happen >> via dbus.) This is why the BSDs are either dropping GNOME and KDE >> (e.g. Lumina in TrueOS) or have badly lagging ports compared to the >> upstream version. >> >> I suspect it?s probably easier to start with C6, then backport as much >> as is possible without dragging in any systemd stuff, the same way the >> BSDs are doing. >> >> Good luck to...

According to "Arthur Schopenhauer": "All truth passes through three stages. First, it is ridiculed. Second, it is violently opposed. Third, it is accepted as being self-evident." I must admit that I skipped through the first and second stages - I never found creating init scripts a joy and instead opted to write my own scripts that I launched via inittab. As

On 17/10/18 1:25 am, Valeri Galtsev wrote: > That said, if one is strongly willing to stay away from systemd, and > not to such extent into Linux as to needing an advise on that, I would > recommend to take a look at non-Linux system, specifically BSD > descendants (FreeBSD, NetBSD, etc). Their kernel is not as heavy > (big,resource demanding) as Linux kernel, and you can do

...ation for my local LUG about it: https://sanitarium.net/golug/rsync+btrfs_backups_2011.html Unfortunately there was nothing but grief. The btrfs just wasn't stable enough and the btrfs-cleaner kernel thread drove performance into the ground. We eventually had to abandon it in favor of ZFS on TrueOS. As far as "fast box" goes we decided on 8GB of RAM for most of the backup servers and essentially whatever CPU can handle that much RAM. Most of them are older AMD Athlon 64 X2 desktops. We do have one with a quad core CPU and 16GB of RAM. That is the only one running ZFS de-duplicat...

...urface. > > The real hard bits come from the way systemd hooks into the whole FreeDesktop infrastructure and vice versa. (e.g. dbus is now inextricably part of systemd, and many FreeDesktop interactions happen via dbus.) This is why the BSDs are either dropping GNOME and KDE (e.g. Lumina in TrueOS) or have badly lagging ports compared to the upstream version. > > I suspect it?s probably easier to start with C6, then backport as much as is possible without dragging in any systemd stuff, the same way the BSDs are doing. > > Good luck to y?all. Sincerely. I plan to keep on using C...

...ystemd hooks into the whole >>> FreeDesktop infrastructure and vice versa. (e.g. dbus is now >>> inextricably part of systemd, and many FreeDesktop interactions >>> happen via dbus.) This is why the BSDs are either dropping GNOME >>> and KDE (e.g. Lumina in TrueOS) or have badly lagging ports compared >>> to the upstream version. >>> >>> I suspect it?s probably easier to start with C6, then backport as >>> much as is possible without dragging in any systemd stuff, the same >>> way the BSDs are doing. >>&g...

...is in practice Try doing without launchd on macOS. If you think that?s irrelevant, count the number of MacBooks at the next FreeBSD conference you attend. For an init system to gain sufficient momentum, it must be the default, with no easy way to avoid it. Without that, you get things like: 1. TrueOS, where major non-core services still have no OpenRC script despite OpenRC being the default for about a year. There were no Samba or NUT OpenRC scripts the last time I tried TrueOS, for example. Even if that?s changed, it?s still a reflection of the fundamental barrier to adoption that I?m talkin...

On Wed, 2017-06-07 at 11:23 -0500, Johnny Hughes wrote: > If you want to create a CentOS-7 variant that does not use systemd, > then start a Special Interest Group and create modified packages > to use something else instead ......., much like the this group did > with Debian: > > https://devuan.org/ > > In the case of CentOS-7 .. you don't need to create a whole new

Folks, Kevin Korb wrote: > Have you considered more advanced methods such as subvolume snapshots > provided by ZFS and BTRFS? At work we were forced to abandon rsync > - --link-dest because of the amount of time it takes to delete old > backups when the data is primarily many millions of small files > (shared web hosting company). We don't have more advanced methods like

Feature request: allow --link-dest dir to be linked to even if file exists in target. This statement from the man page is adhered to too strongly IMHO: "This option works best when copying into an empty destination hierarchy, as rsync treats existing files as definitive (so it never looks in the link-dest dirs when a destination file already exists)". I was suprised by this behaviour

Hello compiler enthusiasts, The Apple LLVM team would like to propose that a new a security process and an associated private LLVM Security Group be created under the umbrella of the LLVM project. A draft proposal for how we could organize such a group and what its process could be is available on Phabricator <https://reviews.llvm.org/D70326>. The proposal starts with a list of goals for