Jessie upgrade without systemd [was: Debian *not very good]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Nov 25, 2016 at 03:57:53PM -0800, Patrick Bartek wrote: > On Fri, 25 Nov 2016 21:26:06 + (UTC) Latincom > wrote: > > > On Fri, 25 Nov 2016 16:31:54 +, Brian wrote: > > > > > On Fri 25 Nov 2016 at 15:21:23 +, oldbluebear wrote: > > > > > > [...Lots of disgruntlement snipped...] > > > > > >> How can I at this stage bring this machine back nearer to SySV? > > > > > > You can bring it back in all its glory with > > > > > > apt-get install sysvinit-core > > > > Is there a step by step guide or How to on line? > > I have 1 Wheezy without Systemd, and i would like to upgrade it. > > Thanks. > > If you do a normal dist-upgrade Wheezy to Jessie, sysvinit will be > replaced with systemd. Not forcefully. > And probably screw everything up.. Now this is an unnecessarily loaded statement. Given the smoking holes the last flame war has left[1], I'd tread carefully if I were you ;-) > I suggest > you do what I did: a clean install of a terminal only Jessie system, > replace systemd with sysvinit, then build the system up from there. > Just remember GNOME3 has systemd as a dependency. Other utilities do, > too. I used LXDE which doesn't to keep things simple. I usually just > run a window manager Openbox and a single LXPanel, but that involves a > lot more configuration. Too much for an initial test. While possible, this isn't really necessary. FWIW I managed a clean Jessie upgrade without touching systemd, by just following the instructions. If you want a straight upgrade without systemd, apt-pinning seems to be the agreed upon way: https://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html#systemd-upgrade-default-init-system Note that many things (Gnome, I'm looking at you) *require* systemd these days: it'll be much more difficult to avoid systemd if you want a "modern" desktop environment. Myself, I'm on Fvwm. I don't even need DBUS :-D thanks [1] Sorry for the somewhat grumpy tone, but I'm pretty tired of people whining about systemd and borderline disrupting otherwise functional mailing lists with their rage. I strongly dislike systemd, yes, but i see no reason to hate systemd proponents let alone to harrass them. On the contrary, they are doing free software, FFS! If all that energy spent on foaming at the mouth and hatred had been spent on keeping viable alternatives to systemd afloat and running, we'd be in much better shape these days (and perhaps MikeeeUSA would have found other coattails to ride on). - -- tomás -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlg5T7oACgkQBcgs9XrR2kZ7vACcDEQ6DAqH1YBcKkdTJfv+fBin PXIAmwQTe2QUPn1tSD8XhjPhaTH/BatB =8Pqr -END PGP SIGNATURE-
Re: forcefsck inconsistency
On Wed, 23 Nov 2016, David Wright wrote: As for the root filesystem, are you saying that it was not checked even when you did what I suggested? What does # tune2fs -l /dev/sda1 | grep 'st ch' show (assuming / is /dev/sda1)? hi David, I said "inconsistency, but I must add "behaviour impossible to understand": 1/ According the tune2fs output, the check on / was actually done. I naïvely looked at syslog to find the checked devices, and I could not imagine that the fsck checks are reported in syslog for all partitions, but not for /... 2/ An other strange behaviour. For my /dev/sda3 ext4 partition, I get: in syslog Nov 26 07:53:37 pfr2 systemd[1]: Started File System Check on /dev/sda3. with ->>tune2fs -l /dev/sda3 | grep 'st ch' Last checked: Wed Nov 23 11:35:43 2016 3/ for the /dev/sdg1 partition for which no check was done at boot, I tried manually, but that didn't work. I then decided to recreate it (it was just a backup): - delete all partitions on /dev/sdg - add a Linux partition - run mkfs.ext4 After that, the "Maximum mount count" was -1. Is this normal? I then set it to 30, and the behaviour is half normal: the fsck check is not done at boot, but I can do it manually. I imagine that it's a specific feature of this Seagate model. cheers, -- Pierre Frenkiel
Re: Jessie upgrade without systemd [was: Debian *not very good]
On Sat, 26 Nov 2016 10:02:50 +0100 wrote: > On Fri, Nov 25, 2016 at 03:57:53PM -0800, Patrick Bartek wrote: > > > > If you do a normal dist-upgrade Wheezy to Jessie, sysvinit will be > > replaced with systemd. > > Not forcefully. > > > And probably screw everything up.. > > Now this is an unnecessarily loaded statement. Given the smoking holes > the last flame war has left[1], I'd tread carefully if I were you ;-) > A fair number of wheezy systems will be servers, upgraded many times. Mine started out as sarge. What are the odds of such a system making the change to systemd without problems? I converted a sid to systemd, but had to give up on it as it became too flaky, unstable in all senses of the word. A workstation isn't really a problem to reinstall from scratch, an old server is a nightmare. Obviously I had to do a reinstallation to move to 64 bits, but that was a get-selections/set-selections job, with the old /etc pretty much copied over. All the same software, just 64 bit, and more importantly, all the old scripts. That's not going to work with a systemd-based reinstall. > > If you want a straight upgrade without systemd, apt-pinning seems > to be the agreed upon way: > > > https://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html#systemd-upgrade-default-init-system > > Note that many things (Gnome, I'm looking at you) *require* systemd > these days: it'll be much more difficult to avoid systemd if you > want a "modern" desktop environment. > > Myself, I'm on Fvwm. I don't even need DBUS :-D > And my server doesn't have X. But I don't expect that to eliminate all systemd problems. -- Joe
Package configure problem during Installation.
Hello! I am unable to configure the package manager. The mirrors given in the list of INDIA can't fetch any content. Is there any other way to configure it. I would really appreciate any help. Thank You!
Is preseed.cfg flexible enough?
I have a laptop whose *SOLE* purpose is to have multiple installs of Debian for demonstration of different ways Debian may be configured. While I work out kinks I am using Mate as my D.E. I find some Debian defaults annoying. Setting them to reasonable values on a running system is straight forward but becomes annoying every time an installation is done. Problem 1. Defeat automounting of usb flash drives This can be handled by gsettings set org.mate.media-handling automount false on a running system if Mate is installed. Problem 2. Default font size is too small. In Mate that can be remedied *on a PER USER* basis by menu option System>-Preferences->Appearance->Fonts The default there is "10". I also have note that "10" appears as a default size elsewhere implying that it is system wide. Can I force everything to use "14"? Problem 3. File-managers default to pretty Icons rather than informative List view. Can preseed.cfg handle those and similar in an D.E. agnostic manner? The possibility is hinted near the end of https://www.debian.org/releases/stable/i386/apbs05.html.en#preseed-chainload . TIA
Re: Package configure problem during Installation.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, Nov 26, 2016 at 04:29:19PM +0530, amir khan wrote: > Hello! > I am unable to configure the package manager. The mirrors given in the list > of INDIA can't fetch any content. > Is there any other way to configure it. I would really appreciate any help. Have you tried with any other mirrors? regards - -- tomás -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlg5jkQACgkQBcgs9XrR2kavDwCfTsv7zZ2LUqcHyCpqb2J5rQbu GBEAn26EQPj23nM1fPr1ASrTTBYPecuE =hwF2 -END PGP SIGNATURE-
Re: Jessie upgrade without systemd [was: Debian *not very good]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, Nov 26, 2016 at 10:27:07AM +, Joe wrote: > On Sat, 26 Nov 2016 10:02:50 +0100 > wrote: > > > On Fri, Nov 25, 2016 at 03:57:53PM -0800, Patrick Bartek wrote: > > > > > > > If you do a normal dist-upgrade Wheezy to Jessie, sysvinit will be > > > replaced with systemd. > > > > Not forcefully. > > > > > And probably screw everything up.. > > > > Now this is an unnecessarily loaded statement. Given the smoking holes > > the last flame war has left[1], I'd tread carefully if I were you ;-) > > > > A fair number of wheezy systems will be servers, upgraded many times. > Mine started out as sarge. What are the odds of such a system making the > change to systemd without problems? [...] > And my server doesn't have X. But I don't expect that to eliminate all > systemd problems. I'd say you are in a pretty good shape to choose whatever init system suits you without big problems, then. regards - -- tomás -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlg5jeMACgkQBcgs9XrR2kaaAwCeLOlri8qYZzoGouk/KtCWFXYC a0EAnA3o0NsEaTlzzH/3aYj0J99pJq0+ =MAqs -END PGP SIGNATURE-
Re: Is preseed.cfg flexible enough?
Hi Richard, On Sat, Nov 26, 2016 at 06:56:23AM -0600, Richard Owlett wrote: > Can preseed.cfg handle those and similar in an D.E. agnostic manner? If you can't find a feature or setting built in to d-i's preseed, then you can always preseed a program or shell script and run it at the end of the install: d-i preseed/late_command/path/to/some/script.sh So yes ultimately preseed can do anything, with a greater or lesser degree of effort. It seems like you have already worked out the commands to type to fix your issues manually, so you are half way there. If the problem is how to achieve it globally, regardless of desktop environment, then I would suggest the question isn't really about preseed. The first step would be to work out how to do it manually, and then put it in preseed.cfg. I'm afraid I don't know how to solve your issues globally without regard to desktop environment. Cheers, Andy
Re: Jessie upgrade without systemd [was: Debian *not very good]
On Sat, Nov 26, 2016 at 10:27:07AM +, Joe wrote: > On Sat, 26 Nov 2016 10:02:50 +0100 > wrote: > > > On Fri, Nov 25, 2016 at 03:57:53PM -0800, Patrick Bartek wrote: > > > > > > > If you do a normal dist-upgrade Wheezy to Jessie, sysvinit will be > > > replaced with systemd. > > > > Not forcefully. > > > > > And probably screw everything up.. > > > > Now this is an unnecessarily loaded statement. Given the smoking holes > > the last flame war has left[1], I'd tread carefully if I were you ;-) > > > > A fair number of wheezy systems will be servers, upgraded many times. > Mine started out as sarge. What are the odds of such a system making the > change to systemd without problems? > A reasonable amount. I did it, and experienced no issues at all. In fact I had more issues while upgrading to wheezy. > I converted a sid to systemd, but had to give up on it as it became too > flaky, unstable in all senses of the word. A workstation isn't really a > problem to reinstall from scratch, an old server is a nightmare. > > Obviously I had to do a reinstallation to move to 64 bits, but that was > a get-selections/set-selections job, with the old /etc pretty much > copied over. All the same software, just 64 bit, and more importantly, > all the old scripts. That's not going to work with a systemd-based > reinstall. You hardly can blame systemd for a 32/64 bit switch. so you exchange binaries, and? Not s systemd issue. And while we are at a network issue topic (OP). Systemd is actually better than any network-manager or your beloved init scripts at that. It tracks much more reliably the status of your interfaces than any other method. Period. -H -- Henning Follmann | hfollm...@itcfollmann.com
Re: Package configure problem during Installation.
On Sat, Nov 26, 2016 at 5:59 AM, amir khan wrote: > Hello! > I am unable to configure the package manager. The mirrors given in the list > of INDIA can't fetch any content. > Is there any other way to configure it. I would really appreciate any help. > > Thank You! Hi Amir Khan, There are currently 3 Debian mirrors in India - debianmirror.nkn.in, ftp.iitm.ac.in, mirror.cse.iitk.ac.in . The list changes from time to time. To get the latest set of mirrors, go to https://www.debian.org/mirror/list and search for the country of interest (which in your case is India). You can try these mirrors one-by-one and see which one works for you. But I do not suggest this for the following reasons 1) This is not a scalable approach. For example, there could be many mirrors for some countries (ex:- United States has 60) and trying each can be tiring. 2) Geographical proximity to a mirror does not always mean that it will serve you best. 3) Not all mirrors carry all the architectures. For example, debianmirror.nkn.in carries three architectures while ftp.iitm.ac.in carries five. 4) The process has to be repeated every time you move to a different location which can be annoying for laptop users. For these and many other reasons, it is better to use the "mirror redirector service". The idea is to add something like deb http://httpredir.debian.org/debian jessie main contrib non-free in the /etc/apt/sources.list and let apt-get figure out the best mirror for you. More details on this approach can be found at http://httpredir.debian.org/ . hope that helps raju -- Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog
Re: Jessie upgrade without systemd [was: Debian *not very good]
On Sat, 26 Nov 2016 09:01:33 -0500 Henning Follmann wrote: > On Sat, Nov 26, 2016 at 10:27:07AM +, Joe wrote: > > On Sat, 26 Nov 2016 10:02:50 +0100 > > wrote: > > > > > On Fri, Nov 25, 2016 at 03:57:53PM -0800, Patrick Bartek wrote: > > > > > > > > > > If you do a normal dist-upgrade Wheezy to Jessie, sysvinit will > > > > be replaced with systemd. > > > > > > Not forcefully. > > > > > > > And probably screw everything up.. > > > > > > Now this is an unnecessarily loaded statement. Given the smoking > > > holes the last flame war has left[1], I'd tread carefully if I > > > were you ;-) > > > > A fair number of wheezy systems will be servers, upgraded many > > times. Mine started out as sarge. What are the odds of such a > > system making the change to systemd without problems? > > > > A reasonable amount. > I did it, and experienced no issues at all. In fact I had more issues > while upgrading to wheezy. Good to hear. Yes, upgrades have been getting progressively less easy. > > > I converted a sid to systemd, but had to give up on it as it became > > too flaky, unstable in all senses of the word. A workstation isn't > > really a problem to reinstall from scratch, an old server is a > > nightmare. > > > > Obviously I had to do a reinstallation to move to 64 bits, but that > > was a get-selections/set-selections job, with the old /etc pretty > > much copied over. All the same software, just 64 bit, and more > > importantly, all the old scripts. That's not going to work with a > > systemd-based reinstall. > > You hardly can blame systemd for a 32/64 bit switch. > so you exchange binaries, and? Not s systemd issue. Sorry, I may not have been clear, I was saying that reinstalling to jump the 32/64 bit barrier has been the only significant upheaval in the progress of my server since sarge, and that reinstallation was like for like and therefore quite simple. If I have to reinstall the server with systemd from the beginning, because the upgrade is too difficult, then restoring its current functionality is likely to be significantly harder than the 32/64 bit change was. I will be migrating configurations between different Debian versions manually, at the same time as dealing with any systemd issues. I hope very much to avoid the need for that. > > And while we are at a network issue topic (OP). > Systemd is actually better than any network-manager or your beloved > init scripts at that. It tracks much more reliably the status of your > interfaces than any other method. Period. > Good, although I have had no trouble with networking so far, and have never installed network-manager on this machine. It has two permanent Ethernet ports and no other interfaces than lo and an openvpn server. -- Joe
Re: Package configure problem during Installation.
kamaraju kusumanchi wrote: > For these and many other reasons, it is better to use the "mirror > redirector service". The idea is to add something like > deb http://httpredir.debian.org/debian jessie main contrib non-free > in the /etc/apt/sources.list and let apt-get figure out the best > mirror for you. More details on this approach can be found at > http://httpredir.debian.org/ . httpredir is somewhat deprecated now. The new official service is deb.debian.org: deb http://deb.debian.org/debian jessie main contrib non-free But you can use both at the same time to get the maximum coverage, of course. Grüße, Sven. -- Sigmentation fault. Core dumped.
debian on lenovo carbon thinkpad 4th generation confirmation report
Hello, I would like to confirm the successfully running Debian testing 'stretch' on Lenovo Thinkpad Carbon X1 4th generation: TYPE 20FC-0038PB production 16/07 1) jessie wifi doesn't work because lack of drivers for Intel® Dual Band Wireless-AC 8260 which is only available in >4.1 linux kernel. So I have to upgrade my installation from jessie to testing 2) after adding firmware https://wireless.wiki.kernel.org/_media/en/users/drivers/iwlwifi-8000-ucode-25.30.13.0.tgz to /lib/firmware wifi works correctly 3) audio and video works 4) suspend/resume works 5) gnome desktop works 6) usb 3.0 works 7) keyboard/touchpad works Greets to all Debian users, Karol
Re: Package configure problem during Installation.
On Sat, Nov 26, 2016 at 11:09 AM, Sven Hartge wrote: > kamaraju kusumanchi wrote: > >> For these and many other reasons, it is better to use the "mirror >> redirector service". The idea is to add something like > >> deb http://httpredir.debian.org/debian jessie main contrib non-free > >> in the /etc/apt/sources.list and let apt-get figure out the best >> mirror for you. More details on this approach can be found at >> http://httpredir.debian.org/ . > > httpredir is somewhat deprecated now. > > The new official service is deb.debian.org: > > deb http://deb.debian.org/debian jessie main contrib non-free > > But you can use both at the same time to get the maximum coverage, of > course. Where is it documented that httpredir is deprecated and that we should use deb.debian.org's service going forward? Has it been announce somewhere? Also, will it work for Jessie or is it more for stretch or later? thanks raju -- Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog
Re: Package configure problem during Installation.
kamaraju kusumanchi wrote: > On Sat, Nov 26, 2016 at 11:09 AM, Sven Hartge wrote: >> httpredir is somewhat deprecated now. >> >> The new official service is deb.debian.org: >> >> deb http://deb.debian.org/debian jessie main contrib non-free >> >> But you can use both at the same time to get the maximum coverage, of >> course. > Where is it documented that httpredir is deprecated and that we should > use deb.debian.org's service going forward? Has it been announce > somewhere? There has been a thread on debian-devel (I can't find the Message-ID at the moment) and the latest version of the next debian-installer for Stretch switched the URL from httpredir.debian.org to deb.debian.org. > Also, will it work for Jessie or is it more for stretch or later? It will work a bit more efficient for Stretch+, but it also works as intended for Wheezy and Jessie. Grüße, Sven. -- Sigmentation fault. Core dumped.
Re: Package configure problem during Installation.
On Sat, Nov 26, 2016 at 11:33 AM, Sven Hartge wrote: > kamaraju kusumanchi wrote: > >> Where is it documented that httpredir is deprecated and that we should >> use deb.debian.org's service going forward? Has it been announce >> somewhere? > > There has been a thread on debian-devel (I can't find the Message-ID at > the moment) and the latest version of the next debian-installer for > Stretch switched the URL from httpredir.debian.org to deb.debian.org. > >> Also, will it work for Jessie or is it more for stretch or later? > > It will work a bit more efficient for Stretch+, but it also works as > intended for Wheezy and Jessie. > Thanks Sven. Is this still a beta service or mature enough to be recommended to debian users? Hopefully there is a formal announcement on this. As it stands, httpredir is mentioned in many places. For example https://www.debian.org/mirror/list https://www.debian.org/mirror/ http://httpredir.debian.org/ and is all over the wiki (there are 145 hits for httpredir site:wiki.debian.org in google). Now I feel stupid for filing https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845769 today morning asking httpredir to be discussed in the debian-handbook. :FacePalm: raju -- Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog
Re: Package configure problem during Installation.
On Sat 26 Nov 2016 at 11:51:19 -0500, kamaraju kusumanchi wrote: > On Sat, Nov 26, 2016 at 11:33 AM, Sven Hartge wrote: > > kamaraju kusumanchi wrote: > > > >> Where is it documented that httpredir is deprecated and that we should > >> use deb.debian.org's service going forward? Has it been announce > >> somewhere? > > > > There has been a thread on debian-devel (I can't find the Message-ID at > > the moment) and the latest version of the next debian-installer for > > Stretch switched the URL from httpredir.debian.org to deb.debian.org. > > > >> Also, will it work for Jessie or is it more for stretch or later? > > > > It will work a bit more efficient for Stretch+, but it also works as > > intended for Wheezy and Jessie. > > > > Thanks Sven. Is this still a beta service or mature enough to be > recommended to debian users? Hopefully there is a formal announcement > on this. As it stands, httpredir is mentioned in many places. For > example > > https://www.debian.org/mirror/list > https://www.debian.org/mirror/ > http://httpredir.debian.org/ > > and is all over the wiki (there are 145 hits for httpredir > site:wiki.debian.org in google). For the -devel thread: https://lists.debian.org/debian-devel/2016/07/msg00071.html For the -project thread: https://lists.debian.org/debian-project/2016/04/msg00012.html I think viewing deb.debian.org as beta is fair. Viewing the redirector as deprecated or about to be closed down in not correct. There is a diversity of views in both threads. > Now I feel stupid for filing > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845769 today morning > asking httpredir to be discussed in the debian-handbook. :FacePalm: Don't feel like that. You can either close the report with an explantion or add to it saying you have become aware of deb.debian.org and leaving any decision until things clarify may not be a bad idea. -- Brian.
Re: Jessie upgrade without systemd [was: Debian *not very good]
Joe writes: > Sorry, I may not have been clear, I was saying that reinstalling to > jump the 32/64 bit barrier has been the only significant upheaval in > the progress of my server since sarge, and that reinstallation was like > for like and therefore quite simple. > > If I have to reinstall the server with systemd from the beginning, > because the upgrade is too difficult, then restoring its current > functionality is likely to be significantly harder than the 32/64 bit > change was. I will be migrating configurations between different Debian > versions manually, at the same time as dealing with any systemd issues. > I hope very much to avoid the need for that. > It really is hard to say. The upgrade can be painless, but there are some services that have changed startup behaviour under systemd, and they can get into some painful issues when reconfiguring. Mostly because systemd handles dependencies differently from SysV init, and especially because it does not blithely ignore failed dependencies. You really are going to have to bite the bullet and build a test server. Mart -- "We will need a longer wall when the revolution comes." --- AJS, quoting an uncertain source.
Re: Debian *not very good
Hi there On 25/11/16 22:26, Latincom wrote: Is there a step by step guide or How to on line? I have 1 Wheezy without Systemd, and i would like to upgrade it. Thanks. You can do both an upgrade and an install from scratch without systemd; http://without-systemd.org/ http://without-systemd.org/wiki/index.php/How_to_remove_systemd_from_the_Netinst_CD http://without-systemd.org/wiki/index.php/How_to_remove_systemd_from_a_Debian_jessie/sid_installation http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html I had to make some other changes to get things to work though. Reading the release notes and keeping a close eye on the install process helps. I run XFCE on my desktop. I had to add myself to sudo to make things work properly. Regards, Rob
Re: Package configure problem during Installation.
Brian wrote: > On Sat 26 Nov 2016 at 11:51:19 -0500, kamaraju kusumanchi wrote: >> Thanks Sven. Is this still a beta service or mature enough to be >> recommended to debian users? Hopefully there is a formal announcement >> on this. As it stands, httpredir is mentioned in many places. For >> example >> >> https://www.debian.org/mirror/list >> https://www.debian.org/mirror/ >> http://httpredir.debian.org/ >> >> and is all over the wiki (there are 145 hits for httpredir >> site:wiki.debian.org in google). > For the -devel thread: > https://lists.debian.org/debian-devel/2016/07/msg00071.html I had a more recent thread in mind and I just found it. It was kind of buried inside the "When should we https our mirrors?" thread. From: https://lists.debian.org/debian-devel/2016/10/msg00362.html ,[ Peter Palfrader | > TL;DR: Would we now recommend deb.d.o over httpredir.d.o for | > production use e.g. in base images (including for Jessie)? | | Yes. ` And here https://lists.debian.org/debian-devel/2016/10/msg00490.html one of the maintainers behind deb.debian.org states the "experimental" phase has ended: ,[ Tollef Fog Heen | As of this morning, the bit about experimental was removed from the web | page. ` And here the reference for d-i (more precisely debootstrap) switching to deb.debian.org: https://lists.debian.org/debian-devel-announce/2016/11/msg6.html > I think viewing deb.debian.org as beta is fair. Viewing the redirector > as deprecated or about to be closed down in not correct. There is a > diversity of views in both threads. There are. But all more or less agree that httpredir.debian.org is unmaintained and just cruising along on auto-pilot. Grüße, Sven. -- Sigmentation fault. Core dumped.
Re: Debian *not very good
Hi there On 26/11/16 18:38, Rob van der Putten wrote: I run XFCE on my desktop. I had to add myself to sudo to make things work properly. And admin. admin is needed to get xconsole syslog to work. sudo to keep xdm logout from complaining. I use lightdm now though. I edited the cups config manually. The web interface breaks stuff. Regards, Rob
Re: Package configure problem during Installation.
On Sat 26 Nov 2016 at 18:40:38 +0100, Sven Hartge wrote: > Brian wrote: > > > For the -devel thread: > > > https://lists.debian.org/debian-devel/2016/07/msg00071.html > > I had a more recent thread in mind and I just found it. It was kind of > buried inside the "When should we https our mirrors?" thread. > > From: https://lists.debian.org/debian-devel/2016/10/msg00362.html > > ,[ Peter Palfrader > | > TL;DR: Would we now recommend deb.d.o over httpredir.d.o for > | > production use e.g. in base images (including for Jessie)? > | > | Yes. > ` > > And here https://lists.debian.org/debian-devel/2016/10/msg00490.html one > of the maintainers behind deb.debian.org states the "experimental" phase > has ended: > > ,[ Tollef Fog Heen > | As of this morning, the bit about experimental was removed from the web > | page. > ` > > And here the reference for d-i (more precisely debootstrap) switching to > deb.debian.org: > https://lists.debian.org/debian-devel-announce/2016/11/msg6.html > > > I think viewing deb.debian.org as beta is fair. Viewing the redirector > > as deprecated or about to be closed down in not correct. There is a > > diversity of views in both threads. > > There are. But all more or less agree that httpredir.debian.org is > unmaintained and just cruising along on auto-pilot. Very informative. Either would do for me in the UK, I think (assuming httpredir.debian.org stays around). Should we now be recommending deb.debian.org in user now? What do we get from it for our money? -- Brian.
Re: debian on lenovo carbon thinkpad 4th generation confirmation report
Good to know, thanks.
Re: Package configure problem during Installation.
On Sat, Nov 26, 2016 at 1:23 PM, Brian wrote: > On Sat 26 Nov 2016 at 18:40:38 +0100, Sven Hartge wrote: > >> Brian wrote: >> > I think viewing deb.debian.org as beta is fair. Viewing the redirector >> > as deprecated or about to be closed down in not correct. There is a >> > diversity of views in both threads. >> >> There are. But all more or less agree that httpredir.debian.org is >> unmaintained and just cruising along on auto-pilot. > > Very informative. Either would do for me in the UK, I think (assuming > httpredir.debian.org stays around). Should we now be recommending > deb.debian.org in user now? What do we get from it for our money? I went through the threads posted by you and Sven. I think you can recommend httpredir service untill there is a formal announcement of moving to deb.debian.org . The httpredir service is just not maintained but not deprecated. If it does not work as expected, bugs can be filed[1] with the following pseudo headers. Package: mirrors Severity: normal User: mirr...@packages.debian.org Usertags: httpredir [1] - https://lists.debian.org/debian-project/2016/04/msg00035.html -- Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog
Error message from GParted, means what?
I've been getting a strange error messages when looking at some 8 GB flash drives from different manufacturers purchased months apart. There is a title bar at top saying "Libparted Warning (as superuser). The body of the message box has: 1. an Exclamation point surrounded by orange and yellow triangle. 2. a message text saying "The driver descriptor says the physical block size is 2048 bytes, but Linux says it is 512 bytes. 3. There are two buttons present. One saying "Cancel" The other saying "Ignore" On today's drive: 1. I clicked "Cancel" then dismissed several boxes the gist of whose messages was that what I had started had not been done. 2. The entire drive is shown as "allocated". 3. Clicking on "New" yields message saying "No partition table found ..." 4.I attempt to create partition table and get the "block sector size" message. 5. Chose "ignore" 6. Apparently then able to create a single 8 GB partition. Any suggestions as to the problem's origin? I've no way to establish the history of the drive. Any reason to expect future problems? TIA
Re: Package configure problem during Installation.
On Sat 26 Nov 2016 at 16:44:42 -0500, kamaraju kusumanchi wrote: > On Sat, Nov 26, 2016 at 1:23 PM, Brian wrote: > > On Sat 26 Nov 2016 at 18:40:38 +0100, Sven Hartge wrote: > > > >> Brian wrote: > >> > I think viewing deb.debian.org as beta is fair. Viewing the redirector > >> > as deprecated or about to be closed down in not correct. There is a > >> > diversity of views in both threads. > >> > >> There are. But all more or less agree that httpredir.debian.org is > >> unmaintained and just cruising along on auto-pilot. > > > > Very informative. Either would do for me in the UK, I think (assuming > > httpredir.debian.org stays around). Should we now be recommending > > deb.debian.org in user now? What do we get from it for our money? > > I went through the threads posted by you and Sven. I think you can > recommend httpredir service untill there is a formal announcement of > moving to deb.debian.org . The httpredir service is just not > maintained but not deprecated. If it does not work as expected, bugs > can be filed[1] with the following pseudo headers. > > Package: mirrors > Severity: normal > User: mirr...@packages.debian.org > Usertags: httpredir Seems to be a reasonable approach. Maybe deb.debian.org is better for people with particular needs. I have to say I have generally done well by the redirector in terms of speed and reliability. The only thing I vaguely understand about the difference between the two is that httpredir.debian.org uses the traditional mirror network whereas deb.debian.org uses the Fastly CDN (Content Delivery Network) and there is some caching going on. Because Fastly has local peering arrangements mirror choices are supposed to be local (and hence faster). I've not noticed any difference in a few short tests. -- Brian. -- Brian.
stunnel or sibling?
Hello, The stunnel manual states "stunnel can be used to add SSL functionality to ... daemons ... ." I'm interested in a complimentary case. The remote server has SSL functionality. I want to add SSL for a local client. For example, a local elementary browser is not SSL capable but a connection to https is required. Can stunnel or something else do that? Thanks, ... Peter E. -- 123456789 123456789 123456789 123456789 123456789 123456789 123456789 Tel: +1 360 639 0202 Pender Is.: +1 250 629 3757 http://easthope.ca/Peter.html Bcc: peter at easthope. ca
