You are not logged in.
UEFI:
If you are trying to make an image of the system you have on a non-EFI box, refracta asks for the grub-uefi which if installed it removes the grub-pc etc. needed on the system. How do you do this?
DIY Faraday canopy; how about that recipe?
I don't think either of those two should worry about anything.
There was a line towards the end of the movie "flashback" with Dennis Hopper saying:
"The 90s are going to make the 60s look like the 50s"
It is hard to interpret this, even after the 90s came and went.
Good music film, by the way.
Am I missing something?
Is it all video or is it video on youtube? If you have a local video file like an mpeg, will it not play?
In order to keep the browser unclogged and the cookie system separate, when I get a utube link I play it with smplayer or browse through youtube with smtube. In "most" cases it works as google changes their codings on an hourly basis and those video players must catch up all the time.
Ever since I got pale moon back I have not played a single utube video that had a problem, so it must be a hw related issue.
Flash is dead, it is done, after all this trouble it caused for more than a decade they pulled the plug. I hope adobe's stock-holders end up on the street begging for bread. Not my bread!
Deja-lost his-view .... I am imagining seeing things on forum that were on the list and list things that are on the forum.
Anyway, as there seems to be some confusion of the actual spelling of the entries in /etc/apt/sources.list, and after some clarification by fsmithred I gathered a huge list of repositories to choose from and what I believe is the correct entry.
From: fsmithred@****
To: dng@lists.dyne.orgMy understanding is that for anything found under /merged on the server,
you should use /merged in your sources, and anything found ONLY under
/devuan needs to have /devuan in the sources.
deb https://pkgmaster.devuan.org/merged/ ascii main contrib non-free
deb https://pkgmaster.devuan.org/merged/ ascii-backports main contrib non-free
deb https://pkgmaster.devuan.org/merged/ ascii-proposed-updates main contrib non-free
deb https://pkgmaster.devuan.org/merged/ ascii-security main contrib non-free
deb https://pkgmaster.devuan.org/merged/ ascii-updates main contrib non-free
deb https://pkgmaster.devuan.org/devuan/ ascii-proposed main contrib non-free
deb https://pkgmaster.devuan.org/devuan/ ascii-proposed-security main contrib non-free
deb https://pkgmaster.devuan.org/merged/ ceres main contrib non-free
deb https://pkgmaster.devuan.org/devuan/ experimental main contrib non-free
deb https://pkgmaster.devuan.org/merged/ jessie main contrib non-free
deb https://pkgmaster.devuan.org/merged/ jessie-backports main contrib non-free
deb https://pkgmaster.devuan.org/devuan/ jessie-proposed main contrib non-free
deb https://pkgmaster.devuan.org/devuan/ jessie-proposed-backports main contrib non-free
deb https://pkgmaster.devuan.org/devuan/ jessie-proposed-security main contrib non-free
deb https://pkgmaster.devuan.org/merged/ jessie-proposed-updates main contrib non-free
deb https://pkgmaster.devuan.org/merged/ jessie-security main contrib non-free
deb https://pkgmaster.devuan.org/merged/ jessie-updates main contrib non-free
deb https://pkgmaster.devuan.org/devuan/ sid main contrib non-free
deb https://pkgmaster.devuan.org/merged/ stable main contrib non-free
deb https://pkgmaster.devuan.org/merged/ stable-backports main contrib non-free
deb https://pkgmaster.devuan.org/devuan/ stable-proposed main contrib non-free
deb https://pkgmaster.devuan.org/merged/ stable-proposed-updates main contrib non-free
deb https://pkgmaster.devuan.org/merged/ stable-security main contrib non-free
deb https://pkgmaster.devuan.org/merged/ stable-updates main contrib non-free
deb https://pkgmaster.devuan.org/merged/ testing main contrib non-free
deb https://pkgmaster.devuan.org/merged/ testing-backports main contrib non-free
deb https://pkgmaster.devuan.org/devuan/ testing-proposed main contrib non-free
deb https://pkgmaster.devuan.org/merged/ testing-proposed-updates main contrib non-free
deb https://pkgmaster.devuan.org/merged/ testing-security main contrib non-free
deb https://pkgmaster.devuan.org/merged/ testing-updates main contrib non-free
deb https://pkgmaster.devuan.org/merged/ unstable main contrib non-free
deb tor://devuanfwojg73k6r.onion/ should be replaced to use the onion address or you could add tor+https://pkg.... to use tor without onion addresses.
I hope this helps to end the confusion. I think some of those repositories, like sid, may be empty but that is not a 404 error, or the side that has non-free may be empty. I hope that someone will verify this list is correct before my mistake or misperception spills more panic.
PS For https and tor you need apt-transport-https & apt-transport-tor otherwise substitute http from the list, right?
PS2 The tor-project repositories are:
deb tor://sdscoq7snqtznauu.onion/torproject.org/ jessie/stretch/buster/sid main (choose a distribution to match)
deb tor://sdscoq7snqtznauu.onion/torproject.org/ tor-experimental-0.3.2.x-stretch main (switch stretch to one you want)
or https://deb.torproject.org/torproject.org
but you must first import the gpg key (look it up at their web page in the linux/debian/ubuntu instructions for tor)
I keep the OEM names and they always seem to be different than previous. This has a date right?
Miyo-XTRA-Ascii-64bit-20171024
It also has a signature file for shasums and I do check those. It is about .5GB which is damn good for a developed desktop.
If you built a stretch (ascii equivalent) with a base install and just add X,DM,& openbox, I think you end up with more than Miyo-Xtra. Then you have to go through the pain of installing more stuff to make it functional (relatively) and configuring. Unless you are using openbox for choosing colors and fonts for a terminal. Debian--menu seems like something from the 70s and most of the menu items are not functional till you install their pointers.
I'm going to work on my celeron-xtra now with 256k-Ram
In what ways is FF-esr better beyond the marketing propaganda?
As I understand it the extended life support provides a more stable code that can be audited line by line before a new version is released and all revisions can be added to the existing code instead for an all new package replacing the old. This gives more (if not adequate time) for security concerns to be addressed and published. Meanwhile bugs in functionality cand be backported if the apply. I believe the current version is 52-4 and has most of any bugs that ever appeared on 52 solved.
But there may be more to this than meets the eye. It has only been a year or two? that debian quit making their own ff as iceweasel and icedove instead of tb. I believe this -esr series was the bargain they struck with mozilla for a free-er and more steady code.
I was referring to the image (iso)
I am amazed of the size of the thing. When I gave it a try I added a tiny bit more and the image doubled.
This is how NOT to install firefox
http://linux.palemoon.org/
Splendid experience on ascii and on artix
If it wasn't for bluejeans with beer spilled on top I would have never discovered it.
It comes on vuu-do too
Katolaz from the DNG-list is trying to clarify
> > The repository is not updated and the previous index files will be used. GPG error: tor://devuanfwojg73k6r.onion/merged ascii InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BB23C00C61FC752C apt is telling you that you don'e have the key for that repo.
You must: # apt-get update # apt-get install devuan-keyring because amprolla3 is using a new signing key, which has been included in the latest devuan-keyring.
This was actually explained in the announcement to this list. I admit that we didn't announce the transition to amprolla3 for the onion address. Sorry for that.> > I think I'm getting somewhere.
> > The merged repositories will not update because the key is expired. One would have to revert to the /devuan/ update the keyring and re-edit the repositories with the new key to be able to upgrade.
> > But what about proposed-updates, is this devuan or merged? jessie-proposed is under /devuan jessie-proposed-updates is under /devuan experimental is under /devuan The rest is under /merges, if I have not missed something.
> > I think there is proposed-security as well.
> > The installation I normally use and was checked frequently didn't have the same problem as the ones that have been unattended for a month or two. Somehow it seems as the keyring was updated before the pkgmaster deal and that makes the difference.> That's because you need to install the latest devuan-keyring, as explained above. HTH KatolaZ -- [ ~.,_ Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ]
What he seems to not understand is that the repositories as they were could not be updated with the old key and the new key couldn't be updated with /merged
Only when the repositories were switched to /devuan was I able to update the key. Switching then back to /merged solved the issue but it would have been nice if there were more clarified instructions before some of us were "automatically" shifted to the new system.
AGAIN, the installation that was kept up to date frequently didn't have such a problem, while the ones who hadn't been updated since before the last keyring was issued were impossible to update as they were.
SO, if you, the forum member or outsider, have not updated your installation for a while and are on onion repositories chances are you may experience the same mess.
The underline of this is that "people" tend to respond a bit nasty here (Devuan) if they thing your question is putting blame on them, especially on that DNG list, when all you ask is for clarification to the lack of detailed instruction.
Amprolla3 was announced as a testing option for people to choose. Those utilizing onion repositories were automatically and after the fact shoved to be testing something new. And this made those with un-updated keyrings unable to update or upgrade anything. That is the bottom line!
While some of you are consumed in cock-fights off-topic there still is some ambiguity in what onion repositories should be.
I got a whole bunch of errors today from missing keys of repositories:
I switched all /merged/ to ../devuan/
Is this correct for all ascii, ceres, experimental? It was the only way I could get updated releases
All of the old tor://devuanfwojg73k6r.onion/merged/ are dead?
Then how come onion addresses have all shifted automatically to http://pkgmaster.devuan.org/merged/ when they are using merged instead of devuan?
Or was this some temporary outage?
I'm waiting on the release notes so I can apply them
I've had 2 of these for months, 1 is 32b the other 64b
The third is vuu-do64ascii
I by no means endorse any of them, and you do have a valid concern and everyone should.
WC has been discontinued since 5/16, so all those who do have one it is what they declared back then, or earlier.
TProject never had one, one of their developers did a personal one, and she fled the US to avoid the harassment she was getting for her involvement in tor and leap (bitmask is leap). On the other hand bitmask is code, the individual vendors of the service should be of concern. 2 which appear to be US based do have a WC. The rest are out of the US, as is leap.se
There was a good discussion on TP's site on the importance and the not so absolute importance of birds.
It is the struggle that always matters, not the absolute outcome of a battle. In lack of massively accepted alternatives it is best to support the little we do have believing in a good direction.
A drawback of being a us citizen is that you can be abducted (in 98% of the world) and brought back to "base". The rest of us can tweet freely. Now that is a fallacy in itself. Nobody had heard of snowden till he was persecuted.
I don't know if anyone has ever tried this https://bitmask.net/en/install/linux
The historical development for this can better be seen here, their parent site https://leap.se/
It used to work before in Devuan but there seems to be a new version that have impossible dependencies. The past version 0.92 would work on and off on Debian depending on how dependencies on Debian changed by upgrades. Now the new one 0.10 doesn't work on Devuan.
What makes their standalone work then? Of course the instructions to do a system install via their debian based repository may work for debian but I don't see why wouldn't python scripts work on Devuan. When it does work it is great.
If anyone who understands such things better has an interest in this and can throw some light it would be appreciated. Maybe if we can make it work here as well we can tell them to add a devuan repository. I think their jessie-sid and ubuntu repositories are identical.
This is what quality journalism is all about. Tomorrow's headlines would be referring to this forum as the source of the news for the demise of vuu-do
@greenjeans is nowhere to be found either..... sources have him vacationing in vuu-do land, Jamaica.
There was a time I took an interest in systemd and how it really worked. The idea seemed interesting, but the chaos it created and that you could hardly audit was like the labyrinth. I gave up.
When I looked at openrc, runit, and a little bit of s6, my first reaction was "Is that it?"
I thought I was missing something and there were other branches to the system.
While messing with Devuan early on, I installed wheezy. It felt like a luxury supersportscar without the a/c, stereo, carpeting, etc.
When I converted it to Devuan it was like putting rollbars on it and throwing out the emissions stuff.
I tried the same with upgrading wheezy to jessie and then going to devuan..... it was like loading trash from the one door and trying to clean the car back out from the other door.
Wheezy, the last true debian!
Now we have systemd in debian, arch, or redhat flavors. I think the developers on those systems are loosing their connectivity. They can work independently and just relate to systemd. It is a matter of time till they all fall apart and work directly for the borg.
If anyone has missed the video you should give it 2' of your time https://sysdfree.wordpress.com/113/
Well that explains why I was having repository mix ups earlier this week, I was on this thing before it even got announced.
By the way, socks5 is one heck of a good way to make sure nobody messes with your packages between mirror and your disk.
I think this is really good work, it is appreciated. I hope most people will appreciate it too.
[LIKE]
For memory Mozilla Firefox requires by force GTK3, pulseaudio and some day soon systemd to use it.
[/like]
I was seeing some weird action a few days ago but thought I was doing something wrong, which I always do and forget to fix back what I broke. While on some recent minor upgrade I saw Debian's repository come up during update, and that was an instruction by devuan while using the onion addresses.
So, do the new reps have onion addresses as well and what are they?
Re: Fsmithred
No, no sydlexia here I am talking about pamac the equivalent of synaptic, not pacman the equivalent of apt/dpkg
It is pamac that has an app-tray-indicator for when an update to a package is available. It may have been originally a Manjaro invention that the AUR community passed to the Arch world, but don't take my word on it. It used to be simple and functional and they have made something that looks like an ubuntu gadget.
In Arch there is pkg manager like synaptic called pamac. There is a tray-app-indicator for pamac that changes the color of a star when an upgadeable pkg is available. One can set the period when repeated updates take place.
But wouldn't the frequency you mention above take a toll on the mirrors?
glancing at the repository it seems as devuan and merged have the same content (structure).
The problem appeared to be ffmpeg and some related library, it eventually got upgraded
The repo. that wanted to change name with apt was proposed-updates but appears the same in both devuan and merged
Interesting find was a |sid|
../
contrib/ 20-Oct-2017 10:02 -
main/ 20-Oct-2017 10:02 -
non-free/ 20-Oct-2017 10:02 -
InRelease 20-Oct-2017 10:03 128669
Release 20-Oct-2017 10:03 128147
Release.gpg 20-Oct-2017 10:03 473
and ceres
../
contrib/ 20-Oct-2017 10:02 -
main/ 20-Oct-2017 10:02 -
non-free/ 20-Oct-2017 10:02 -
InRelease 20-Oct-2017 10:03 128669
Release 20-Oct-2017 10:03 128147
Release.gpg 20-Oct-2017 10:03 473
I tried an update and it asked me to rename some repositories (from ../merged/ to /../devuan/) and then it run ok.
When 6 updates showed up the updated files couldn't be located in the repositories.
Anyone knows what's up? Is it just a temporary problem of updating mirrors?
Boring as usual, everything works, nothing to fix, nothing to configure ..... just a little more refined and tuned with a couple more gadgets
Still that Alt-F is in there, which in most editors and browsers, and many other guis, opens up the top left menu "File"
Not on vuu-do!