Is it safe to continue using Waldorf?

autonomy777 · 2015-03-02 09:05:45

Hi folks,

please forgive the potential "newbie idiot" factor of this post - I'm trying to find out whether it is safe to continue using Waldorf on an ongoing basis, now that it has been discontinued.

I have an age old Packard Bell which is running 32 Bit #! perfectly happily, and I am loathe to change. It's just used as an old workhorse, web surfing, Thunderbird etc - but I'd like to stay protected.

If it *IS* safe to continue, can I ask how I do so? Simply sudo apt-get update? Or do we ignore that now?

Many thanks to anyone prepared to help.

Best,

Ian

Sector11 · 2015-03-02 09:56:16

sudo apt-get update ; sudo apt-get upgrade --no-install-recommends

with or without the "--no-install-recommends" will be good for a long time yet. Once Debian Jessie becomes 'stable' - it's still frozen, then Wheezy ( #! Waldorf ) will become "Old Stable" and will receive security updates.

Considering that Debian Squeeze is currently "Debian Old Stable" and is receiving security updates until "February 2016". I would say Wheezy has a healthy run left.

pvsage · 2015-03-02 10:08:47

We really should have a sticky for this.

Waldorf is almost entirely based on Debian Wheezy, which will continue to receive security updates as Debian oldstable for at least a year after Jessie becomes the new Debian stable. Main differences between Waldorf and Wheezy are a few custom config scripts (which do not have equivalents in the Wheezy repo, so don't go uninstalling them; they shouldn't break or anything, as there should be no changes in features in oldstable, just security patches) and a few custom binaries that Philip built from source because either they weren't available in Wheezy (don't go uninstalling viewnior, for example, unless you want to replace it with something else) or the versions in Wheezy were older than the ones he built while Wheezy was in testing. Practically all the binaries in the Waldorf repo are now older than the ones in Wheezy, and have been since Wheezy went stable.

So basically, once you've installed Waldorf, you want to make sure you're following "Wheezy Proper" for updates. There's only a little prep work:

Comment out the Waldorf stanza in /etc/apt/sources.list.
Rename your /etc/apt/preferences file or simply delete it. (This file handles "apt pinning" and will be irrelevant with only Waldorf sources.)
Run the following commands in order:
```
sudo apt-get purge tint2 tint2conf
sudo apt-get update
sudo apt-get install tint2 --reinstall
sudo apt-get upgrade
```
There are reasons to purge tint2 and tint2conf first. The magnifying glass will bring up a search tool for this forum if you're really curious as to why.

Boom - you're tracking Wheezy.

autonomy777 · 2015-03-02 10:26:09

This is great news, thanks folks. I really don't have the time or the inclination to go distro hopping again, so if I can get some more lifespan out of #!, I'll gladly do so.

Thanks!

Ian

Sector11 · 2015-03-02 10:42:26

Added to the "Recommended Threads" post for this section:

#! Waldorf to Debian Wheezy - Old Stable Security Support

Is it safe, on an ongoing basis...... - Tracking Debian Wheezy into Old Stable

Maybe put it in all?

pvsage · 2015-03-02 11:25:18

I think just the stickied thread in this area should be fine. Nicely done, Sector11!

Sector11 · 2015-03-02 11:28:54

Head_on_a_Stick · 2015-03-02 20:12:17

Just to add: once @pvsage's fine advice has been followed regular updates of the APT database and system upgrades should be performed to receive any bug fixes or security updates pushed out by Debian:

sudo apt-get update
sudo apt-get upgrade

KrunchTime · 2015-03-04 06:18:21

^ Hey, he's back!

I would also like to chime in and recommend that users keep copies of the CrunchBang unique scripts and maybe pipe menus that Phil developed. Under Waldorf, the scripts are located under /usr/bin and start with cb; e.g. cb-exit.

Last edited by KrunchTime (2015-03-04 06:19:04)

MsMattie · 2015-04-14 09:12:54

I did all this and it seems to be working fine, but I would feel safer if somone with more knowledge took a look at my new sources.list below to make sure it is OK and that I am getting updates and upgrades for security. Below is my changed sources.list.

Also, the directions say to rename the etc/apt/preferences file so it is no longer used. As I recall I added something for pinning into that file when I set up Iceweasil to move up to the most recent version. So, without the preferences file, will I be heading toward an iceberg with Iceweasil update-upgrades?

etc/apt/source.list

## CRUNCHBANG
## Compatible with Debian Wheezy, but use at your own risk.
## deb [url]http://packages.crunchbang.org/waldorf[/url] waldorf main
## deb-src [url]http://packages.crunchbang.org/waldorf[/url] waldorf main

## DEBIAN
deb [url]http://http.debian.net/debian[/url] wheezy main contrib non-free
# deb-src [url]http://http.debian.net/debian[/url] wheezy main contrib non-free

## DEBIAN SECURITY
deb [url]http://security.debian.org/[/url] wheezy/updates main
# deb-src [url]http://security.debian.org/[/url] wheezy/updates main

## Iceweasel update from here: [url]http://mozilla.debian.net/[/url]
deb [url]http://mozilla.debian.net/[/url] wheezy-backports iceweasel-release

##PeerGuardian stuff - DHW
deb [url]http://moblock-deb.sourceforge.net/debian[/url] wheezy main
deb-src [url]http://moblock-deb.sourceforge.net/debian[/url] wheezy main

deb [url]http://http.us.debian.org/debian/[/url] wheezy contrib non-free main

KrunchTime · 2015-04-14 10:07:46

@MsMattie: You have wheezy repo listed twice and the line for security updates should include contrib and non-free:

deb http://security.debian.org/ wheezy/updates main contrib non-free

Although, honestly, there will probably be few, if any, security updates for contrib or non-free. Better safe than sorry though.

My $0.02 on Iceweasel...

01) Surf to Mozilla and download the latest Firefox
02) Uninstall Iceweasel
03) Comment out or remove the line in your sources.list file for Iceweasel
04) Extract Firefox and place resulting folder under /home/<user>/bin
05) Create appropriate entry in openbox menu; command should be something like ~/bin/firefox/firefox
06) To upgrade Firefox, simply go to About Firefox in the Firefox browser
07) You'll have to manually update Adobe flash

Flash version check from terminal:

sudo update-flashplugin-nonfree --status | grep Fla

If there's an upgrade:

sudo update-flashplugin-nonfree --install

Last edited by KrunchTime (2015-04-14 10:19:22)

MsMattie · 2015-04-14 10:32:22

It works.

Thanks for the simple instructions...

Head_on_a_Stick · 2015-04-14 10:56:43

KrunchTime wrote:

You'll have to manually update Adobe flash

I prepared a Debian system for my mother-in-law recently and as I won't be able to access it for about a year I used @twoion's cron jobs to update FlashPlayer every day automatically.
http://crunchbang.org/forums/viewtopic.php?id=33319

drink_n_drive · 2015-04-23 13:13:38

Hi all, I followed the steps and I almost everything did ok. What went wrong is that Thunar doesn't recognize my Seagate Expansion Drive no more. Has this happened to anyone of you guys?

EDIT: Forgot to mention that I browsed /media/Seagate Expansion Drive and got "Permission Denied", popup (the folder icon has the "X" emblem). T.I.A.

Last edited by drink_n_drive (2015-04-23 13:18:54)

tknomanzr · 2015-04-23 19:09:25

See this discussion:
Setup Polkit for User level Mounting and Unmounting

Head_on_a_Stick · 2015-04-23 19:19:48

If the drive is permanently attached just put it in /etc/fstab

twoion · 2015-04-23 20:13:26

Why is this sticky? The thread title is as unsuggestive as it can be. Can we have a proper title?

drink_n_drive · 2015-04-23 20:39:00

Thanks tknomanzr!, I was reading the wrong posts. I managed to solve this issue with mountpy command.
And, Head_on_a_Stick since no one else uses this laptop but me, and the drive is plugged in most of the times, I'll follow your advice.
Thank you guys, you are great!

Sector11 · 2015-06-13 15:21:32

twoion wrote:

Why is this sticky? The thread title is as unsuggestive as it can be. Can we have a proper title?

I just caught this ... your right ... how about:

#! Waldorf to Debian Wheezy - the safe way!

ronaldo99 · 2015-06-16 20:35:46

Hi-am I correct in saying that Wheezy is going to be long term supported,with the LTS repos that can be used from feb 2016,and will mean Wheezy will have security updates until May 2018?

Head_on_a_Stick · 2015-06-16 20:54:32

ronaldo99 wrote:

Hi-am I correct in saying that Wheezy is going to be long term supported,with the LTS repos that can be used from feb 2016,and will mean Wheezy will have security updates until May 2018?

Yes.

https://wiki.debian.org/LTS

vlax · 2015-08-19 19:54:04

pvsage wrote:

Practically all the binaries in the Waldorf repo are now older than the ones in Wheezy, and have been since Wheezy went stable.
So basically, once you've installed Waldorf, you want to make sure you're following "Wheezy Proper" for updates. There's only a little prep work:
(...)
Boom - you're tracking Wheezy.

I stay with my Waldorf-freezy-and-wheezy --, so, thanks for this useful quick guide;

CrunchBang Linux

SEARCH

#1 2015-03-02 09:05:45

Is it safe to continue using Waldorf?

#2 2015-03-02 09:56:16

Re: Is it safe to continue using Waldorf?

#3 2015-03-02 10:08:47

Re: Is it safe to continue using Waldorf?

#4 2015-03-02 10:26:09

Re: Is it safe to continue using Waldorf?

#5 2015-03-02 10:42:26

Re: Is it safe to continue using Waldorf?

#! Waldorf to Debian Wheezy - Old Stable Security Support

#6 2015-03-02 11:25:18

Re: Is it safe to continue using Waldorf?

#7 2015-03-02 11:28:54

Re: Is it safe to continue using Waldorf?

#8 2015-03-02 20:12:17

Re: Is it safe to continue using Waldorf?

#9 2015-03-04 06:18:21

Re: Is it safe to continue using Waldorf?

#10 2015-04-14 09:12:54

Re: Is it safe to continue using Waldorf?

#11 2015-04-14 10:07:46

Re: Is it safe to continue using Waldorf?

#12 2015-04-14 10:32:22

Re: Is it safe to continue using Waldorf?

#13 2015-04-14 10:56:43

Re: Is it safe to continue using Waldorf?

#14 2015-04-23 13:13:38

Re: Is it safe to continue using Waldorf?

#15 2015-04-23 19:09:25

Re: Is it safe to continue using Waldorf?

#16 2015-04-23 19:19:48

Re: Is it safe to continue using Waldorf?

#17 2015-04-23 20:13:26

Re: Is it safe to continue using Waldorf?

#18 2015-04-23 20:39:00

Re: Is it safe to continue using Waldorf?

#19 2015-06-13 15:21:32

Re: Is it safe to continue using Waldorf?

#20 2015-06-16 20:35:46

Re: Is it safe to continue using Waldorf?

#21 2015-06-16 20:54:32

Re: Is it safe to continue using Waldorf?

#22 2015-08-19 19:54:04

Re: Is it safe to continue using Waldorf?

Board footer