Skip to main content

 

Using floss software as professional workflow alternative


For the very first time I introduced a # workflow in the job of my wife, we submitted some permit plans that she realized in Revit and that I layout on my # + # box using: #, # #, # and again #.

I imported all the necessary PDFs in Scribus and then exported the plans in black and white without losing quality or rasterizing the vector graphic. The print quality was very good (even though I didn't see it actually).

Scribus is often quite wooden but after a couple of proofs I found the best method to create the title block and to prepare the proper master pages. Unfortunately the preview of the PDF on Scribus is not yet in high-res, neither in preview mode, but is enough to lay out the tables in the right position.

It would be fantastic if she may consider # as alternative to Revit, but I think it will never happen... 🤔

# # #

 

Why I ditched POP!_os 20.04


In total counter-sense, as usual, here my reasons to ditch POP!_os 20.04!

https://write.snopyta.org/gnuserland/make-the-linux-desktop-great-again-a-year-later

# # # # # # # # # #

 

Hi folks,

I am trying to install # however the # # doesn't recognize the # raid0 I prepared before on the terminal hence I don't have a place where putting the OS, unless I don't format the disk and break the raid.

I have been reading the # wiki and the official btrfs wiki during these days but I haven't understood if I can create a raid after the OS installation on the first disk, and then create the raid with the second. I haven't done this last option though.

I have very few spare time any suggestion that makes me save time is really appreciated, thanks!

# # # #

2 people reshared this

 
No, those are entirely independent. You can most certainly use raid modes on any btrfs filesystem if you have multiple physical devices. You can create multiple filesystems each of which is spread across multiple physical devices, even the same devices if you use partitions.

For example, the first filesystem composed of sda1 and sdb1 mounted on / and the second filesystem composed of sda2 and sdb2 mounted on /home

Of course then it becomes inconvenient to change the space allocation unless you use LVM instead of raw partitions. But if you're going to get that complicated you might as well use subvolumes in the first place.
 
Thank you again for your kind reply... I don't need, actually, also the home over a btrfs. I was originally interested in snapshots and rollingback, then reading the documentation I realized that I could use a RAID on two identical ssd I have on my machine. A wise partition setup is good but an overly complicated setup might be not. I'll go doing further tests..

 

Hi folks,

I am evaluating the option of using # for / (root) on my new installation.

The most compelling feature I am interested in is the snapshot/rollback one, however this will take space, hence my question is: how many disk space does # require for snapshots?

I am planning to reserve for / (root) 100GB, will be this space enough?

Thanks!

# # # # #

Daniel reshared this.

 
After had read the Debian wiki I lost my interest, better using btrfs on a distro that is design to work with it like OpenSuse; I'll check out if there are implementation for ext4 for snapshots and rollback...
 
LVM serves that scope, and my / (root) will be on unencrypted LVM logical volume. Now I just figuring out to create a script that overwrite your snasphot just before everytime you are goingo to upgrade the packages... 🤔

 
Hmm... aren't those the week numbers where it hits 32?
 
Hey you may right, shame on me... 🤣🤣🤣

 

Librem Mail


The latest version of # (1.1.0) from # got a tremendous enhancement!

Better UI, better settings, modern look! Started as a simple fork of # now it is one of the best # # Client available for #.

Warmly recommended if you are looking for a # app for your mobile, I installed it from #.

# #

2 people reshared this