You can start the Brave Browser on a Mac in incognito mode from the CLI (Terminal) using the “open -a” command:
open -a "Brave Browser" -n --args --incognito --new-window https://huf.org
open -a : opens the Application
-n : Open a new instance of the application even if one is already running
--args : the following arguments go to Brave
--incognito : what do you think?
--new-window : don't reuse an already existing browser window
looking at the manual page with “man open” will help you here.
however grave the problems were that dylan addressed in his song and 1963 album, he certainly didn’t envision how linux distributions like debian are a-changing the way in which we have to configure our network settings. if we look at how we define static ip addresses, we can see quite some dylan-esque transitions. and when you need to persistently define static routes, keeping up-to-date can be at least hard.
it’s been hardly nine months since my post about static routes in debian 9 when that method has been marked as “deprecated” and won’t actually work anymore in debian 10 “buster”. So here’s how to do both static ip and static routes in buster:
the good thing is, it’s now all in one file. just edit /etc/network/interfaces. for the not-so daring types, make a backup before the edit:
so, the other day I needed to add a static route to my raspberry’s route table. the critter is running raspbian 9 (“jessie”). this version of debianesque linux uses dhcpcd for the network configuration.
you can find a whole lot of info on how to configure the box with a static ip address. however, there are few examples for configuring a static routing table entry that will persist after a reboot.
as we all know by now, you can enter a manual route using the command:
# /sbin/route add -net 10.1.2.0/24 gw 10.1.1.100
where 10.1.1.100 is the router on your local network behind which the target network 10.1.2.0 with the netmask 255.255.255.0 (the “/24”) is to be found!
this entry will be lost after a reboot. in order to make it persistent, you have to edit/create a so-called “exit hook”. that’s a file that gets executed by dhcpd at various occasions, e.g. after the network interface has been configured with a valid address.
here’s how to do it:
edit the exit hook file. the command will create it, if it’s not there already:
# sudo vi /etc/dhcpcd.exit-hook
add the routing command, just as you’d type it on the command line (first line is for documentation):
## adding the persistent route from the example above:
/sbin/route add -net 10.1.2.0/24 gw 10.1.1.100
now, in order to activate the hook file, you can try:
# sudo service dhcpcd restart
for a definitive test issue the reboot command.
if something goes wrong, you can debug the dhcpcd hooks by editing the file /lib/dhcpcd/dhcpcd-run-hooks and change the line
you can then “tail /var/syslog” in order to see the debug output.
here we go again… wasn’t it months ago when you were fed up with that chrome cloud printing dialog?
you wanted apples’ standard dialog window with chrome! you wanted back control!! you wanted reven… – whatever!
so you updated the policy above (DisablePrintPreview=true) and lived happily ever after since… until now: “your browser is being managed by someone else!” – you want to get rid of that message, for zarquon’s sake!
the thing is, when you set the policy element back to “false”, this still counts as a modified policy.
you can set the propery back with this command in a terminal window and restarting chrome:
et abracadabra: after a chrome restart your browser belongs to you again. no evil corp controlling whatever sleazy (or not) policies are set.
jokes aside: this method is a good way to see if this policy you deleted is actually the reason for the nefarious message. if the message persists after deleting the policy, there’s still another policy active.
Chrome öffnet beim Drucken einer Webseite, oder eines eingebetteten Dokuments stets seinen eigenen Druckdialog. Seit heute habe ich das Problem, dass der Druckdialog für eingebettete pdf’s unterhalb des Dokumentes geöffnet wird und somit vom Bildschirm verschwindet.
Abhilfe: 1) größeren Monitor verwenden, oder 2) Chrome dazu überreden, den System-Druckdialog zu benutzen. Während Lösung 1 auch nach einem Systemupgrade noch sicher funktioniert, ist Lösung 2 ein wenig günstiger zu haben ;-)
Folgender Befehl in einem “Terminal” Fenster veranlasst Chrome, seinen eigenen Druck-Dialog nicht zu verwenden: