Re: Dependencies between components.
Hi, I have not found a mistake in your considerations about "sane" component inter-dependency. However, package dependencies are declared upon a package with a suitable version, whether this package can be set-up on a bespoke target system remains to be determined by APT when the package is installed or upgraded. Just consider for example some manually held packages - These might break your package install even if all the needed packages are downloadable (All the components needed are correctly configured in sources.list ). I hope this helps. I'd like to understand why you are asking this question, this might enable us to give you better-suited information. Ciao, Simon P.S.: I am sorry for first sending this to Tim directly - I should take extra care when using this weird web interface here. On Sat, 30 Mar 2024 at 18:12, Tim Woodall wrote: > > Is there a wiki or something else that lays out exactly what other > distributions and components each debian (distribution,component) tuple > is allowed to depend on? > > This is what I've concluded so far. > > I'm assuming transitive dependencies are allowed, e.g. > bookworm-updates-contrib can depend on bookworm-non-free so I've > considered the dependencies between distributions with the same > component and the dependencies between components of the same > distribution separately. > > > First considering the distribution dependencies. All of these are > always allowed between the same component. > > bookworm-proposed-updates : bookworm > bookworm-updates : bookworm > bookworm-backports-sloppy : bookworm-backports bookworm > bookworm-backports: bookworm > > I believe that updates is a subset of proposed-updates so dependency > on updates by proposed-updates is moot > > I'm unclear whether backports is allowed to depend on -updates but I > assume not as I've not seen anything saying that you need to enable > -updates if you enable -backports. I guess the backporter would have to > wait for the point release if they ever needed something only in > bookworm-updates (it's hard to imagine many cases where a -updates > package would be required for backporting so this is somewhat > theoretical - I think it's only if there's a security update involved) > > > Now considering the dependencies between components in the same > distribution: > > contrib : non-free non-free-firmware main > non-free : non-free-firmware main > non-free-firmware: main > > Some sources seem to say that non-free depends on contrib while others > say contrib depends on non-free. My understanding on contrib is that it > is for packages that cannot be in main because they depend on non-free > even though they're otherwise free. But I'm not sure if there's a two > way dependency here. > > I'm assuming that non-free-firmware cannot depend on non-free or contrib > - that would seem to defeat the goal of non-free-firmware - although I > could see a case where a firmware loader is in contrib while the > firmware itself is in non-free so I'm not sure exactly what is allowed > or expected here. >
Re: Old control sums for packages.
Hello KJ, there is the snapshot archive at https://snapshot.debian.org/ - You can get older Packages files from there. I don't know if you mean the links like `Packages.gz -> by-hash/SHA256/c039245acc063d9b42cade368a874bf5e0ee3025a7bb2634f3f3bc601f15bb89` or the actual contents of Packages: These by-hash links are in use since somewhen in 2017 for sid, but since you were talking about looking back a month or two, this should not be a problem. Please also note that there was a time when Packages had no SHA256 fields. Ciao, Simon On Mon, 1 Apr 2024 at 12:37, Kamil Jońca wrote: > > At http://deb.debian.org/debian/dists/sid/main/binary-amd64/ we can find > files with SHA256 sums of packages. Unfortunately they are only 2 weeks > old. Is this possible to have little older files? (For example month or > 2)? > KJ > > -- > http://stopstopnop.pl/stop_stopnop.pl_o_nas.html >
Re: Moderering av user forums...
On Fri 27 May 13:10, Rickard B Hansson wrote: > Den fre 27 maj 2022 kl 12:05 skrev Hund : > > > Nej nej nej. Som jag sa, det finns inget som talar för att det här är sant. > > På svenska heter det här direktivet "Upphovsrättsdirektivet". > > > Det finns olika uppgifter på vilken lag som skulle nödvändiggöra moderering > dygnet runt av kommentarsfältet på din hemsida eller onlineforumet för det > lilla linux-kommunen. > > Samtidigt med att jag ställde frågan här, skickade jag den till EU på > https://www.consilium.europa.eu/en/contact/general-enquiries/send-message. > Jag lär väl inte få svar förrän i nästa v. > Jag postar deras svar när det kommit. Really looking forward to the answer. Several german lawyers came to the conclusion that also small and non-profit sites are targeted by the law. I'm not a lawyer so I trust that they can interpret it correctly. Hälsningar, Simon > > // Med vänliga hälsningar rbh > > Rickard B Hansson > > > > > > > > On 27 May 2022 11:44:38 CEST, Rickard B Hansson > > wrote: > > >Tack för snabbt och fylligt svar. > > >Följdfråga: > > >Är verkligen ett onlineforum "An online content-sharing service provider"? > > >Är verkligen ett supportmöte för linux att anse som "An online > > >content-sharing service provider"? > > >Om nu servren står i Tyskland, är det alltså tysk nationell tillämpning > > som > > >gäller? > > > > > >Hur blir det med publik åtkomst till denna lista, på > > >https://lists.debian.org/debian-user-swedish and all other debian lists > > >under lists.debian.org. De måste väl falla under smma bestämelse? Kan ens > > >mejlinglista vara kvar? > > > > > >Skall man kanske flytta server utanför EU? > > > > Nej nej nej. Som jag sa, det finns inget som talar för att det här är sant. > > På svenska heter det här direktivet "Upphovsrättsdirektivet". > > > > > Dess syfte är att harmonisera och modernisera bestämmelser om digital > > upphovsrätt inom Europeiska unionen,[4] att minska intäktsgapet mellan > > monopolliknande internetföretag och europeiska innehållsproducenter samt > > att främja en digital inre marknad inom EU. > > >[...] > > >Såväl små och nystartade som privata och icke-kommersiella > > webbplattformar, exempelvis Wikipedia, undantas från kraven i artikel > > 17,[9] men inte i artikel 15. > > > > Källa: https://sv.wikipedia.org/wiki/Upphovsr%C3%A4ttsdirektivet > > > > Många läser idag bara rubriken på artiklar, för att sedan dra egna > > ofullständiga slutsatser, som sedan ligger till grund för osanna rykten, > > eller "fake news" som det populärt kallas idag. Detta kan tyvärr bli > > väldigt fel ibland. Ni har inget att oroa er för. > > > > -- > > Hund > > > > signature.asc Description: PGP signature
Re: Moderering av user forums...
On Fri 27 May 10:24, Rickard B Hansson wrote: > Den fre 27 maj 2022 kl 07:22 skrev Hund : > > > Det låter befängt. Varför skulle ett forum behöva ha en ansvarig > > närvarande dygnet runt, när ingen annan hemsida behöver det? > > > Det har har ju förts diskussion om skärpning av moderering av de > företagsstyrda sociala medierna. Fake News, hatbrott, kränkningar, > länkningar till virussiter osv, som företagen tjänar multum på och inte > städar undan... Men, att Facebook måste ha några heltidsanställda > moderatorer att övervaka miljoner inlägg. innebär ju ett litet ingrepp... > > Om samma krav skall ställas på små nätverk med något hundratal inlägg per > dag, verkar ju befängt som du säger. Men det gör det, tyvärr. EU direktivet gäller för allt på nätet, no matter om det är små eller inte. > > Den gamla svenska "BBS-lagen", ställde ju också krav på ägaren av ett forum > att *inom viss tid* städa undan olagliga postningar. > > En hemsida utan kommentarsfält, har ju inget behov av modererering... > Tillåter man kommentarer, har du i princip ett nätforum. Precis. Så aldrig tillat kommentarer på din sida. :) Simon. signature.asc Description: PGP signature
Re: Moderering av user forums...
cked from the automatic content filter, so you rather block more and prohibit freedom of speech, where there is no fine, then block less and risk fines for violating copyright. Sadly, the german politician and member of the EP Axel Voss, who was the driving force behind the directive, did not care at all what the experts sad, and commented on the huge protests and demonstrations we had in germany that "they are just some teens who were fed some wrong narrative from big companies who dont want to be held accountable". Believe me, I am really not proud of our exports to the EP. This directive was passed in 2019, and came into effect as national law 2 years later, whereas each member of the EU had to draft their own law. So the actual swedish implementation might be a little different from the implementation in other EU contries, which is why i leave it as a task for the reader to look up their actual binding version of this directive and figure out what is allowed and what it not in their country :) Med hälsningar från Tyskland Simon signature.asc Description: PGP signature
Re: AMD EPYC throttled to 400 mhz
Am 17.01.22 um 22:53 schrieb Mike Kupfer: > Simon Kainz wrote: > >> #Governor: >> root@node3:~# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor >> schedutil > > Maybe try a different governor? I had a different problem (CPU running > too hot) after upgrading to Bullseye, and the problem went away after I > switched to the ondemand governor. Thanks for the tip. Well, i now changed the governor to "performance", as my hosts are all compute nodes on a HPC system, so no real reason for cpu throttling anyway. Maybe this helps, we'll see. Regards, Simon > > mike >
Re: AMD EPYC throttled to 400 mhz
Am 17.01.22 um 11:36 schrieb Alexander V. Makartsev: > On 17.01.2022 14:41, Simon Kainz wrote: >> Hello, >> >> we are experiencing spontaneous CPU speed throttlings. >> >> System is a Lenovo ThinkSystem SR645 with 2 >> AMD EPYC 7452 32-Core Processor, running >> >> Linux node3 5.10.0-10-amd64 #1 SMP Debian 5.10.84-1 (2021-12-08) x86_64 >> GNU/Linux >> >> After some time (hours, day, weeks even) the system suddenly gets >> throttled to 400 Mhz (see below) >> >> HW Vendor replies with "Debian ist not on the supported OS" list, so we >> are currently fighting on our own. >> >> Does someone else experince the same/similar issue? It seems to my as >> some kind of thermal throttling, but kernel does not log thottling >> events. Maybe some Debian-specific kernel setting, that influences CPU >> throttling.. >> > Are you sure it is not due to a "power save" feature for a system under > low load? Good point, but no, because the system is under heavy load all the time, not idling. After throttling down to 400 mhz, system also stays at this speed. Only system reboot mitigates the issue. > What CPU driver and Governor currently in use? > https://www.kernel.org/doc/html/latest/admin-guide/pm/working-state.html #CPU driver: root@node3:~# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver acpi-cpufreq #Governor: root@node3:~# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor schedutil I did not set/change governor/driver settings, this is a stock debian kernel. > > Is the CPU temperature ok? > Since this is a server platform, it could be due to wrong installation > of FANs/Radiators/Air ducts and shields/etc.> Check it with "sensors". yes, good point, but CPU/temp/fans are all ok. BMC, ipmi and management interface all show no issues whatsovers. Regards, Simon
AMD EPYC throttled to 400 mhz
Hello, we are experiencing spontaneous CPU speed throttlings. System is a Lenovo ThinkSystem SR645 with 2 AMD EPYC 7452 32-Core Processor, running Linux node3 5.10.0-10-amd64 #1 SMP Debian 5.10.84-1 (2021-12-08) x86_64 GNU/Linux After some time (hours, day, weeks even) the system suddenly gets throttled to 400 Mhz (see below) HW Vendor replies with "Debian ist not on the supported OS" list, so we are currently fighting on our own. Does someone else experince the same/similar issue? It seems to my as some kind of thermal throttling, but kernel does not log thottling events. Maybe some Debian-specific kernel setting, that influences CPU throttling.. root@node3:~# lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 48 bits physical, 48 bits virtual CPU(s): 64 On-line CPU(s) list: 0-63 Thread(s) per core: 1 Core(s) per socket: 32 Socket(s): 2 NUMA node(s):2 Vendor ID: AuthenticAMD CPU family: 23 Model: 49 Model name: AMD EPYC 7452 32-Core Processor Stepping:0 Frequency boost: enabled CPU MHz: 399.256 CPU max MHz: 3364.3550 CPU min MHz: 1500. BogoMIPS:4691.25 Virtualization: AMD-V L1d cache: 2 MiB L1i cache: 2 MiB L2 cache:32 MiB L3 cache:256 MiB NUMA node0 CPU(s): 0-31 NUMA node1 CPU(s): 32-63 Vulnerability Itlb multihit: Not affected Vulnerability L1tf: Not affected Vulnerability Mds: Not affected Vulnerability Meltdown: Not affected Vulnerability Spec store bypass: Vulnerable Vulnerability Spectre v1:Vulnerable: __user pointer sanitization and usercopy barriers only; no swapgs barriers Vulnerability Spectre v2:Vulnerable, IBPB: disabled, STIBP: disabled Vulnerability Srbds: Not affected Vulnerability Tsx async abort: Not affected Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mm xext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_leg acy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw_pstate ssbd mba ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local c lzero irperf xsaveerptr rdpru wbnoinvd amd_ppin arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif umip rdpid overflow_recov succor smca root@node3:~# cpupower monitor | Mperf PKG|CORE| CPU| C0 | Cx | Freq 0| 0| 0| 99.52| 0.48| 399 0| 1| 1| 99.52| 0.48| 399 0| 2| 2| 99.52| 0.48| 399 0| 3| 3| 99.52| 0.48| 399 0| 4| 4| 99.51| 0.49| 399 0| 5| 5| 99.51| 0.49| 399 0| 6| 6| 99.50| 0.50| 399 0| 7| 7| 99.50| 0.50| 399 0| 8| 8| 99.49| 0.51| 399 0| 9| 9| 99.49| 0.51| 399 0| 10| 10| 99.48| 0.52| 399 0| 11| 11| 99.48| 0.52| 399 0| 12| 12| 99.47| 0.53| 399 0| 13| 13| 99.46| 0.54| 399 0| 14| 14| 99.46| 0.54| 399 0| 15| 15| 99.45| 0.55| 399 0| 16| 16| 99.45| 0.55| 399 0| 17| 17| 99.45| 0.55| 399 0| 18| 18| 99.44| 0.56| 399 . Thanks, Simon
Re: Opensource photo user group
On Mi, 26 mai 21, 05:08:52, Polyna-Maude Racicot-Summerside wrote: > > I am planning to open a user group, with forums, place to share picture > and tips, video chat server (Jitsi or something alike) and more. > > So this is a call to anyone interested. > > I am not limiting to photograph using Debian but caring for people using > opensource software at large, with preferred operating system of Linux. Sounds like a very nice idea :) As it happens such a community of users and creators of open source photography software already exists at https://pixls.us. Many projects use the forum (https://discuss.pixls.us/) as their official place for support. There's a section to showcase your works (https://discuss.pixls.us/c/showcase/11) and one to share works for everyone to try their hands on with processing, thus learn from each other (https://discuss.pixls.us/tag/play_raw). And since recently there's irregular videoconference meetups. The page itself features tutorials and news around the FLOSS photography ecosystem. I can very much recommend anyone interested in photography (and also video) to have a look.
Linux kernel 5.10 (or 5.4) with Debian Buster
I'm currently using Debian Buster on an embedded system (ARM) and am currently using an older 4.4 kernel. I need to upgrade to later version to support a new Ethernet Phy device (KSZ9131). Kernel 4.19 is the default for Buster, but it doesn't seem to have the KSZ9131 support. I have cherry-picked some newer KSZ9131 commits and hope that it works. Just wondering, is it safe to use kernel 5.4 or 5.10 with Debian Buster packages? My preference would be 5.10 (over 5.4), mainly because that is what Unstable/Testing is currently using. Thanks, Brendan.
Wifi won't connect in debian
Hello, I have a Lenovo Thinkpad which I used to run Windows on. A few days ago I installed Debian 10.6.0 (first as dual-boot to make sure I could transfer everything, later deleting the Windows partition). I had to install non-free firmware to get wifi working during install, but I found the required drivers on Intel's website and everything went smoothly from there. Fast forward three days problem free and when I booted up this morning I had lost some of the graphical features of my desktop environment MATE (the top/bottom panels, my chosen theme, and a number of keyboard shortcuts no longer worked) and I couldn't connect to the internet. I don't know if these problems are related, but I can't fix the desktop environment without internet access so it's somewhat moot. Clarifications on the internet problems: It's not my provider, that's been working fine all day on other devices It's not a hardware fault; while I was trying out stuff to fix it I tried using my boot-repair live usb to see if the hard drive was the problem, and while in that mode connecting to the internet was easy and worked fine. I'm not sure what difference using ethernet would make as I can't figure out how to connect using that either but I do have access to an ethernet port if needed. I have tried a number of suggested solutions online, but none have worked and I couldn't try a lot of them because they required packages I didn't have and couldn't install offline. I need wifi access back fairly promptly as I am a university student studying remotely, so any help is thoroughly appreciated. Thanks, Simon
Re: Re: Issue with OpenVPN inside a LXC container: Failed at step NAMESPACE spawning /usr/sbin/openvpn: Permission denied
Thanks a ton! I'm running this container on my private network behind a NAT, so I'm not too worried about disabling apparmor. I ended up just giving as loose of a configuration I could and it did the trick. lxc.apparmor.profile = unconfined lxc.apparmor.allow_nesting = 1 lxc.apparmor.allow_incomplete = 1 The first line alone did not seem to do the trick, so I added 2 and 3 and it worked. Good enough for me. Thanks again!
Issue with OpenVPN inside a LXC container: Failed at step NAMESPACE spawning /usr/sbin/openvpn: Permission denied
I have a LXC container which is connected to a remote VPN using OpenVPN. After upgrading to buster, the VPN does not start anymore. I'm using Debian buster on my host OS and Debian buster on the guest OS. Both were updated from stretch. Aside from OpenVPN there's only deluged and deluge-web that are installed. This is the journalctl log for the openvpn service: root@dl:/# journalctl -u openvpn-client@pia.service -- Logs begin at Tue 2019-07-16 20:32:30 EDT, end at Tue 2019-07-16 22:31:19 EDT. -- Jul 16 20:32:30 dl systemd[1]: Starting OpenVPN tunnel for pia... Jul 16 20:32:30 dl systemd[70]: openvpn-client@pia.service: Failed to set up mount namespacing: Permission denied Jul 16 20:32:30 dl systemd[70]: openvpn-client@pia.service: Failed at step NAMESPACE spawning /usr/sbin/openvpn: Permission denied Jul 16 20:32:30 dl systemd[1]: openvpn-client@pia.service: Main process exited, code=exited, status=226/NAMESPACE Jul 16 20:32:30 dl systemd[1]: openvpn-client@pia.service: Failed with result 'exit-code'. Jul 16 20:32:30 dl systemd[1]: Failed to start OpenVPN tunnel for pia. I've searched online but I haven't found anything relevant to my situation. Anything to help me figure this one out will be greatly appreciated. Thanks!
Re: OpenGL forwarding via ssh session: works on jessie, does not work on stretch
I think i found the culprit: I use the debian apt repo for machinekit and the rt kernel: deb [arch=armhf] http://repos.rcn-ee.com/debian/ stretch main This repo installs libGL.so.1.0.0 instead of libGL.so.1.2.0. I forced to use the default debian apt source repo and purged all libgl stuff from the rcnee repo. And now i get: > glxinfo|head name of display: localhost:10.0 display: localhost:10 screen: 0 direct rendering: No (LIBGL_ALWAYS_INDIRECT set) server glx vendor string: NVIDIA Corporation server glx version string: 1.4 perfect! So it seems like the libGL package is somehow messed up or not up to date on the repo server I use because of the machinekit stuff. I contacted the owner of the repo and I will wait for his reply.
Re: OpenGL forwarding via ssh session: works on jessie, does not work on stretch
Am Sonntag, 2. Juni 2019 15:00:05 UTC+2 schrieb Simon S: > Hi, > > I have a weird problem with opengl forwarding via ssh. > I am running debian jessie on my BeagleBone Black (armhf) that I use for my > CNC machine by running machinekit. > Everything works as expected, I even got indirect opengl rendering working > when I connect to the BBB using windows. > > Now I tried to upgrade my setup using a more recent stretch based image. > I am not able to use opengl forwarding on stretch. > > The following test setup: > (A) linux machine running ubuntu (Nvidia GPU) > (B) BBB running jessie > (C) BBB running stretch > > I connect from (A) -> (*) by ssh -X x@host > > When I connect from (A) to (B): > > export LIBGL_ALWAYS_INDIRECT=1; glxinfo|head > name of display: localhost:10.0 > display: localhost:10 screen: 0 > direct rendering: No (LIBGL_ALWAYS_INDIRECT set) > server glx vendor string: NVIDIA Corporation > server glx version string: 1.4 > server glx extensions: > > When I connect from (A) to (C): > > export LIBGL_ALWAYS_INDIRECT=1; glxinfo|head > Error: couldn't find RGB GLX visual or fbconfig > name of display: localhost:10.0 > > > Did something change from jessie -> stretch concerning x permissions? > > Running plain x apps like xterm works in all cases. > > I installed lxde on (c) and glxinfo/glxgears runs fine under lxde on the BBB. > > Any hints? > > Simon
Re: OpenGL forwarding via ssh session: works on jessie, does not work on stretch
Hi! Thanks for testing it out! I was wondering if it had to do with an user beeing logged in to lxde. I think autologin might be enabled on the jessie system. Unfortunately this does not help. Still the same problem on stretch. I have some additional info. Without exporting the inderect rendering flag it does not work on ssh either: > glxinfo|head libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast Error: couldn't find RGB GLX visual or fbconfig name of display: localhost:10.0 ... With the export still the same issue: >export LIBGL_ALWAYS_INDIRECT=1; glxinfo|head Error: couldn't find RGB GLX visual or fbconfig name of display: localhost:10.0 And there are no X error messages in the log either. I was wondering if it has to do something with the gl libs on the armhf build. Does your stretch based image have /usr/lib/*ARCH*/libGL.so.1.0.0 or /usr/lib/*ARCH*/libGL.so.1.2.0 installed? On jessie i havce 1.2.0, on stretch 1.0.0. The 1.2.0 seems to be in a "transitional package" that does not install anything useful?! Not sure if this is meaningful as glxinfo runs under lxde just fine. Adding iglx to the config on the BBB allows me to run glxinfo with DISPLAY=:0 (otehrwise I get X Error of failed request: GLXBadContext). But it did not change anything for running gl stuff on a remote screen. I also think the xserver on the BBB should not be necessary for running stuff via ssh -X on a remote screen. I think I killed the server on jessie once and ssh -X still worked fine. My ubuntu box is running with iglx. In addition running indirect GL stuff works for the jessie box on windows too. Again it does not work on stretch. Simon
OpenGL forwarding via ssh session: works on jessie, does not work on stretch
Hi, I have a weird problem with opengl forwarding via ssh. I am running debian jessie on my BeagleBone Black (armhf) that I use for my CNC machine by running machinekit. Everything works as expected, I even got indirect opengl rendering working when I connect to the BBB using windows. Now I tried to upgrade my setup using a more recent stretch based image. I am not able to use opengl forwarding on stretch. The following test setup: (A) linux machine running ubuntu (Nvidia GPU) (B) BBB running jessie (C) BBB running stretch I connect from (A) -> (*) by ssh -X x@host When I connect from (A) to (B): > export LIBGL_ALWAYS_INDIRECT=1; glxinfo|head name of display: localhost:10.0 display: localhost:10 screen: 0 direct rendering: No (LIBGL_ALWAYS_INDIRECT set) server glx vendor string: NVIDIA Corporation server glx version string: 1.4 server glx extensions: When I connect from (A) to (C): > export LIBGL_ALWAYS_INDIRECT=1; glxinfo|head Error: couldn't find RGB GLX visual or fbconfig name of display: localhost:10.0 Did something change from jessie -> stretch concerning x permissions? Running plain x apps like xterm works in all cases. I installed lxde on (c) and glxinfo/glxgears runs fine under lxde on the BBB. Any hints? Simon
Live boot
Goedemorgen mensen, Ik ben sinds een paar jaar een linux gebruiker naar grote tevredenheid hem ook voor kennisen laptop voor zien van verschilde distro. Nu heb ik een laptop (asus n90sc met intel pentium 4400) kan niet live booten heb geprobeert lubuntu 18.04 lts debian ldxe met non free en linux mint. Enigste wat wel werkt was lubuntu 13.04 met acpi uit. Puppy xenial start ook gewoon op. Dus hardware lijkt te werken maar iets in de kernel gaat er mis bij het opstraten loopt hij vast. Iemand een idee hoe ik stap voor stap kan zien wat wel en niet goed gaat? Alvast bedankt voor jullie input. groet Simon
Questions about VRF function in /etc/network/interfaces
Hi all, I'm working on SONiC project management vrf function under debian with kernel 4.3. This is my OS: > # uname -a > Linux dut211 4.9.0-7-amd64 #1 SMP Debian 4.9.110-3+deb9u2 (2015-12-19) > x86_64 GNU/Linux This is SONiC project management vrf function: > https://www.youtube.com/watch?v=uAHmZKEdqDE=youtu.be Now I have to rewrite /etc/network/interfaces to implement this function, but I got errors, so I want to know if there is demo about how to define VRF interface and implement VRF function in /etc/network/interfaces. As I follow your man file, I don't know how to do, and gots errors. This is my try on this feature, rewrite /etc/network/interfaces like this iface eth0 inet static > address 172.18.8.211 > netmask 255.255.255.0 > ## management network policy routing rules > # management port up rules > up ip -4 link add mgmtvrf type vrf table 10 > up ip -4 link set dev mgmtvrf up > up ip -4 link set dev eth0 master mgmtvrf > up ip -4 route add default via 172.18.8.1 dev eth0 table 10 > up ip -4 route add 172.18.8.0/24 dev eth0 table 10 > up ip -4 rule add from 172.18.8.211/32 table 10 > post-up sysctl -w net.ipv4.tcp_l3mdev_accept=1 > # management port down rules > down ip -4 route delete default via 172.18.8.1 dev eth0 table 10 > down ip -4 route delete 172.18.8.0/24 dev eth0 table 10 > down ip -4 rule delete from 172.18.8.211/32 table 10 > down ip -4 link set dev eth0 nomaster This is errors I got Dec 29 02:38:48 dut211 ifup[8690]: RTNETLINK answers: File exists > Dec 29 02:38:48 dut211 ifup[8690]: ifup: failed to bring up eth0 > Dec 29 02:38:48 dut211 systemd[1]: networking.service: Main process > exited, code=exited, status=1/FAILURE > Dec 29 02:38:48 dut211 systemd[1]: Failed to start Raise network > interfaces. > -- Subject: Unit networking.service has failed > -- Defined-By: systemd > -- Support: https://www.debian.org/support > -- > -- Unit networking.service has failed. > -- > -- The result is failed. > Dec 29 02:38:48 dut211 systemd[1]: networking.service: Unit entered failed > state. > Dec 29 02:38:48 dut211 systemd[1]: networking.service: Failed with result > 'exit-code’. Thank you. Simon Jones
Re: Why does Debian allow all incoming traffic by default
Am Samstag, den 22.09.2018, 23:58 +0200 schrieb Pascal Hambourg: > Le 22/09/2018 à 23:35, Simon Kengelbacher a écrit : > > Am Samstag, den 22.09.2018, 22:36 +0200 schrieb to...@tuxteam.de: > > > On Sat, Sep 22, 2018 at 04:15:42PM -0400, Gene Heskett wrote: > > > > > > > They have over the last two "upgrades" from wheezy to jessie > > > > and on > > > > to > > > > stretch, totally disabled any attempts to forward x to another > > > > machine, > > > > > > Just a tip: there's "ssh -X" or better "ssh -Y" for that. Perhaps > > > it > > > suits your needs... > > > > In this case I would prefer sshfs as "ssh -X" can be somewhat laggy > > when you don't have a fast connection. > > sshfs to run a remote shell and X programs ? > no, to edit the file on your local environment
Re: Why does Debian allow all incoming traffic by default
Am Samstag, den 22.09.2018, 22:36 +0200 schrieb to...@tuxteam.de: > On Sat, Sep 22, 2018 at 04:15:42PM -0400, Gene Heskett wrote: > > [...] > > > They have over the last two "upgrades" from wheezy to jessie and on > > to > > stretch, totally disabled any attempts to forward x to another > > machine, > > Just a tip: there's "ssh -X" or better "ssh -Y" for that. Perhaps it > suits your needs... > > Cheers > -- tomás In this case I would prefer sshfs as "ssh -X" can be somewhat laggy when you don't have a fast connection.
Re: Hibernate not working !
On Fri, 08 Jun 2018 at 04:03:42 +0100, Aaron Gray wrote: > I have noticed a while back the hibernate option disappearing from desktop > options and have found this does not work. > > Is there any reason for this not working on Debian Stretch or Debian Jessie > or even other Linii I have tried ? Hibernation (suspend-to-disk) works on some hardware, but whether it works is very dependent on the combination of hardware, drivers and kernel, and when it fails it leads to a bad user experience. Desktop environment developers do not want to offer a feature by default while knowing that it is unreliable (and not feasible for them to fix). If you're using GNOME and your particular hardware can hibernate and resume successfully, you might find https://extensions.gnome.org/extension/755/hibernate-status-button/ useful. smcv
Re: Inexplicable memory usage after move to Debian9
I've been out for a bit, I'll bundle multiple replies in a single mail. Before I start: thank you to everybody taking the time to respond in this thread :) How are you determining what you call "consumed memory"? Memory which isn't available to the system. So "used" minus "buffers/cache" Keep in mind that the kernel will by default use almost all free memory (not actually used by processes and libraries) as cache space, because it makes no sense to leave memory just laying around. However, once it's really needed, the caches will be dropped. Thus "free" memory is usually reported as low. Compare with "available" memory as reported by free. Yup. I'm aware of this and it's not the issue I'm trying to solve. Disk cache is good. The free's 'available' value is computed without taking "SUnreclaim" (unreclaimable kernel slabs) value from /proc/meminfo. The difference is not that great, usually, but for NFS server it can lead to funny things like "I have plenty of free swap and OOM killer was invoked, despite 'available' telling me there's plenty of free RAM". Can happen with Java too, as OP e-mail shows us. Unfortunately the system I was currently seeing the issues on has apparently been rebooted by the client, so right now I don't have a system to verify, but it sounds like this is what I'm on about. I'll verify as soon as another system with issues pops up. Happened to me with kernel 4.9.0-5, continued with kernel 4.9.0-6, seems to be solved by upgrading to backported kernel version 4.14. Hm. This could bite me in the ass. Thanks for your feedback. The last line from smem sticks out with high usage figures: 566 jetty /usr/lib/jvm/java-8-openjdk 493896 958124 958381 959804 Java is actually consuming the expected amount of RAM for the settings we start it with. Also, the hight memory usage presists after shutting down Jetty (and pretty much any other service), which is why I was hinting at possible kernel issues (not much else was running).
Re: Inexplicable memory usage after move to Debian9
I'm not sure that a ratio of 512MB swap to 1.8GB RAM really proves anything. If the swap space matched RAM in size and still filled up, I think that would be more definitive. The bottom line for me is that I when I shut down everything I install and manage on the system, it's still conuming about half a gig more than a system running the exact same base image right after use, without the extra memory being accounted for by monitoring tools. Enabling swap just helped me realize that the allocated memory isn't actively used, otherwise the system would be swapping it in/out more than it is. These machines (thousands) have been running on without swap on Debian 7 for a *long* time without issues. I wasn't intending on activating swap now either. It's just a debugging step. What I'm actually looking for is a way to trace where to which process that mistery half-a-gig is allocated. As I said: I can't find a memory list which acocunts for everything. This is what makes me think of a memory leak somewhere. I just want to debug this. I'm not trying to imply that I was solving anything by allocating RAM. Also note this comment at the top of the stackexchange article: "UPDATE: I'm no longer having this problem on 4.9.* Not sure when it was fixed." I know. Just wanted to indicate that I had looked at slab allocation issues, but it doesn't seem to be related Thanks Simon
Inexplicable memory usage after move to Debian9
Hi Recently I've started moving a fleet of Debian 7, 32-bit machines over to Debian 9, 64-bit. This migration is done by creating a fresh Debian 9 image with the necessary services, moving over user data (some wars and the content of /home) and rebooting into the new OS. Relevant services (ones we manage and use) are: - Jetty- Puppet - SSH - AutoSSH - NewRelic Infrastructure Through Puppet, we enforce system configuration is pretty much identical, save for stuff like host names and SSH keys. Now, we notice that on some systems, the RAM usage is way higher than expected, to the point where system memory is exhausted and processes (are) terminate(d). Investigation into what is causing this, leaves me at a dead end. I can't figure out where the memory is being consumed. Even after quitting all services we manage (leaving a "clean" installation), RAM usage on the system hovers just over 600MB, half a gig over what the same exact image consumes just after boot. The only fix I found so far is to reboot the system. The systems have ~1.8GB of system memory available. We don't use swap. Enabling swap gives the system some breathing room. On one system I enabled a swap volume of 512MB, which the kernel fills up and leaves filled up indefinitely. This points me to unused memory being allocated by mistake. A memory leak in the kernel, maybe? Below I've posted the output of some of the things I checked (with all services online). I also searched the internet and reached a topic about slab allocation (1). However, that didn't seem to solve anything. Can anyone here point me to some more stuff I can check out or try to debug this? Thanks! Simon root@mysystem:~# uname -a Linux mysystem 4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u2 (2018-02-21) x86_64 GNU/Linux root@mysystem:~# free -m total used free shared buff/cache available Mem: 1831 1091 238 16 501 520 Swap: 511 511 0 root@mysystem:~# vmstat 1 procs ---memory-- ---swap-- -io -system-- --cpu- r b swpd free buff cache si so bi bo in cs us sy id wa st 2 0 524268 244480 46044 467248 1 2 2137 36 97 35 9 3 85 3 0 0 0 524268 244092 46052 467244 0 0 0 16 1125 2406 3 3 94 1 0 0 0 524268 244092 46060 467284 0 0 4 208 1230 3906 4 3 93 0 0 0 0 524268 244084 46068 467256 0 0 0 32 1003 1990 1 2 97 0 0 0 0 524268 244180 46068 467256 0 0 0 0 1099 2121 4 1 95 0 0 0 0 524268 244204 46076 467272 0 0 0 20 1000 1978 1 2 97 1 0 0 0 524268 244080 46076 467272 0 0 0 0 1135 2315 2 2 96 0 0 0 0 524268 244080 46084 467264 0 0 0 16 1079 2103 1 3 96 1 0 0 0 524268 244080 46092 467272 0 0 0 56 1002 1973 2 2 96 0 0 1 0 524268 244080 46100 467264 0 0 0 16 997 1979 1 2 97 1 0 0 0 524268 244144 46100 467268 0 0 0 0 988 1957 1 2 97 0 0 0 1 524268 244228 46108 467260 0 0 0 980 1292 2700 4 5 81 9 0 root@mysystem:~# smem PID User Command Swap USS PSS RSS 528 root /sbin/agetty -f /etc/issue. 148 4 4 8 554 myuser /usr/lib/autossh/autossh -o 80 24 40 184 220 root /lib/systemd/systemd-udevd 552 108 140 688 10665 root /usr/lib/autossh/autossh -o 0 104 143 648 432 root /usr/sbin/cron -f 164 120 147 500 434 root /usr/sbin/irqbalance --fore 252 156 172 508 12042 mail /usr/sbin/nullmailer-send - 120 144 219 1228 382 systemd-timesync /lib/systemd/systemd-timesy 456 152 301 1060 439 messagebus /usr/bin/dbus-daemon --syst 272 280 348 1116 430 root /lib/systemd/systemd-logind 380 192 448 1224 557 myuser /usr/bin/ssh -o StrictHostK 564 360 515 1472 216 root /sbin/lvmetad -f 188 484 517 1028 10668 root /usr/bin/ssh -o StrictHostK 0 736 825 1112 14225 ntp /usr/sbin/ntpd -p /var/run/ 0 808 849 1404 435 root /usr/sbin/rsyslogd -n 716 896 980 2036 11612 root /usr/sbin/sshd -D 0 856 991 1560 500 root /sbin/dhclient -4 -v -pf /r 840 928 1010 2068 1330 root sudo -i 0 920 1375 3548 1234 myuser -bash 0 600 1407 3684 1331 root -bash 0 640 1447 3712 1233 myuser sshd: myuser@pts/0 0 300 1697 4568 1 root /sbin/init 524 1568 1935 3524 1227 root sshd: posios [priv] 0 1372 2984 6380 193 root /lib/systemd/systemd-journa 312 4304 4521 5828 8885 root /usr/bin/python /usr/bin/sm 0 9100 9452 11292 14574 root /usr/bin/newrelic-infra 1440 17348 17378 17828 520 root /opt/puppetlabs/puppet/bin/ 20636 40140 40168 40592 566 jetty /usr/lib/jvm/java-8-openjdk 493896 958124 958381 959804 [1] https://unix.stackexchange.com/questions/244735/why-are-slab-objects-not-reclaimed-automatically
Re[2]: 9.2 DNS Confusion
Hi Pascal, Surprised, no not really. Broken DNS, yes as I say not assigning blame anywhere but yes it's the Juniper and given I can do squat about that lets move on to another solution :) Gai.conf, didn't suggest this did disable IPv6 I just replied to a suggestion by another. I've used various ways to disable IPv6 the GRUB amendment you mention is one, resolver issue appeared to still exist for me but I will check. Forcing IPv4 is all well and good but not a workable solution on an app by app basis, docker is being a pita for example. I'm chasing the juniper bunch for a solution in-case there's a magic button, but I doubt it. Centos 7 does not exhibit this behaviour so it does seem to be Debian specific Cheers for the respone Simon -- Original Message -- From: "Pascal Hambourg" <pas...@plouf.fr.eu.org> To: debian-user@lists.debian.org Sent: 26/11/2017 15:07:52 Subject: Re: 9.2 DNS Confusion Le 26/11/2017 à 14:23, Simon Slaytor a écrit : Today I Wiresharked the network and I can what's happening now. When I don a plain ping www.apple.com the resolver is sending 2x requests to the FW's DNS proxy the first for an IPv4 A record and the 2nd for an IPv6 record! You sound surprised. That was obvious though. Note : In previous versions up to Jessie, ping was IPv4 only and there was a separate ping6 executable for IPv6. Since Stretch, ping and ping6 are now the same executable which is able to do both IPv4 and IPv6. When invoked as ping4 or with -4, it does IPv4 only. By default, it behaves as most IPv6-capable programs do, asking the resolver for IPv4 and IPv6 addresses of the target name. When I specify the -4 flag in PING the resolver sends only 1x request which is for the IPv4 A record. It would seem that the DNS Proxy on my SSG's (SSG140 ScOS 6.3r24) doesn't like the request (rightly so I guess as IPv6 is not enabled anywhere!) and returns nothing at all when this request is made. Not rightly. Your DNS proxy is broken. The ability to properly process DNS queries for records has nothing to do with IPv6 connectivity. So my question changes to 'How do I get the resolver to NOT send the request, simply disabling IPv6 on the box does not prevent this behaviour?' How did you disable IPv6 on the box ? I did so by appending ipv6.disable=1 to the kernel command line, and it actually prevented the resolver to send DNS queries for records. This setting totally disables IPv6 features in the kernel and is not recommended because it can break some programs which rely on the kernel IPv6 features, even though IPv6 connectivity is not available. The recommended setting is ipv6.disable_ipv6=1 which disable IPv6 on network interfaces but still enables IPv6 features in the kernel. However, according to my tests, it does not prevent the resolver to send DNS queries for records. I have not tested it because I do not have a broken DNS server, but there are a couple of options in /etc/resolv.conf which may help workaround your DNS proxy brokenness. See man resolv.conf about single-request and single-request-reopen. Or you can just use ping -4 or ping4 as you know you don't have any IPv6 connectivity. From: "Dan Ritter" <d...@randomstring.org> To: "Simon Slaytor" <si...@slaytor.com> Cc: debian-user@lists.debian.org Sent: 17/11/2017 16:39:57 Subject: Re: 9.2 DNS Confusion You can effectively disable IPv6 on a Debian box by editing /etc/gai.conf and uncommenting the line: precedence :::0:0/96 100 No, this is far from disabling IPv6. It just gives precedence to IPv4 addresses over IPv6 addresses. But the resolver still does record lookups and IPv6 addresses are used when no IPv4 address is returned.
Re[3]: 9.2 DNS Confusion
Ok a small update on this which might help sort my problem. Today I Wiresharked the network and I can what's happening now. When I don a plain ping www.apple.com the resolver is sending 2x requests to the FW's DNS proxy the first for an IPv4 A record and the 2nd for an IPv6 record! When I specify the -4 flag in PING the resolver sends only 1x request which is for the IPv4 A record. It would seem that the DNS Proxy on my SSG's (SSG140 ScOS 6.3r24) doesn't like the request (rightly so I guess as IPv6 is not enabled anywhere!) and returns nothing at all when this request is made. So my question changes to 'How do I get the resolver to NOT send the request, simply disabling IPv6 on the box does not prevent this behaviour?' Cheers -- Original Message -- From: "Simon Slaytor" <si...@slaytor.com> To: "Dan Ritter" <d...@randomstring.org> Cc: debian-user@lists.debian.org Sent: 18/11/2017 07:39:59 Subject: Re[2]: 9.2 DNS Confusion Hi Dan, Yes my thoughts exactly I've tried numerous ways including the gai.conf mod to 'disable' IPv6 on 9.2 none seem all that successful in 9.2. e.g. root@backup:/home/# cat /etc/gai.conf # Configuration for getaddrinfo(3). # ... ... ... # #precedence ::1/128 50 #precedence ::/0 40 #precedence 2002::/16 30 #precedence ::/96 20 #precedence :::0:0/96 10 # # For sites which prefer IPv4 connections change the last line to # precedence :::0:0/96 100 # # scopev4 # Add another rule to the RFC 6724 scope table for IPv4 addresses. ... ... ... #scopev4 :::127.0.0.0/104 2 #scopev4 :::0.0.0.0/96 14 root@backup:/home/# ip ad 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether ca:57:82:c2:51:ad brd ff:ff:ff:ff:ff:ff inet 172.16.11.22/24 brd 172.16.11.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::c857:82ff:fec2:51ad/64 scope link valid_lft forever preferred_lft forever root@backup:/home/# root@backup:/home/# ping www.google.com ping: www.google.com: Temporary failure in name resolution root@backup:/home/# ping -4 www.google.com PING www.google.com (216.58.206.36) 56(84) bytes of data. 64 bytes from 216.58.206.36: icmp_seq=1 ttl=54 time=11.2 ms 64 bytes from 216.58.206.36: icmp_seq=2 ttl=54 time=11.2 ms 64 bytes from 216.58.206.36: icmp_seq=3 ttl=54 time=11.5 ms 64 bytes from 216.58.206.36: icmp_seq=4 ttl=54 time=11.3 ms 64 bytes from 216.58.206.36: icmp_seq=5 ttl=54 time=11.3 ms ^C --- www.google.com ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4004ms rtt min/avg/max/mdev = 11.2 -- Original Message -- From: "Dan Ritter" <d...@randomstring.org> To: "Simon Slaytor" <si...@slaytor.com> Cc: debian-user@lists.debian.org Sent: 17/11/2017 16:39:57 Subject: Re: 9.2 DNS Confusion On Thu, Nov 16, 2017 at 07:55:18PM +, Simon Slaytor wrote: Hi Folks, Long time Debian user and up until now I've not had to reach out for help as I've always found the answer after a short Google. I've recently made the move from 8.x to 9.2 for my production boxes and I'm having the mother of all DNS issues. My network is simple: My network 2 x Juniper SSG-140 (Active/Passive) HA 1xTrust 1xDMZ 1xUntrust interfaces IPv4 only IPv6 is not enabled. 2 x Netgear GSM724 Switches The Junipers do DNS proxying for the Trust and DMZ networks. Junipers are in NAT/Route mode. Sitting onthe Trust network (172.16.11.0/24) are Debian 8.8 / 9.2 and Windoze 10 devices. Sitting in the DMZ network (192.168.102.0/24) are Debian 9.2 and Centos 7 devices My problem is this, after a vanilla 9.2 AMD 64 install DNS resolution 99 times out of 100 fails unless I force IPv4 for example: @backup:~$ su Password: root@backup:/home/# cat /etc/resolv.conf domain abc.com search abc.com. nameserver 172.16.11.1 root@backup:/home/# ip ad 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether ca:57:82:c2:51:ad brd ff:ff:ff:ff:ff:ff inet 172.16.11.22/24 brd 172.16.11.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::c857:82ff:fec2:51ad/64 scope link valid_lft forever preferred_lft forever root@backup:/home/#
Re[2]: 9.2 DNS Confusion
Hi Dan, Yes my thoughts exactly I've tried numerous ways including the gai.conf mod to 'disable' IPv6 on 9.2 none seem all that successful in 9.2. e.g. root@backup:/home/# cat /etc/gai.conf # Configuration for getaddrinfo(3). # ... ... ... # #precedence ::1/128 50 #precedence ::/0 40 #precedence 2002::/16 30 #precedence ::/96 20 #precedence :::0:0/96 10 # # For sites which prefer IPv4 connections change the last line to # precedence :::0:0/96 100 # # scopev4 # Add another rule to the RFC 6724 scope table for IPv4 addresses. ... ... ... #scopev4 :::127.0.0.0/104 2 #scopev4 :::0.0.0.0/96 14 root@backup:/home/# ip ad 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether ca:57:82:c2:51:ad brd ff:ff:ff:ff:ff:ff inet 172.16.11.22/24 brd 172.16.11.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::c857:82ff:fec2:51ad/64 scope link valid_lft forever preferred_lft forever root@backup:/home/# root@backup:/home/# ping www.google.com ping: www.google.com: Temporary failure in name resolution root@backup:/home/# ping -4 www.google.com PING www.google.com (216.58.206.36) 56(84) bytes of data. 64 bytes from 216.58.206.36: icmp_seq=1 ttl=54 time=11.2 ms 64 bytes from 216.58.206.36: icmp_seq=2 ttl=54 time=11.2 ms 64 bytes from 216.58.206.36: icmp_seq=3 ttl=54 time=11.5 ms 64 bytes from 216.58.206.36: icmp_seq=4 ttl=54 time=11.3 ms 64 bytes from 216.58.206.36: icmp_seq=5 ttl=54 time=11.3 ms ^C --- www.google.com ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4004ms rtt min/avg/max/mdev = 11.2 -- Original Message -- From: "Dan Ritter" <d...@randomstring.org> To: "Simon Slaytor" <si...@slaytor.com> Cc: debian-user@lists.debian.org Sent: 17/11/2017 16:39:57 Subject: Re: 9.2 DNS Confusion On Thu, Nov 16, 2017 at 07:55:18PM +, Simon Slaytor wrote: Hi Folks, Long time Debian user and up until now I've not had to reach out for help as I've always found the answer after a short Google. I've recently made the move from 8.x to 9.2 for my production boxes and I'm having the mother of all DNS issues. My network is simple: My network 2 x Juniper SSG-140 (Active/Passive) HA 1xTrust 1xDMZ 1xUntrust interfaces IPv4 only IPv6 is not enabled. 2 x Netgear GSM724 Switches The Junipers do DNS proxying for the Trust and DMZ networks. Junipers are in NAT/Route mode. Sitting onthe Trust network (172.16.11.0/24) are Debian 8.8 / 9.2 and Windoze 10 devices. Sitting in the DMZ network (192.168.102.0/24) are Debian 9.2 and Centos 7 devices My problem is this, after a vanilla 9.2 AMD 64 install DNS resolution 99 times out of 100 fails unless I force IPv4 for example: @backup:~$ su Password: root@backup:/home/# cat /etc/resolv.conf domain abc.com search abc.com. nameserver 172.16.11.1 root@backup:/home/# ip ad 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether ca:57:82:c2:51:ad brd ff:ff:ff:ff:ff:ff inet 172.16.11.22/24 brd 172.16.11.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::c857:82ff:fec2:51ad/64 scope link valid_lft forever preferred_lft forever root@backup:/home/# ping www.apple.com ping: www.apple.com: Temporary failure in name resolution root@backup:/home/# ping -4 www.apple.com PING e6858.dsce9.akamaiedge.net (2.18.170.28) 56(84) bytes of data. 64 bytes from 2.18.170.28: icmp_seq=1 ttl=50 time=19.3 ms 64 bytes from 2.18.170.28: icmp_seq=2 ttl=50 time=19.7 ms ^C --- e6858.dsce9.akamaiedge.net ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 19.311/19.508/19.705/0.197 ms root@backup:/home/# The above box is in the Trust network however the same result occurs if I use a host in the DMZ. If I however use a Centos 7 box everything works as expected e.g. [root@loadbalancer ~]# cat /etc/resolv.conf # Generated by NetworkManager nameserver 192.168.102.1 [root@loadbalancer ~]# ip ad 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft
9.2 DNS Confusion
Hi Folks, Long time Debian user and up until now I've not had to reach out for help as I've always found the answer after a short Google. I've recently made the move from 8.x to 9.2 for my production boxes and I'm having the mother of all DNS issues. My network is simple: My network 2 x Juniper SSG-140 (Active/Passive) HA 1xTrust 1xDMZ 1xUntrust interfaces IPv4 only IPv6 is not enabled. 2 x Netgear GSM724 Switches The Junipers do DNS proxying for the Trust and DMZ networks. Junipers are in NAT/Route mode. Sitting onthe Trust network (172.16.11.0/24) are Debian 8.8 / 9.2 and Windoze 10 devices. Sitting in the DMZ network (192.168.102.0/24) are Debian 9.2 and Centos 7 devices My problem is this, after a vanilla 9.2 AMD 64 install DNS resolution 99 times out of 100 fails unless I force IPv4 for example: @backup:~$ su Password: root@backup:/home/# cat /etc/resolv.conf domain abc.com search abc.com. nameserver 172.16.11.1 root@backup:/home/# ip ad 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether ca:57:82:c2:51:ad brd ff:ff:ff:ff:ff:ff inet 172.16.11.22/24 brd 172.16.11.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::c857:82ff:fec2:51ad/64 scope link valid_lft forever preferred_lft forever root@backup:/home/# ping www.apple.com ping: www.apple.com: Temporary failure in name resolution root@backup:/home/# ping -4 www.apple.com PING e6858.dsce9.akamaiedge.net (2.18.170.28) 56(84) bytes of data. 64 bytes from 2.18.170.28: icmp_seq=1 ttl=50 time=19.3 ms 64 bytes from 2.18.170.28: icmp_seq=2 ttl=50 time=19.7 ms ^C --- e6858.dsce9.akamaiedge.net ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 19.311/19.508/19.705/0.197 ms root@backup:/home/# The above box is in the Trust network however the same result occurs if I use a host in the DMZ. If I however use a Centos 7 box everything works as expected e.g. [root@loadbalancer ~]# cat /etc/resolv.conf # Generated by NetworkManager nameserver 192.168.102.1 [root@loadbalancer ~]# ip ad 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000 link/ether 22:e7:41:55:a6:9c brd ff:ff:ff:ff:ff:ff inet 192.168.102.10/24 brd 192.168.102.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::20e7:41ff:fe55:a69c/64 scope link valid_lft forever preferred_lft forever [root@loadbalancer ~]# ping www.apple.com PING e6858.dsce9.akamaiedge.net (2.20.214.243) 56(84) bytes of data. 64 bytes from 2.20.214.243 (2.20.214.243): icmp_seq=1 ttl=55 time=28.4 ms 64 bytes from 2.20.214.243 (2.20.214.243): icmp_seq=2 ttl=55 time=28.4 ms ^C --- e6858.dsce9.akamaiedge.net ping statistics --- 3 packets transmitted, 2 received, 33% packet loss, time 2002ms rtt min/avg/max/mdev = 28.453/28.456/28.459/0.003 ms [root@loadbalancer ~] Also Windoze 10 boxes running on the Trust network and Debian 8 boxes on both have no issues its purely the 9.2 boxes. Any help would be much appreciated. Simon
Re: Re: System becomes inaccessible after upgrade of libgl1-mesa-glx to version 17.2.2-1
> > The solution seems simple: > > > > The following packages will be REMOVED: > > libglvnd0-nvidia > > The following NEW packages will be installed: > > libglvnd0" > > > > But how do you do that with an inaccessible system? The system can be > > booted in recovery mode, and the change can be made there. But the > > network is not yet up and running. > You can do the following (assuming you use grub): > Change the kernel command line and append > systemd.unit=multi-user.target > This will boot (one-time) into a multi-user system (including network) > but not start the display manager. Thanks, that is a useful suggestion. These systemd targets open new possibilities, which I was not aware of.
System becomes inaccessible after upgrade of libgl1-mesa-glx to version 17.2.2-1
After an upgrade of libgl1-mesa-glx to version 17.2.2-1 and a reboot, the system hangs during startup and has become inaccessible. lightdm's x-0.log and Xorg.0.log logfiles mention an error: undefined symbol: _glapi_tls_Current. The problem is described in several bug reports: * Bug #878948 <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878948> * Bug #878851 <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878851> * Bug #876220 <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876220> The solution seems simple: The following packages will be REMOVED: libglvnd0-nvidia The following NEW packages will be installed: libglvnd0" But how do you do that with an inaccessible system? The system can be booted in recovery mode, and the change can be made there. But the network is not yet up and running. I solved the problem as follows. * Boot in another system on the machine that can mount the root file system of the affected debian system. * Download the libglvnd0 package. It can be found at /pool/main/libg/libglvnd/libglvnd0_0.2.999+git20170802-5_amd64.deb, e.g. ftp.nl.debian.org/debian/pool/main/libg/libglvnd/libglvnd0_0.2.999+git20170802-5_amd64.deb. Save the package in /var/cache/apt/archives of the mounted root file system. * Reboot into the affected system; select recovery mode in Grub * start aptitude * mark libglvnd0 for installation * resolve conflict by removing (purging) libglvnd0-nvidia * install * Check in aptitude whether libglvnd0 is installed * Continue to multi-user mode: systemctl default If everything went well, the prompt of lightdm appears. The first upgrade problem in years in testing that made the system unusable, has been solved. Thanks are due to the people who analyzed the problem and described their solution in the bug reports. Note: The syslog of the inaccessible system suggests that the system is up and running: Oct 18 10:07:07 vuurvlinder systemd[1]: Startup finished in 5.917s (kernel) + 20.713s (userspace) = 26.630s. Then it may be possible to log into the system from another computer and perform the package change, instead of the above procedure. Best, Simon
Server did not start after upgrade to postgresql 10
When I upgraded from postgresql 9.6 to 10, the postgres server failed to start. Error message: 'max_wal_senders must be less than max_connections'. The configuration file /etc/postgresql/10/main/postgresql.conf has the line #max_wal_senders = 0 suggesting that 0 is a default value. When I removed the comment symbol, effectively including this setting, I could start the server. This is different from 9.6. Is this a known problem, or should I report it as a bug? Simon
Re: Is there a list contains all debian packages and it's license ?
On Sat, 23 Sep 2017 at 10:25:33 +0200, to...@tuxteam.de wrote:
> Not a readymade solution, but perhaps a lead to follow: package copyright
> info is supposed to be in a file debian/copyright within the package source
> archive[1]. I don't know at the moment whether this info percolates to
> the package binary when building.
It does, and Debian Policy says it must. That information ends up in
/usr/share/doc/${binary_package}/copyright where ${binary_package} is the
binary package. For instance, the dbus source package produces binary
packages that include dbus, dbus-x11 and libdbus-1-3, so its
debian/copyright gets copied to /usr/share/doc/dbus/copyright,
/usr/share/doc/dbus-x11/copyright and /usr/share/doc/libdbus-1-3/copyright,
among others.
In rare cases the binary package copyright file is not identical to the
source copyright: if a package foo has a GPL part packaged as foo-utils
and a LGPL part packaged as libfoo0, it would be valid to list both GPL
and LGPL in debian/copyright, only GPL in /u/s/d/foo-utils/copyright
and only LGPL in /u/s/d/libfoo0/copyright. However, in practice
maintainers don't make use of this, because it creates extra work for
little or no benefit, and carries a risk of accidentally providing
incomplete or untrue copyright/licensing information.
S
Re: Mismatch of wxglade and wxwidgets
On 12/9/17 5:27 pm, Michael Lange wrote: > On Tue, 12 Sep 2017 15:02:35 +1000 > "Brendan Simon (eTRIX)" <brendan.si...@etrix.com.au> wrote: > >> I'm running Debian 8 Jessie. >> >> There seems to be a mismatch between wxglade (`python-wxglade`) and >> wxwidgets (`python-wxgtk3.0`) >> >> If I install wxglade and run it, I can choose to generate code for wx >> 2.6 or 2.8 compatibility. However the wx widgets that are installed use >> wx 3.0. >> >> It seems to me that wxglade needs to be updated in Jessie, to be >> compatible with the installed wxwidgets. >> >> According to the webpage at sourceforge, wxglade v0.7 added wx 3.0 >> compatibility and removed wx 2.6. >> >> http://wxglade.sourceforge.net/ >> >> v0.7.2 is latest release according to the sourceforge page, however the >> BitBucket repository states that it is out of date and to use the latest >> in the repository (a new maintainer). >> >> https://bitbucket.org/wxglade/wxglade >> >> ### How do I request getting `python-wxglade` updated to at least >> version 0.7.2 ?? > you could use reportbug to file a bug against python-wxglade. I doubt > however that this will be fixed for Jessie, but of course you could try. > Have you checked if the bug still persists with Stretch? Looks ok in Stretch (wxglade is at version `0.7.2-2`) https://packages.debian.org/stretch/wxglade I will report a bug and see what happens. It's not critical for me as I'm actually using the latest from the source repo. Maybe backports will update wxglade ? Thanks, Brendan.
Mismatch of wxglade and wxwidgets
I'm running Debian 8 Jessie. There seems to be a mismatch between wxglade (`python-wxglade`) and wxwidgets (`python-wxgtk3.0`) If I install wxglade and run it, I can choose to generate code for wx 2.6 or 2.8 compatibility. However the wx widgets that are installed use wx 3.0. It seems to me that wxglade needs to be updated in Jessie, to be compatible with the installed wxwidgets. According to the webpage at sourceforge, wxglade v0.7 added wx 3.0 compatibility and removed wx 2.6. http://wxglade.sourceforge.net/ v0.7.2 is latest release according to the sourceforge page, however the BitBucket repository states that it is out of date and to use the latest in the repository (a new maintainer). https://bitbucket.org/wxglade/wxglade ### How do I request getting `python-wxglade` updated to at least version 0.7.2 ?? Regards, Brendan.
cups: Backend /usr/lib/cups/backend/usb does not exist! [solved]
Hi everybody, it took me quite a while to figure this out so I thought I post this here for someone else in need to find this. I wanted to reinstall my printer Brother HL-3040CN after I upgraded to stretch. That didn't work at first. The installer failed with "Backend /usr/lib/cups/backend/usb does not exist!". ldadmin gave 'Bad device-uri scheme "usb"'. The solution was easy, if I had known what to do: copy /usr/lib/cups/backend-available/usb to /usr/lib/cups/backend/. Doi! Maybe this will help someone in the future. Simon
Re: laptop Acer Nvidia optimus
J'ai bumblebee + nvidia non-free. J'ai aussi des problèmes avec le gestionnaire de fichier. Mon fond d'ecran disparait quand je lance nautilus, ça m'a jamais vraiment gêné même si c'est moche. J'ai jamais tenté de brancher un second écran avant d'être logué (sous xfce4). Pour le gestionnaire je suis sous gdm3. Simon. Le 12/05/2016 14:06, e Lpe a écrit : > J'ai aussi un Acer avec Nvidia optimus. > > J'utilise "bumblebee", qui me permet de désactiver la carte nvidia (gain > d'autonomie énorme!). Jpeux toujours l'activer avec "optirun" mais je le > fais quasiment jamais. > > Si je branche un écran externe, mes deux écran sont bien détectés. > > > Nous parlons bien de la même chose ? A savoir bumblebee+nvidia et non > bumblebee+nouveau ? > > > Le 10 mai 2016 à 04:04, Simon P <si...@le-huit.fr > <mailto:si...@le-huit.fr>> a écrit : > > Salut, > > J'ai aussi un Acer avec Nvidia optimus. > > J'utilise "bumblebee", qui me permet de désactiver la carte nvidia (gain > d'autonomie énorme!). Jpeux toujours l'activer avec "optirun" mais je le > fais quasiment jamais. > > Si je branche un écran externe, mes deux écran sont bien détectés. > > Simon. > > Le 09/05/2016 20:17, Grégory Reinbold a écrit : > > Salut, > > > > Tu dis que pour l'instant ça tourne avec le driver Intel, as-tu déjà > > essayé d'installer les paquets nvidia non-free ? > > > > > > https://packages.debian.org/search?keywords=nvidia=names=all=all=mozilla-search > > > > > > Cordialement > > > > Le 09/05/2016 19:58, e Lpe a écrit : > >> Chalut, > >> > >> Je finis d'installer Debian Jessie x64 sur un Acer V3 nvidia optimus > >> gtx760m/intel 4600 > >> > >> 1°) j'ai jeté un oeil à la configuration nvidia via nvidia setting. > >> Une chose m'a surpris. Sur les deux écrans branchés (laptop+externe), > >> un seul écran apparaît ce qui ne me plait pas plus que ça. > >> > >> 2°) la résolution affichée dans l'onglet idoine est des plus > basique : > >> 640x480 > >> > >> Pour l'instant, je n'ai touché à rien. > >> Visiblement je tourne actuellement avec le pilote Intel. > >> > >> J'ai beau chercher dans divers site, il en ressort le bilan. La > >> plupart des sites donnent une documentation obsolète ou/et > incomplète. > >> Les canaux IRC doivent sûrement être habité par des administrateurs > >> réseaux ou autre car dès que l'on touche aux domaines qui intéressent > >> les portables : bouche cousue. > >> > >> Décevant ! Y aurait-il un autre utilisateur de Jessie x64 qui soit > >> allé un peu plus loin qu'une installation basique ? > >> > >> Merci d'avance. > >> > > > >
Re: laptop Acer Nvidia optimus
Le 10/05/2016 10:31, Pascal Obry a écrit : > Je pensais que bumblebee n'était plus maintenu? Je sais pas ce qu'il en ai mais le paquet debian évolue en tout cas: wheezy-backports 3.2.1-4~bpo70+1 jessie (stable) 3.2.1-7 jessie-backports 3.2.1-10~bpo8+1 stretch (testing) 3.2.1-10 sid (unstable) (utils): 3.2.1-11 J'utilise le paquet de Jessie (stable). Ca marchait bien aussi sous wheezy avec le paquet du backport. > L'écran externe est connecté en HDMI? J'avais eu des problèmes avec > l'HDMI lorsque j'avais essayé sur un Dell 4800. Il m'était impossible > d'obtenir une image sur l'écran externe! Je suis pas sur d'avoir déjà essayé en HDMI. Mais en VGA ça marche parfaitement. Simon.
Re: laptop Acer Nvidia optimus
Salut, J'ai aussi un Acer avec Nvidia optimus. J'utilise "bumblebee", qui me permet de désactiver la carte nvidia (gain d'autonomie énorme!). Jpeux toujours l'activer avec "optirun" mais je le fais quasiment jamais. Si je branche un écran externe, mes deux écran sont bien détectés. Simon. Le 09/05/2016 20:17, Grégory Reinbold a écrit : > Salut, > > Tu dis que pour l'instant ça tourne avec le driver Intel, as-tu déjà > essayé d'installer les paquets nvidia non-free ? > > https://packages.debian.org/search?keywords=nvidia=names=all=all=mozilla-search > > > Cordialement > > Le 09/05/2016 19:58, e Lpe a écrit : >> Chalut, >> >> Je finis d'installer Debian Jessie x64 sur un Acer V3 nvidia optimus >> gtx760m/intel 4600 >> >> 1°) j'ai jeté un oeil à la configuration nvidia via nvidia setting. >> Une chose m'a surpris. Sur les deux écrans branchés (laptop+externe), >> un seul écran apparaît ce qui ne me plait pas plus que ça. >> >> 2°) la résolution affichée dans l'onglet idoine est des plus basique : >> 640x480 >> >> Pour l'instant, je n'ai touché à rien. >> Visiblement je tourne actuellement avec le pilote Intel. >> >> J'ai beau chercher dans divers site, il en ressort le bilan. La >> plupart des sites donnent une documentation obsolète ou/et incomplète. >> Les canaux IRC doivent sûrement être habité par des administrateurs >> réseaux ou autre car dès que l'on touche aux domaines qui intéressent >> les portables : bouche cousue. >> >> Décevant ! Y aurait-il un autre utilisateur de Jessie x64 qui soit >> allé un peu plus loin qu'une installation basique ? >> >> Merci d'avance. >> >
Re: clone d'un système: problème avec systemd au boot
Si le nouveau disque dur a été formaté, il doit y avoir un problème d'UUID. Solution booter sur un système live. exécuter la commande sudo blkid identifier les UUID des partitions. monter le disque dur fraichement restauré mettre à jour les fichier de config avec les nouveau UUID: /boot/grub/grub.cfg et surtout /etc/fstab Et ça devrait pouvoir fonctionner à nouveau correctement. Le 08/03/2016 01:06, Gaëtan PERRIER a écrit : > Bonjour, > > Je viens de changer le disque dur de mon portable en clonant (avec fsarchiver > savedir/restdir) son disque vers le nouveau puis en réinstallant grub avec un > chroot. Mais au boot suivant, bien que la machine démarre, j'ai plein > d'erreurs > systemd du genre: > > Failed to mount Configuration File System > > Failed to mount FUSE Control File System > > Failed to start File System Check on Root Device > > etc. > > Vu que j'entrave que dalle à systemd je ne sais pas trop quoi faire ? > > A+ > > Gaëtan >
Unable to connect to higher wifi channels with Broadcom BCM4360
Hi everyone, I have a Broadcom BCM4360 wireless card (Archer T8E), which uses the wl module (version 6.30.223.248 on jessie). I am unable to connect to channel 100 or higher on the 5GHz band. The problem seems to be: `iwlist wlan0 chan` returns: wlan0 32 channels in total; available frequencies : Channel 01 : 2.412 GHz [snip] Channel 64 : 5.32 GHz Channel 66 : 5.33 GHz Channel 68 : 5.34 GHz Channel 96 : 5.48 GHz Current Frequency:5.22 GHz (Channel 44) `iw reg get` gives me: country DE: DFS-ETSI (2400 - 2483 @ 40), (N/A, 20), (N/A) (5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS (5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS (57000 - 66000 @ 2160), (N/A, 40), (N/A) Am I missing something or is the card and the module just not supporting higher channels? I would be thankful for any pointers. Cheers, Simon
Re: Restrict apt to specific Jessie distro
On 14/02/2016 12:07 AM, Andrew M.A. Cater wrote: > On Sat, Feb 13, 2016 at 10:12:15PM +1100, Brendan Simon wrote: >> Is there a way to restrict apt to a **specific release** of Jessie. >> e.g. 8.1, 8.2, 8.3, ... ?? >> >> I build root filesystems for embedded systems. The sources.list is set >> to Jessie, but the contents of the generated rootfs can change from one >> day to the next if there have been updates. I want to lock into a >> specific release and be sure that the packages wont change if I build >> now and 6 or 12 months later. >> >> What's the best way to do this? > Short answer: No, if you ever want security updates / other fixes. > > Longer answer: not by design. Mirror 8.4 on the day of release, get the DVDs > / build a Blu-Ray .iso using jigdo > and use these for hoever long. > > Jessie is Debian 8 - so all changes to Debian 8 apply through the lifetimme > of the release. > > Point releases are snapshots rolling up security fixes etc. to that point. > You don't _need_ them if you keep > systems up to date. > > In general, locking to a specific point in time / a "golden image" and using > it for a period would be a bad > move because of the fact that the release receives fixes. > > Sizes shouldn't change that drastically - in general, packages replace their > predecesors precisely so net > change is of the order of kB. > > Hope this helps > > AndyC Thanks Andy. I guess the DVDs might be the way to go. The thing is when you are deploying something to lots of sites (e.g. an embedded data logger in many remote locations), it's important to know exactly what versions you have created and installed, and more importantly be able to rebuild the exact same system sometime down the track. e.g. 6-12 months later, when bug is reported and you need to be able to replicate the build and make changes based on that build. Often a patch release will be deployed based on the a build from that point in time, so as to not introduce any "new features" or unknown changes in behaviour. Thanks, Brendan.
Re: Restrict apt to specific Jessie distro
On 14/02/2016 12:49 AM, Christian Seiler wrote: > On 02/13/2016 12:12 PM, Brendan Simon wrote: >> Is there a way to restrict apt to a **specific release** of Jessie. >> e.g. 8.1, 8.2, 8.3, ... ?? >> >> I build root filesystems for embedded systems. The sources.list is set >> to Jessie, but the contents of the generated rootfs can change from one >> day to the next if there have been updates. I want to lock into a >> specific release and be sure that the packages wont change if I build >> now and 6 or 12 months later. >> >> What's the best way to do this? > If you *really*, *really* want to do that against better judgment, > you can use the http://snapshot.debian.org/ service. See the > instructions there, just pick the current date. And realize that > you are using old versions of software with potential security > problems. (Even worse, since at least for me snapshot.d.o doesn't > support https, and you have to disable Valid-Until in APT to make > it work, an attacker in your network with man-in-the-middle > capabilities could serve you versions of Jessie that are even > older than the ones you want, which have more security problems > and you wouldn't really notice it, especially if you automate your > process.) > > Regards, > Christian Thanks Christian. I've had a quick look at snapshot.debian.org and it might be worth considering. The thing is when you are deploying something to lots of sites (e.g. an embedded data logger in many remote locations), it's important to know exactly what versions you have created and installed, and more importantly be able to rebuild the exact same system sometime down the track. e.g. 6-12 months later, when bug is reported and you need to be able to replicate the build and make changes based on that build. Often a patch release will be deployed based on the a build from that point in time, so as to not introduce any "new features" or unknown changes in behaviour. Specifying a date in the apt sources.list may achieve that, but locking in the versions to that date or earlier. Subsequent security release based updates can be achieved by updating the date at a controlled time, doing a build, testing thoroughly and then releasing. Does apt not use keyrings or some kind of certificates for authenticating versions? Thanks, Brendan.
Restrict apt to specific Jessie distro
Hi, Is there a way to restrict apt to a **specific release** of Jessie. e.g. 8.1, 8.2, 8.3, ... ?? I build root filesystems for embedded systems. The sources.list is set to Jessie, but the contents of the generated rootfs can change from one day to the next if there have been updates. I want to lock into a specific release and be sure that the packages wont change if I build now and 6 or 12 months later. What's the best way to do this? Thanks, Brendan.
can't boot Jessie since power drop-out (virtualbox on MacBook with SSD)
I was/am running Jessie 8.2 in a VirtualBox on my MacBook. The MacBook shutdown without warning while my Jessie VB was running, and now the VM wont boot properly. I get stuck in emergency mode. Ctrl-D does nothing - just cycle back to same message. I googled a bit and found that if I comment out entries in /etc/fstab for the cdrom and my home directory (on the mac) then it will boot fine. Once booted I can uncomment my home directory entry and mount it ok, but the system refuses to boot if it is left uncommented. It used to work find before the power drop-out, so I'm presuming something is corrupt on the filesystem somewhere. I tried to boot a live image and do an "fsck /dev/sda1" but it said it was clean. Really ??? What's the best way to recover this so my system will boot properly? I was going to do a reinstall but I couldn't find a way of doing that without repartitioning the disk (which I didn't want to do as I don't want to lose any of my data). I could always create a new virtual disk for my home directory and just reinstall a new debian system, but I figure there should be a better way to recover. Thanks, Brendan.
Re: can't boot Jessie since power drop-out (virtualbox on MacBook with SSD)
On 5/11/2015 10:09 AM, Charlie Kravetz wrote: > On Thu, 5 Nov 2015 09:59:19 +1100 > "Brendan Simon (eTRIX)" <brendan.si...@etrix.com.au> wrote: > >> I was/am running Jessie 8.2 in a VirtualBox on my MacBook. The MacBook >> shutdown without warning while my Jessie VB was running, and now the VM >> wont boot properly. I get stuck in emergency mode. Ctrl-D does nothing >> - just cycle back to same message. >> >> I googled a bit and found that if I comment out entries in /etc/fstab >> for the cdrom and my home directory (on the mac) then it will boot fine. >> Once booted I can uncomment my home directory entry and mount it ok, but >> the system refuses to boot if it is left uncommented. >> >> It used to work find before the power drop-out, so I'm presuming >> something is corrupt on the filesystem somewhere. >> I tried to boot a live image and do an "fsck /dev/sda1" but it said it >> was clean. Really ??? >> >> What's the best way to recover this so my system will boot properly? >> >> I was going to do a reinstall but I couldn't find a way of doing that >> without repartitioning the disk (which I didn't want to do as I don't >> want to lose any of my data). >> I could always create a new virtual disk for my home directory and just >> reinstall a new debian system, but I figure there should be a better way >> to recover. >> >> Thanks, >> Brendan. > Check the hidden files in your home directory. They should all be user > owned. If any are root owned, that can prevent the user from being able > to access the directory. > > The usual suspects are .Xauthority and .ICEauthority. I delete the > problem, usually. Then I can restart and the system will work again.It > recreates the missing file in the users name. In linux home directory, I do not have a .Xauthority file, and my .ICEauthority is owned by me (uid=1001) In Mac home directory, I do not have a .ICEauthority file, and my .Xauthority is owned by me (uid=501) I don't see how those files would stop my linux system booting and entering emergency mode. The system should be able to boot to a login prompt (console or graphical) without having to look into a user's home directory (the linux home directory is on the root filesystem) I can mount the directory fine after the system has booted (comment out /etc/fstab entries, boot, uncomment /etc/fstab entries, mount). Here is met /etc/fstab file. # # / was on /dev/sda1 during installation UUID=eee91f72-bc88-4877-9b98-7b10c7de2d9a / ext4 errors=remount-ro 0 1 # swap was on /dev/sda5 during installation UUID=331c2aba-e505-4d25-bb0b-863dfdb9eb8f noneswap sw 0 0 #/dev/sr0/media/cdrom0 udf,iso9660 user,noauto 0 0 #brendan /media/sf_brendan vboxsf uid=1001,gid=1001 0 0 Is there some dpkg command to reinstall al the installed packages (or base packages) so that it wont barf at boot time?
Re: Rsnapshot /var/run PID
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, Oct 25, 2015 at 04:27:10PM +, Simon wrote: Hi All, Using Debian 8 and I'd like to run rsnapshot as a regular (non-root) user but it doesn't have permissions to drop the pid file in /var/run. I created a directory called rsnapshot in /var/run with the appropriate permissions which, I thought, fixed the problem. Unfortunately, I now realise that the dir I created gets removed upon a reboot. Could someone let me know the correct way create an application-specific directory in /var/run (if that is the right thing to do). It seems to be that since a while, all those /run, /var/run etc. are on tmpfs anyway; the init machinery is supposed to set up the necessary subdirectories [1] [2]. This doesn't help you in your case, I guess, because you want to run rsnapshot "ad hoc". My gut feeling would be to set things up in a well-known sub-directory of the user's home, on the theory that this is the space the user controls. Either just ~/.rsnapshot, or ~/.backup, or if you want to go the full Freedesktop Monty, have a look at [3] (they specify /run/user for that; there's no such thing in my system, but my system is somewhat Freedesktop hostile by explicit choice, so that might be just a consequence of that. Perhaps going the systemd way fixes that). [1] https://wiki.debian.org/ReleaseGoals/RunDirectory#Policy [2] https://www.debian.org/doc/debian-policy/ch-opersys.html#s-sysvinit [3] http://www.freedesktop.org/software/systemd/man/file-hierarchy.html Regards - -- tomás -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlYt3kgACgkQBcgs9XrR2kaMtgCfSu74xjoNnwinPh8uxxKzUrZP vM4An0D5qD0ZPs2X3jLCEf+SOeOf29oy =FI7A -END PGP SIGNATURE- Thanks for the detailed answer, I went with putting the lock file in the users' home as that makes sense to me. I guess when I have more time I'll look into doing it the systemd way (be good to learn more about it). Thanks : )
Rsnapshot /var/run PID
Hi All, Using Debian 8 and I'd like to run rsnapshot as a regular (non-root) user but it doesn't have permissions to drop the pid file in /var/run. I created a directory called rsnapshot in /var/run with the appropriate permissions which, I thought, fixed the problem. Unfortunately, I now realise that the dir I created gets removed upon a reboot. Could someone let me know the correct way create an application-specific directory in /var/run (if that is the right thing to do). Thanks, Simon
Re: Security in our local network
Hi, On 08/15/2015 12:00 PM, B. M. wrote: - WLAN: SSID hidden, strong password, but I can't really trust the router, can I ? Hidden SSID probably just gives you a wrong sense of security. See here [1] for example. Cheers, Simon [1] http://www.howtogeek.com/howto/28653/debunking-myths-is-hiding-your-wireless-ssid-really-more-secure/
Re: Grub not seeing my root did
Hi, On 12/08/15 03:46, Herminio Hernandez Jr. wrote: I just installed Debian on my MacBook Pro and now it cannot see my root to boot from. On the live CD and manually set the boot flag on the partition but still no go. Has anyone ran into this before? How did you install Debian? What version/... of Debian did you install? Be specific, opt for telling more than less if in doubt. What is the exact model of your laptop? Can you maybe give us hardware specification? Are you using SecureBoot? What boot loader are you using? If you use grub2(the default), where did you install grub2? Are there operation systems other than Debian installed to your laptop right now? Don't think people here are unhelpful, you asked for help without caring to disclose the information needed to do so. Please follow the guidelines of this mailing list when using it. To help you, assuming you didn't reinstall grub when booting from the install CD in rescue mode (I think that's what you did): You probably just need to run rescue mode chrooted into your installed root partation and run: (assuming /dev/sda is the disk you installed Debian to you want GRUB to take over the Master Boot Record of this disk (You want GRUB to manage booting).) # update-grub # grub-install /dev/sda Afterwards, reboot to hd and voilà. Ciao, Simon
Re: IP address
Hi, On 07/17/2015 07:50 PM, John J. Boyer wrote: None of these solutions work. ifconfig is not available on Jessie. ip seems to be inapropriate. dig produces nothing. I have used ifconfig on other distros. ifconfig is available if you install net-tools. And what do you mean with ip seems to be inapropriate? `ip addr` works fine here on Jessie. Cheers, Simon -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/mobftp$3at$1...@news.albasani.net
Re: nfs problems
Hi, On 05/08/2015 09:00 AM, Petter Adsen wrote: On Fri, 8 May 2015 00:50:24 -0400 Gene Heskett ghesk...@wdtv.com wrote: On Friday 08 May 2015 00:36:51 bri...@aracnet.com wrote: On Fri, 8 May 2015 00:03:22 -0400 Gene Heskett ghesk...@wdtv.com wrote: i just finished wrestling with NFS set-up problems myself. Add no_root_squash here, and root will be able to write on the clients. But isn't there a potential security risk in using that option? AFAIK, with that option enabled, a remote root user (on the nfs client) could gain root privileges the nfs server. Cheers, Simon -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/miis8s$15h$1...@news.albasani.net
Re: Have I been hacked?
On 01/06/2015 09:10 AM, Danny wrote: [...] However, prior to this breakin, in early December 2014, I noticed my network behaving strangely especially through wireless connections. [...] I can't give you any input on your specific problem. But here is a pointer from the Securing Debian Manual (if you don't already know it): After the compromise (incident response) [1] Cheers, Simon [1] https://www.debian.org/doc/manuals/securing-debian-howto/ch-after-compromise.en.html -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/m8h3u6$q7e$1...@news.albasani.net
Re: Continuing to use SysV; LTS [Re: Fwd: Re: Skipping fsck during boot with systemd?]
On 31 December 2014 18:10:00 GMT+00:00, Andrei POPESCU andreimpope...@gmail.com wrote: On Mi, 31 dec 14, 09:45:53, Jerry Stuckle wrote: I've never said anyone should be obliged to maintain Debian the way I want. I said the way they are going is not acceptable, so my clients are changing distributions. Period. I think the point some are trying to make is that Debian's direction can be influenced[1], but this requires involvement. It might also be cheaper in the long term than distro-hopping every time the distribution in use takes an unwanted turn. Of course, this will not fare well with people that chose GNU/Linux because of the wrong impression that it is without cost. [1] possibly even more so than other distributions, provided the desired changes don't go against the Social Contract, etc. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt This is very interesting, I've always viewed Linux as 'the peoples' choice for an OS but watching these responses has made me think/realise that it's not really. Its development is driven by the biggest financial contributors - which will always be the corps. Due to it's open nature it is perhaps more susceptible to abuse/conflict in this area too. I guess I've been a little naive to that till this whole sysd thing. -- Simon
Re: /var/lib/dpkg/status strangeness
SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_DescriptionStatus Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 14025 - # 2 Extended offlineCompleted without error 00% 14024 - That all looks good. It still seems like a big coincidence that the word airdrawndagger appeared there as this machine never in it's life saw that wifi. Although The smart TV it's connected to via HDMI did... It is strange. I don't know what more to suggest. And apparently no one else does either because there are no other comments. Among the last hints I can provide would be to install mcelog to make sure that any machine check exceptions are logged. # apt-get install mcelog It would also be possible to 'grep' through your swap partition just to see if there are interesting things there. For example if you found airdrawndagger there or other things then that could be a useful clue that it came through there. For example, I am just brainstorming, haven't thought about it much: # LC_ALL=C grep -a airdrawndagger /dev/mapper/v1-swap Or perhaps: # strings /dev/mapper/v1-swap | grep airdrawndagger But since then it could have been overwritten too. So even if nothing found it doesn't say much. Again, to me this feels like flaky hardware more than anything else. Is it too paranoid to consider some kind of malware from another machine on the network? Some would say that it is impossible to be too paranoid. But it is all a long gray scale. It all depends. If this is simply your desktop and it lives on a private home network then I probably wouldn't be too paranoid. If you are running a banking system and it is handling credit card data on the hostile Internet then for that I would be quite a bit more paranoid. It all depends. It doesn't feel like an attack since an attacker would have no knowledge of that old wifi ssid either. So at least not directly using that data. So far too many unknowns. I still think that somehow the string was still in the swap partition of the disk after all of this time and therefore got sucked into memory that way somehow. I think if we knew exactly how it happened we would be amazed at the coincidences needed to have it occur. It feels more like a random machine failure due to the consumer grade hardware which we are all using these days. It isn't required to run faster than the bear. It is only required to run faster than the other person who is also running from the bear. Therefore hardware vendors don't make great reliable Unix server quality hardware these days. Instead it is mosly MS quality hardware. Almost no desktops have parity anymore for example. Because of this the hardware just isn't ultimately reliable. You will drive yourself crazy if you try to chase down every odd thing. Bob Thanks a lot, I'll defo get mcelog installed -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/4882998.Z6FHP07u20@dragonfly
Re: dpkg/status corruption question
On Tuesday 23 December 2014 15:29:47 Bob Proulx wrote: Hello Simon, Simon Bell wrote: My /var/lib/dpkg/status file became corrupt recently, I was getting this when trying to apt-update: You asked this question before and I posted a reply to it then. Did you miss seeing it? I think you must have because you have apparently asked the same question again. https://lists.debian.org/20141222182904951848044.noccsple...@bob.proulx.com Bob I did miss it, thanks for the link. Something didn't quite work right with my initial subscription so I assumed my mail hadn't made it. Apologies, I'll reply to the original. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1669403.BYF7jZVJNI@dragonfly
Re: /var/lib/dpkg/status strangeness
Thanks Bob, I'll update /etc/smartd.conf as you recommended. The output currently looks ok: *** ... === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED ... SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 100 100 062Pre-fail Always - 0 2 Throughput_Performance 0x0005 100 100 040Pre-fail Offline - 0 3 Spin_Up_Time0x0007 173 173 033Pre-fail Always - 2 4 Start_Stop_Count0x0012 100 100 000Old_age Always - 464 5 Reallocated_Sector_Ct 0x0033 100 100 005Pre-fail Always - 0 7 Seek_Error_Rate 0x000b 100 100 067Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 100 100 040Pre-fail Offline - 0 9 Power_On_Hours 0x0012 068 068 000Old_age Always - 14064 10 Spin_Retry_Count0x0013 100 100 060Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000Old_age Always - 464 160 Unknown_Attribute 0x0032 100 100 000Old_age Always - 0 191 G-Sense_Error_Rate 0x000a 100 100 000Old_age Always - 51539607552 192 Power-Off_Retract_Count 0x0032 100 100 000Old_age Always - 30 193 Load_Cycle_Count0x0012 023 023 000Old_age Always - 776233 194 Temperature_Celsius 0x0002 171 171 000Old_age Always - 32 (Min/Max 16/48) 195 Hardware_ECC_Recovered 0x000a 100 100 000Old_age Always - 0 196 Reallocated_Event_Count 0x0032 100 100 000Old_age Always - 0 197 Current_Pending_Sector 0x0022 100 100 000Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000Old_age Offline - 0 199 UDMA_CRC_Error_Count0x000a 200 200 000Old_age Always - 0 223 Load_Retry_Count0x000a 100 100 000Old_age Always - 0 254 Free_Fall_Sensor0x0032 100 100 000Old_age Always - 20 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_DescriptionStatus Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 14025 - # 2 Extended offlineCompleted without error 00% 14024 - *** fsck seems to run fine on boot too. It still seems like a big coincidence that the word airdrawndagger appeared there as this machine never in it's life saw that wifi. Although The smart TV it's connected to via HDMI did... Is it too paranoid to consider some kind of malware from another machine on the network? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1434287.BRldXdCveZ@dragonfly
dpkg/status corruption question
Hi Everyone, My /var/lib/dpkg/status file became corrupt recently, I was getting this when trying to apt-update: dpkg: error: parsing file '/var/lib/dpkg/status' near line 27803 package 'gcr': field name `°[?@' must be followed by colon E: Sub-process /usr/bin/dpkg returned an error code (2) I managed to correct the issue by pulling some stuff from /var/lib/dpkg/status- old... But, can anyone explain why the corruption (shown below) ended up containing the name of an old wireless SSID I used to use!? *** Description: GNOME crypto services (daemon and tools) GCR is a library for crypto UI and related tasks. . This package contai9c^@^@^@^D ÃÃJ^@^@^@^@^@^@^@^@^@^F^AïE^L^@r and prompter ^D°^D[?@^@^@^@ÿÿÿÿÿÿ8cÃÃr^NÃÿÿÿÿÿÿpã^@^Nairdrawndagger^A^D^B^D^K^V2^H^L^R^X$0H`l- ^Zl^X^Zÿÿ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^^A^@^A^@^C^E^@^@^@^@^@Ã^^^@90L3l^X^Zÿÿ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^A^A^@^@ÿ^A^@^@^@^@^@1à ^K^Salled *** The SSID was called 'airdrawndagger', it hasn't been active for over a year and the machine in question was clean installed after the Wireless network was replaced with another! Is corruption of the /var/lib/dpkg/status file normal - I've never had it happen before now? And does anyone have any idea how 'airdrawndagger' could have appeared there?! Thanks : ) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1442536.BWRW2CJmYH@dragonfly
Re: wine does nothing
On Tuesday 23 December 2014 14:43:13 François Patte wrote: Bonjour, I have a garmin GPS; in order to register the product and update the maps, there is only a windows application GarminExpress. I have no windows install, so I installed wine on my debian sid and tried to run this program: wine GarminExpress.exe But, wine seems to do nothing, says nothing and, after a while gives up without any message... Do I have to install something else? Is there a way to understand why wine gives up? Some logs somewhere? Moreover, I cannot see any wine menu in xfce menus... Is it normal? Thanks for anty help. WineHQ is often a good place to start if you haven't been there already e.g. https://appdb.winehq.org/objectManager.php?sClass=versioniId=7502 Simon -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1712632.plBsIc0ATM@dragonfly
/var/lib/dpkg/status strangeness
Hi Everyone, My /var/lib/dpkg/status file became corrupt recently, I was getting this when trying to apt-update: dpkg: error: parsing file '/var/lib/dpkg/status' near line 27803 package 'gcr': field name `°[?@' must be followed by colon E: Sub-process /usr/bin/dpkg returned an error code (2) I managed to correct the issue by pulling some stuff from /var/lib/dpkg/status- old... But, can anyone explain why the corruption (shown below) ended up containing the name of an old wireless SSID I used to use!? *** Description: GNOME crypto services (daemon and tools) GCR is a library for crypto UI and related tasks. . This package contai9c^@^@^@^D ÃÃJ^@^@^@^@^@^@^@^@^@^F^AïE^L^@r and prompter ^D°^D[?@^@^@^@ÿÿÿÿÿÿ8cÃÃr^NÃÿÿÿÿÿÿpã^@^Nairdrawndagger^A^D^B^D^K^V2^H^L^R^X$0H`l- ^Zl^X^Zÿÿ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^^A^@^A^@^C^E^@^@^@^@^@Ã^^^@90L3l^X^Zÿÿ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^A^A^@^@ÿ^A^@^@^@^@^@1à ^K^Salled *** The SSID was called 'airdrawndagger', it hasn't been active for over a year and the machine in question was clean installed after the Wireless network was replaced with another! If only for my sanity, does anyone have any idea how this could happen? Thanks : ) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5243583.fnnqpd5hLi@dragonfly
Re: boot fails on jessie on Acer Travelmate
Hi again, On 03/12/14 08:56, Pierre Couderc wrote: Le 03/12/2014 07:58, Simon Hollenbach a écrit : you might want to dig further into this, Mmm, what is my other choice ? W8 ? Ubuntu ? I was talking about reporting a bug when you don't know what's wrong. But indeed, there are other choices if you want them, I don't, right now, and as we are talking about this on a Debian support list, discussing them here would be imho inappropriate anyway. as I can't see how a developer could fix the error you are experiencing without more information. But I am ready to spend hours to fix that ! Wht is needed ? Further information. But what you provided in your other mail, the partition layout, seems to be a good start, maybe even enough to solve your problem, not the installer's/GRUB's. I'll come back to that. When exactly does the boot-up stall? You don't even see the GRUB menu, do you? I am not sure what is the grub menu, but if it is the blue menu asking which debian version to load. I do not arrive there. It isn't blue any more at my place, it's skinned with a Debian logo aso, but yes, the menu that lets you select a boot-mode/kernel/os . It starts with GRUB loading... and then Welcome to GRUB iirc, followed by aforementioned menu. In fact, it seems to me that the disk is not read, but it tries to net boot. Why do you think it tries to boot from a network? Have you tried with another boot loader? Last time I installed, LILO was still available for selection from expert install iirc. If the system boots with LILO, you would have narrowed down the problem quite a bit. No, sorry, I am not enough expert. If this is a regression in GRUB, it must be solved, one way or another. Debian wheezy works fine on this computer. Jessie has worked too, but no more today. I don't consider myself an expert either, the expert install just asks more stuff, explained very well imo. Maybe just try it next time you install or on a spare machine. Again, I don't think filing a bug without any info but it doesn't work will get your problem solved. I am not able to find the bug myself. I am ready to spend hours to fix it, but I need the help of someone to tell me where to search... I think we got a differing understanding here. I think you just encountered a bug, or you did something really stupid, which shouldn't happen if you sanely try to install Debian. We got to describe the bug now, so it can be fixed. Now my solution attempt, it worked for me once (but like 3 years ago) On 03/12/14 11:19, Pierre Couderc wrote: One big difference is that after jessie installation boot flag has disappeared : gpt : wheezy : snip/ Number Start EndSizeFile system Name Flags 1 1049kB 512MB 511MB fat32 boot snip/ jessie : Number Start EndSizeFile system Name Flags 1 1049kB 538MB 537MB fat32 Why don't you toggle the bootable-flag on your /boot-partition by hand? It happened to me that this was the only thing that was wrong after installing. I did it with fdisk, run it from a rescue CD, specifying your disk /dev/sda as parameter: # fdisk /dev/sda Then, you hit [p] to print the partition table of sda, start counting from 0 until you find your boot partition, it should be 0, according to the gpt output. Then hit [b] to toggle the bootable flag on a partition and select the partition you just identified as your /boot-partition. Finally, write the changes to disk with [w], which also exits fdisk. Then reboot and, if you want, cross your fingers... Cheers, Simon -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/547f6858.4050...@gmail.com
Re: boot fails on jessie on Acer Travelmate
Sent this to Pierre's private mail first. Sorry. Hi Pierre, you might want to dig further into this, as I can't see how a developer could fix the error you are experiencing without more information. Have you tried chrooting into the unbootable system from an install cd's rescue mode? Is there anything suspicious in the logs? When exactly does the boot-up stall? You don't even see the GRUB menu, do you? Have you tried with another boot loader? Last time I installed, LILO was still available for selection from expert install iirc. If the system boots with LILO, you would have narrowed down the problem quite a bit. If you do get to GRUB but booting fails afterwards, you can try adding debug flags to your kernel options, see: https://wiki.archlinux.org/index.php/boot_debugging This link is for Arch, so be careful, not every last bit also applies to Debian, but it was the most comprehensive guide I could find now. Again, I don't think filing a bug without any info but it doesn't work will get your problem solved. Good luck, Simon -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/547eb486.20...@gmail.com
aa-logprof/aa-genprof not working after jessie upgrade
Hi everyone, I recently upgrade to jessie. I noticed now that aa-logprof/aa-genprof (for apparmor) stopped working. When I try to create a new profile with aa-genprof it doesn't add any rules while I see them in the logs. Same with aa-logprof (both worked just fine in wheezy) . I don't know how to debug this further. Is this a bug in the jessie packages or did I miss something in the upgrade progress? Cheers, Simon -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/m57rlt$eie$1...@news.albasani.net
Re: Ctrl-Alt-F12 to show Kernel messages
On 11/13/2014 11:50 AM, Renaud (Ron) OLGIATI wrote:
In a distribution I used long ago (Slackware 96 ? Mandrake 6.0 ?)
Ctrl-Alt-F12 would take you to a screen displaying in real time the kernel
messages.
Is that possible in Debian ?
Yes. With syslog-ng, you can use destination d_console_all {
file(/dev/tty12); }; and set up a proper log path.
Cheers,
Simon
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/m42sg4$e75$1...@news.albasani.net
Re: Possible comprommission, what to do ?
On 11/13/2014 10:00 AM, Erwan David wrote: [...] However, I'd prefer be sure my server was not compromised, and at the lower possibe cost (in time and work). Is there a way to check the packages/installed files from outside sources (I may boot a fresh live system in order to have clean utilities), or even provoke a reinstall with a new download of the whole system ? You might want to have a look at the Securing Debian Manual Chapter 11 - After the compromise (incident response) [1]. Cheers, Simon [1] https://www.debian.org/doc/manuals/securing-debian-howto/ch-after-compromise.en.html -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/m42s9a$dm1$1...@news.albasani.net
Re: WLAN router doesn't provide fix IP addresses
Hello,
On 31/10/14 09:45, Karl E. Jorgensen wrote:
On Fri, Oct 31, 2014 at 09:28:33AM +0100, B. M. wrote:
Hi list,
I have a problem with my (w)lan setup. We use telephone and
internet over the cable network and the company gives us a wlan
modem for free. Unfortunately this modem doesn't allow me to specify
fix IPs in the internal network for all of our machines.
Well - even if it doesn't, surely it allows you to specify which
*range* of IP addresses should be used for DHCP?
There is nothing wrong with configuring a server with a fixed IP
address (=not use DHCP client), as long as you use the correct
network, netmask and default gateway.
That seems the way to go to me.
Nevertheless I setup an owncloud server on one machine (which is
somehow our server but not always running), including SSL
encryption with a self-signed certificate for its IP address. That
worked well for a couple of months because the IP addresses didn't
change (although they were not fixed).
Now due to a technical problem our modem got replaced all of the IP
addresses changed. (I did expect that for sometime in the
future... but not so early...)
Since it's impossible to manually define the IP addresses, I've a
problem. Of course I could create a new certificate, put it on all
other machines and adjust all settings (owncloud server address...);
but that's quite an hassle.
Do the machines use avahi (or mdns? I'm actually not sure of the name,
but having libnss-mdns installed and mdns4 mentioned in
/etc/nsswitch.conf would indicate so).
A quick research suggests you need avahi-daemon for propagation of
.local-domains, e.g. for machines that need to be discovered, and
libnss-mdns for discovery of the former.
For the name, the description of libnss-mdns says:
Multicast DNS (using Zeroconf, aka Apple Bonjour / Apple Rendezvous )
It seems to have many names.
If so, you should be able to use ${hostname}.local instead of an IP
address, and the multicast DNS resolution would sort things out.
So I wanted to ask if there are other possibilities? I can define
one or two DNS server in the modem's config. Would it work to setup
my main machine (which is not always running) as an internal DNS
server and use the hostnames instead of the IP addresses?
That is also a possibility. But if it is only for facilitating a
single server, then it's overkill. And it adds a single point of
failure too: you would not be able to resolve IP addresses while the
machine is down.
Maybe I'm mistaken, but wouldn't this just shift the problem to the
internal DNS? It will still need a static IP or mDNS. Adding to that, it
would need to be the only DNS in the router's config, as you cannot
guarantee which one the router will use otherwise and the owncloud
server wouldn't be discoverable via the second(public) DNS. And having
your only DNS on a machine which is not always running seems a bad idea.
If you already own/run a domain, you can also add a A record in the
DNS for this to point to it - e.g. owncloud.example.com IN A
192.168.0.45.
That would need dynamic DNS if the IP is still obtained via DHCP. And
having a public DNS propagating a private IP will make reverse lookups
impossible, I think. Correct my if I'm wrong.
Using an entry in /etc/hosts is also an option.
This seems the way to make the machine discoverable by name, but would
still need a fixed IP for the owncloud server.
Summarizing, mDNS generally seems to be the easiest way. But if you use
a static IP for your owncloud server you will need to change less with
your current setup, it seems.
Best wishes,
Simon
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/5453890d.8010...@gmail.com
Re: iceweasel Video can't be played because the file is corrupt
On 27/10/14 07:18, Bob Holtzman wrote: Uhh, maybe look yet again. Mine says 24.6.0. To make sure I just ran apt-get update apt-get upgrade with no change to browser or system. I suggest to everyone wanting to know the available versions of some Debian package using packages.debian.org. For iceweasel in all suites: https://packages.debian.org/search?keywords=iceweaselsearchon=namesexact=1 Bye, Simon -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/544df80c.2030...@gmail.com
Re: [exim4] mixed up about terminology
Hello Harry, On 05/10/14 18:01, Harry Putnam wrote: when running `dpkg-reconfigure exim4-config' I've run accross a few of the questions that are confusing to me... The current one I'm stumbling over is 1) A question about listing of host IPs the smtp listener will listen for... All the hosts listed here will be able to send mails to your server. And then later on there is 2) A question about which hosts your server will relay for. All the hosts listed here will be able to send any mail via your server to a remote host, your server is not the destination for the mail. You should leave the relay-list empty unless you really know what you are doing. Mail to remote hosts should generally only be processed for users that have authenticated to your SMTP-server. Hope I could help, Simon -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54317f5f.3000...@gmail.com
Re: [exim4] mixed up about terminology
On 05/10/14 19:26, Simon Hollenbach wrote: 1) A question about listing of host IPs the smtp listener will listen for... All the hosts listed here will be able to send mails to your server. Sorry, Brian is right. I think the config option you refer to is: IP-addresses to listen on for incoming connections ^^ And this just lists the IPs exim4 will listen on for incoming smtp connections. If you have multiple IPs for your server, you could specify only one... Sorry for the confustion, Simon -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/543180ff.9080...@gmail.com
Solution provider for HealthCare
Hi, Would you be interested in acquiring an Email List of Healthcare professionals Email Lists 2014 ? Physicians, Healthcare Staffing , Pharmacies, Hospital Clinics, Biotechnology, Medical Device manufacturers and Nurses,Medical Billing Physicians: Anesthesiology, Cardiology, Chiropractic, Dentist, Emergency Medicine, Family Practice, Gastroenterology, Gynecology, Hematology, Internal medicine, Neurology, Obstetrics/Gynecology, Oncology, Ophthalmology, Optometry, Orthopedic Surgery, Psychiatry, Psychologist, Radiologist etc Let me know your Exact Target Audience that your trying to target , so that I can send you more information. Looking forward to hear from you. Best Regards, Simon Lee Marketing Manager Tel: 302-251-8219 To remove from this mailing: reply with subject line as leave out.
Re: Signature of wheezy's linux source package
On 12/06/2014 21:39, Don Armstrong wrote: On Thu, 12 Jun 2014, Matthias Großmann wrote: after downloading the most recent linux source package for wheezy on my wheezy system, I noticed that dpkg-source fails to verify its signature: [...] I would expect everything required to verify packages in wheezy to be included in wheezy, so I guess this is a bug. Or am I missing something? The keyring in stable is almost never updated, while the keys that are used by developers to sign packages are often updated in the time between the freezing of stable and now. You can either download the newest version of the keyring, or you can use keyring.debian.org. Hi, thanks for explaining this. I am asking myself why the updated debian-keyring package is not available from wheezy-backports repository. Can someone shed some light on this? Regards, Simon -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/539acd44.70...@gmail.com
Re: Signature of wheezy's linux source package
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 13/06/2014 12:44, Andrei POPESCU wrote: On Vi, 13 iun 14, 12:07:00, Simon Hollenbach wrote: I am asking myself why the updated debian-keyring package is not available from wheezy-backports repository. Can someone shed some light on this? I'd say such an update rather qualifies for stable-updates, not backports, but in any case the answer is because nobody is doing it (yet?). You might want to file a wishlist bug against the debian-keyring package, see what the Maintainers think about it. I just filed a wishlist bug for this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751480 I felt like not needing to explain the request in great lengths, if anyone of you can contribute further information, I would really appreciate it. This was just my third(?!) bug report, so I didn't feel really confident while doing this, but it's fine, I guess. Regards, Simon -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBCgAGBQJTmuokAAoJEHF8kGeIE02K5xEP/RY0hiiQz551LimMxa/43+yP u8+ole0+qReJAcQHn6I2uihaAA5YnmgFlqez3HDqF4nPfwTeZvGhl5z2DK5kVVZl D7zmdh2hXO7LjHWEa5bIsKvzq5GLav/jSO81ONB6/+aX/vlwedp5qDuLrIGiFqvv ebIc8379iM26BKhgxr3gqFumHtJGJZeQ55AzDS0MDYhKVNc+AxxBCsJxC99MK5rs IXUDGx8g5a+nRpgICnbU8q3zFlscuzSSo20pVxRgg3j+7ldPFHXXnLqHvJD5/g/l DeKNbigXq3itAjdIRPh/lb6ZEGTYkLmADeAE2L8LcpMMqoYTPwCLm6G5Z3qGAVS/ ccjs8gNnJXoyS+wm2V+flZk2qm31XrIQW70K7+INuT9Ltz0U3vYpc81BGI1bD2S3 9UfARsY92tuZ4tEUWr2bqOS72wUhL5qk+tyywYlQfqKF8dhcZfSybgbJ8ZbbHBF8 Liq0aHjMybyKJcDhA50yq3KPwXuovU8KGhDx69hpElfY1sIY0D2R0AUcij3Ht8yJ indJz+M2OXHW7SxEfqVXNDkDd47zKxcS94+NE7WbnqngdUPlEF0VcXfJ0NPhKYX3 ClIcS1ZA9EMqn1PzusPCs3LHExFmrVDo00aq2Kn1uvvCloB3wQzCL/QZ2jdC8Pat Dqru5Y/KDXhRNaWcpriC =jZMH -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/539aea24.3020...@gmail.com
Re: Signature of wheezy's linux source package
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 13/06/2014 14:16, Andrei POPESCU wrote: On Vi, 13 iun 14, 14:10:12, Simon Hollenbach wrote: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751480 I think it would help if you would mention exactly the issues you had with the package in stable (i.e. the reason an update would be useful). So something like: Integrity/authenticity of linux_3.2.57-3+deb7u2.dsc could not be verified because of missing key, RSA ID 1343CF44, in d-k. ? I would have thought that my statement on $ dpkg-source -x linux[...] failing to verify the package tells the same story, but will append further information to the bug report. Regards, Simon P.S. Andrei, please apologize that I first sent this mail off-list. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBCgAGBQJTmvD+AAoJEHF8kGeIE02KknIP/1wQrUbeW08lf8nwSzyRHPlc tfXZ8CZKxgXZwYfEx60DEaqmuyXP6BhJlj3migX63c9s6yAqrI1OsZPGzLPIjOoH Yt/hqq+ytvrHhDY/5/Cox5ySNgpemN5H5WFFUshe4fTql7QHm+l1/0h7fkX2+Szj dpeyIxULSObmBx8LOINW9510yUt9Qariy3OZN4SMMt711D26vxQu9CkojnbcN/Mh wnv04yT7Zk53DBJbyYRIvB0ksOkIBhtKD1COvjoM2BwBUxWbHs+dTuGpAUmkJoAC ChAQDn00voGtmxwJ9YL8KsKWDHlLZr93O5GCyaZ1KxbzpYdLats6CY5xvyM8oCtU d7Qg4enQBk7msl6hE3Pi5YaPCUecLpu7r1LcTgFCW4ahIctD9SLTCsitpQQBe2KK 9brd6yvNqvpRw3iTWa5gty7Wx8+ifzd23HT6C01jyxnhQbqNdIh+hGkUJkcEM54x tAtP90qWe74YCIJaPjlcG1ENDHzYByg5ZtKISizntSeTlA8NSA1Za84imTEHBw72 Diix+43uGKaS9WkoX1A02kqKNPEO9DPOjpoF3Sr14o/tb3RFp7W7r46NO/zuoJut GZ8DsQdn5OCY7znquXkUfKjGOk5Xi045aiS71FABRRd8/h2Pc4ez0ocdm703d1Xl 2xbvzFfU5hiYAAseh88o =gIoQ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/539af0fe.3040...@gmail.com
Bash completion doesn't prompt files in current directory
Hi all, After yesterday's upgrade, I find that bash's completion rules changed a bit. She doesn't prompt potent files any more if I don't type the first character in file's name (but still prompt all directories). Say when I have a tmp/ and tmp.txt at pwd, $cat then press tab brings only tmp/ Further she fails me when a file's name starts with a ( or [. $cat \[ or $cat [ prompt nothing even as I have a [tmp].txt file. I have not tested other special characters yet. I do want bash going back to old way. I'd like to ask you for how. My bash version is 4.3-2, bash-completion 1:2.1-2
Re: Need help recovering from 'experiment' in firefox
On 1 Dec 2013 19:32, Paul E Condon pecon...@mesanetworks.net wrote: snip / And I cannot open the 'about:blank' page manually. I have all my bookmarkes sites and can use firefox to access the sites I want, but --- I know I have used 'about:blank' in the past when I had other problems with firefox and I was told to go to 'about:blank' and tweek something to get things working again. snip / Hello Paul, I suppose you want to access 'about:config', NOT 'about:blank', to access advanced iceweasel/firefox settings. Cheers, Simon
Re: Hosting advice
On Saturday 02 Nov 2013 12:46:21 Igor Cicimov wrote: May I trouble you good people for suggestions that meet these needs? We would like to have at least one working email address by close of business tomorrow (Friday, 1 November), or Monday at the latest. Thanks, Craig I recommend gandi.net, been using their services for many years now. Very flexible all tech staff, USA data centres if you want. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2281034.FIQTjlzr9D@dragonfly
Re: fsck on boot...revisited
Hi Tim, Back to the original question(s), how can I make this the most robust system (not of all time, but in this use case scenario), both in data integrity and ability to fully boot? I'd set up a system that boots from a read only file system that is all set up to run the services you need. For the sake of simplicity you could use overlayfs or aufs to offer a writable rootfs to the system, just like all the Linux Live CDs do, where all changes to the file system go to RAM and are lost on power loss. As the real root file system is mounted ro, it is never written to and can't get corrupted. In case you need to do local logging you could create a separate partition on your HDD which you mount rw. Then, even if this partition gets totally wrecked your system will still boot up perfectly fine on power loss, so you can connect to it and fix the problems. If you have a reliable network connection, you don't even need that rw logging partition, although it is usually nice to have some persistent storage. - Simon -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/op.w0sddcizixxya5@dellnichtsogutkiste
60 secs freeze with jessie on i7-4770
So today I decided to try debian jessie for a while, but immediately ran into problems. The system will hang for a minute after a couple of hours. Installation is pretty minimal, no desktop, just command line. Linux testbox 3.9-1-amd64 #1 SMP Debian 3.9.8-1 x86_64 GNU/Linux CPU: Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz RAM: 32GiB lspci: 00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 04) 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 04) 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d4) 00:1c.1 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #2 (rev d4) 00:1c.3 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d4) 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation H87 Express LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 04) 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) 03:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 03) last lines of dmesg: [6.262019] r8169 :02:00.0: firmware: agent loaded rtl_nic/rtl8168e-3.fw into memory [6.371077] r8169 :02:00.0 eth0: link down [6.371094] r8169 :02:00.0 eth0: link down [6.371247] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [9.533558] r8169 :02:00.0 eth0: link up [9.533696] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 2400.538060] i2c /dev entries driver [ 2461.805625] CPU1: Package power limit notification (total events = 1) [ 2461.805627] CPU0: Package power limit notification (total events = 1) [ 2461.805628] CPU3: Package power limit notification (total events = 1) [ 2461.805629] CPU7: Package power limit notification (total events = 1) [ 2461.805631] CPU2: Package power limit notification (total events = 1) [ 2461.805632] CPU5: Package power limit notification (total events = 1) [ 2461.805633] CPU6: Package power limit notification (total events = 1) [ 2461.805634] CPU4: Package power limit notification (total events = 1) [ 2461.807602] CPU0: Package power limit normal [ 2461.807603] CPU3: Package power limit normal [ 2461.807604] CPU4: Package power limit normal [ 2461.807604] CPU7: Package power limit normal [ 2461.807605] CPU1: Package power limit normal [ 2461.807606] CPU5: Package power limit normal [ 2461.807607] CPU6: Package power limit normal [ 2461.807608] CPU2: Package power limit normal I didn't post the full startup as it looked pretty normal, so let me know if you need the full output, or any other information. Any ideas what might be going on there? I also installed jessie on a different box with a Core i5, no problems there yet.. - Simon -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/op.w0lc6k05ixxya5@zahlpc.local
unsuscribe
-- Antonio Guzmán Simón Mov.: 605 21 48 96
Grub Loading software raid.
Hello folks, I have built a system with Debian software RAID-1 and everything works great until you pull a drive and try to boot, the system just hangs at Grub loading If I pop the drive back in the system will boot normally then do # mdadm /dev/md0 -a /dev/sdb it adds the drive and begins the rebuild, as shown by cat /proc/mdstat I installed the boot loader to the second drive by doing # grub-install /dev/sdb Then checked the disks; # fdisk -l Disk /dev/sda: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x000a1072 Device Boot Start End Blocks Id System /dev/sda1 1 121602 976760832 fd Linux raid autodetect Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x000a4dbb Device Boot Start End Blocks Id System /dev/sdb1 1 121602 976760832 fd Linux raid autodetect But still when I remove the drive it just hangs at Grub loading and doesn't go any further, what am I doing wrong? Thanks. - Simon. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/C1ABE3AA84CD964DB07F21189E2C4BF99E3DFD86@ALTERNATEREALIT.thematrix.local
(Re-)Mounting random crypto disk - how to create file system?
Hello. I set up an encrypted partition with randomly regenerated password that I want to mount at /tmp with some older(6w) wheezy netinstall. Apparently I need to create a file system there before mounting on every boot, don't I? I wrote myself a little mount script, that: Tries to mount (mount /dev/mapper/sda2_crypt /tmp ) Failing:ensures umount, calls mkfs.ext3 and retries mount without failure check. I plan on running this while booting, but don't know at which runlevel. Help? But I am now asking myself if I need it or if I overlook some handy option with mtab or cryptsetup or..? Any input is highly appreciated, thanks for reading. Kind Regards, Simon
Re: RAID1 all bootable
Hi Francesco, I was under the impression your grub configuration was correct and the only thing wrong was not having it installed on that one HDD. Of course your grub configuration should point to the correct root. In my little (easy) setup I have my main partition, boot partition and swap partition in raid-1. The update-grub command was able to create the correct entries for this configuration in my grub.cfg all by itself. If grub is sending you to the rescue prompt it means something it wrong with your grub configuration, so you'll have to fix that and install grub again. With kind regards, Simon On Mar 3, 2013 8:48 AM, Francesco Pietra chiendar...@gmail.com wrote: Hi Lennart, Hi Simon A proper understanding of mdadm is required. Hurrying with focus on codes for biochemical applications has brought me into a mess. Relying of all my data, and special compiled programs, present on another raid1 amd64 wheezy, I carried out a reinstall of amd64 wheezy on the machine with new HD. mdo (boot, ext20, md1 (LVM, home, usr, etc). GRUB was installed on /dev/sda Then the command grub-install /dev/sdb with reported installation compete. No errors reported. On rebooting, GRUB was no more found, entering in grub rescue which should also be known accurately, because prefix/root/ are now wrong. The only care I exerted, was not to work with the machine where I have my data, until the damaged machine is in order again. At any event, how to install safely GRUB on both disks of a RAID1 is a must. Thanks for your kind advice. francesco pietra As to mdadm, On Sat, Mar 2, 2013 at 7:05 AM, Simon Vos simon...@gmail.com wrote: Have you assembled you raid devices again (mdadm --assemble /dev/mdX /dev/sdX)? That should still work with the disk that was used for your RAID-1, when that's done you can mount your disk, chroot into it and run grub-install /dev/sda (and grub-install /dev/sdb, so you won't have this problem in the future ;-)). On 2 March 2013 11:10, Francesco Pietra chiendar...@gmail.com wrote: A further piece on information. With knoppix 7.0, the procedure for examining mdadm arrives at cat /proc/partitions sda sdb RAID1 (md0 md1) is not seen. I assume that this is the way Knoppix behaves in this situation. Thanks francesco pietra -- Forwarded message -- From: Francesco Pietra chiendar...@gmail.com Date: Sat, Mar 2, 2013 at 10:11 AM Subject: Re: RAID1 all bootable To: Lennart Sorensen lsore...@csclub.uwaterloo.ca, amd64 Debian debian-am...@lists.debian.org, debian-users debian-user@lists.debian.org Is this recipe devised for installing grub on both sda and sda with an undamaged RAID1? In my case, with the sda that contained grub loader replaced by a new disk, the rescue mode (using the same CD installer for amd64 wheezy) did not find any partition. Inverting the SATA cables, same result. In both cases (I mean position of SATA cables) I went to the shell in the installer environment: #fisk /dev/sda (or sdb) device contains neither a valid DOS partition table, nor Sun, etc (expected for a raid) #dmesg |grep -i sd sda (and sbb): unknown partition table (expected for a raid), however md: raid0 md: raid1 were identified, along with rai4, 5, 6 etc (unfortunately | less does not work to see the whole message). Am I using the Rescue Mode improperly? I was unable to dig into the HD that contains md0 (booth loader, EXT2) and md1 ( LVM partitions home tmp usr opt var swap EXT3) Thanks a lot for your kind advice francesco pietra On Fri, Mar 1, 2013 at 10:35 PM, Lennart Sorensen lsore...@csclub.uwaterloo.ca wrote: On Fri, Mar 01, 2013 at 08:20:09PM +0100, Francesco Pietra wrote: Hi: With a raid1 amd64 wheezy, one of the two HDs got broken. Unfortunately, I had added grub to sda only, which is just the one broken. So that, when it is replaced with a fresh HD, the OS is not found. Inverting the SATA cables of course does not help (Operative System Not Found). In a previous similar circumstance, I was lucky that the broken HD was the one without gru. Is any way to recover? perhaps through Knoppix? I know how to look into undamaged RAID1 with Knoppix. Also, when making a fresh RAID1 from scratch, where to find a Debian description of how to make both sda and sdb bootable? (which should be included by default, in my opinion) You can boot the install disk in rescue mode, select the root partition to chroot into, then run grub-install from there. When grub asks where to install, you should configure it for both sda and sdb. I think 'dpkg-reconfigure grub-pc' is where that is selected. Might need it to use -plow to asks all levels of questions. Not sure. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject
Re: RAID1 all bootable
Have you assembled you raid devices again (mdadm --assemble /dev/mdX /dev/sdX)? That should still work with the disk that was used for your RAID-1, when that's done you can mount your disk, chroot into it and run grub-install /dev/sda (and grub-install /dev/sdb, so you won't have this problem in the future ;-)). On 2 March 2013 11:10, Francesco Pietra chiendar...@gmail.com wrote: A further piece on information. With knoppix 7.0, the procedure for examining mdadm arrives at cat /proc/partitions sda sdb RAID1 (md0 md1) is not seen. I assume that this is the way Knoppix behaves in this situation. Thanks francesco pietra -- Forwarded message -- From: Francesco Pietra chiendar...@gmail.com Date: Sat, Mar 2, 2013 at 10:11 AM Subject: Re: RAID1 all bootable To: Lennart Sorensen lsore...@csclub.uwaterloo.ca, amd64 Debian debian-am...@lists.debian.org, debian-users debian-user@lists.debian.org Is this recipe devised for installing grub on both sda and sda with an undamaged RAID1? In my case, with the sda that contained grub loader replaced by a new disk, the rescue mode (using the same CD installer for amd64 wheezy) did not find any partition. Inverting the SATA cables, same result. In both cases (I mean position of SATA cables) I went to the shell in the installer environment: #fisk /dev/sda (or sdb) device contains neither a valid DOS partition table, nor Sun, etc (expected for a raid) #dmesg |grep -i sd sda (and sbb): unknown partition table (expected for a raid), however md: raid0 md: raid1 were identified, along with rai4, 5, 6 etc (unfortunately | less does not work to see the whole message). Am I using the Rescue Mode improperly? I was unable to dig into the HD that contains md0 (booth loader, EXT2) and md1 ( LVM partitions home tmp usr opt var swap EXT3) Thanks a lot for your kind advice francesco pietra On Fri, Mar 1, 2013 at 10:35 PM, Lennart Sorensen lsore...@csclub.uwaterloo.ca wrote: On Fri, Mar 01, 2013 at 08:20:09PM +0100, Francesco Pietra wrote: Hi: With a raid1 amd64 wheezy, one of the two HDs got broken. Unfortunately, I had added grub to sda only, which is just the one broken. So that, when it is replaced with a fresh HD, the OS is not found. Inverting the SATA cables of course does not help (Operative System Not Found). In a previous similar circumstance, I was lucky that the broken HD was the one without gru. Is any way to recover? perhaps through Knoppix? I know how to look into undamaged RAID1 with Knoppix. Also, when making a fresh RAID1 from scratch, where to find a Debian description of how to make both sda and sdb bootable? (which should be included by default, in my opinion) You can boot the install disk in rescue mode, select the root partition to chroot into, then run grub-install from there. When grub asks where to install, you should configure it for both sda and sdb. I think 'dpkg-reconfigure grub-pc' is where that is selected. Might need it to use -plow to asks all levels of questions. Not sure. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caev0nmtmhadi2e_uk+wf+c0k9d1ygn3tv91jsr4g2ppp5_a...@mail.gmail.com
Re: exchange like alternative
On Wed, 5 Dec 2012 16:34:13 +0100 Olivier BATARD obat...@gmail.com wrote: That's a great idea I'll write a tutorial about that. snip / Hello Olivier, If you write a tutorial about your groupware-like setup, I would really appreciate a follow-up to this thread from you, providing me/us with a link to said howto. Thanks, Simon -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121207084234.7e9f9...@fr13dn4nd.home.co0n
Re: UEFI install
On 27/11/2012 20:50 Erwan David wrote: I got a new Lenovo T530, I added a SSD as second disk, and now have a win7, UEFI boot on MBR partitionned sdb disk. I tried latest beta installer for wheezy (beta4), but it could not boot in UEFI mode (I got a text menu writtent on the right of the screen, then after selecting an entry Error, no suitable mode found, then reboot...) Is there a way for me to install a debian double boot without first reinstalling the windows ? I recently had a simliar problem. I managed to install Debian by changing in the bios the boot method from UEFI the Legacy BIOS. Once Debian was up and running, I replaced the normal grub with grub-efi, changed the bios setting back to UEFI boot, and dual boot works now pretty good. Cheers, Simon -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/k936h3$7tf$1...@news.albasani.net
After updating wheezy, sound card not properly recognized anymore
Hi,
after installing automatic updates a few weeks ago for my wheezy box,
sound disappeared. I'm using the box only occasionally and didn't
immediately try to figure out what's wrong - I assumed the next update
would fix it. Sadly, I'm still without sound. (That is one kernel update
later.)
First I checked that nothing is muted and that all sound output is at
maximum. Doing that I noticed in the sound settings (little speaker
symbol in the top right hand corner of gnome, then sound settings) that
only a dummy output device is listed. That's probably bad. I'm using the
onboard sound of the Gigabyte GA-Z68XP-UD4 mainboard with Intel Z68
Express Chipset. The specs say it should be using the Realtek ALC889 codec.
Next I checked whether modules are loaded (as far as I can see, they
are; lsmod output is further below) and whether the speakers work (they do).
Then I started to google for debugging howtos and possible fixes. Most
of what I found suggested to write something like
pcm.!default {
type hw
card 0
device 0
}
ctl.!default {
type hw
card 0
device 0
}
into ~.asoundrc or into /etc/asoundrc. None of those existed but
creating them (and testing different card/devices values) didn't work.
On the upside I learned about aplay and speaker-test (see output below)
which seem to indicate that the sound isn't going to the correct device.
Another suggestion was to use alsa-info.sh to gather information about
the current alsa configuration. Unfortunately, I couldn't find the
script. Which package does it belong to? Has it been replaced with
something newer? Or do I have to download it manually from the alsa
project webpage?
I'm not a Linux pro and this is as far as I got. Any help to fix the
issue would be appreciated.
Best, Simon
~$ aplay -l
List of PLAYBACK Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC889 Analog [ALC889 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 1: ALC889 Digital [ALC889 Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
~$ aplay -L
null
Discard all samples (playback) or generate zero samples (capture)
pulse
PulseAudio Sound Server
default:CARD=PCH
HDA Intel PCH, ALC889 Analog
Default Audio Device
sysdefault:CARD=PCH
HDA Intel PCH, ALC889 Analog
Default Audio Device
front:CARD=PCH,DEV=0
HDA Intel PCH, ALC889 Analog
Front speakers
surround40:CARD=PCH,DEV=0
HDA Intel PCH, ALC889 Analog
4.0 Surround output to Front and Rear speakers
surround41:CARD=PCH,DEV=0
HDA Intel PCH, ALC889 Analog
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=PCH,DEV=0
HDA Intel PCH, ALC889 Analog
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=PCH,DEV=0
HDA Intel PCH, ALC889 Analog
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=PCH,DEV=0
HDA Intel PCH, ALC889 Analog
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=PCH,DEV=0
HDA Intel PCH, ALC889 Digital
IEC958 (S/PDIF) Digital Audio Output
hdmi:CARD=Generic,DEV=0
HD-Audio Generic, HDMI 0
HDMI Audio Output
speaker-test results in a nutshell:
null | fail
pulse | fail
default| OK
sysdefault | OK
front | fail
surround40 | fail
surround41 | fail
surround50 | OK
surround51 | fail
surround71 | fail
iec958 | fail
hdmi | fail
(Please see the attachment for all speaker-test output.)
~$ uname -a
Linux Stoertebecker 3.2.0-4-amd64 #1 SMP Debian 3.2.32-1 x86_64 GNU/Linux
~$ lspci | grep Audio
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset
Family High Definition Audio Controller (rev 05)
01:00.1 Audio device: Advanced Micro Devices [AMD] nee ATI
Turks/Whistler HDMI Audio [Radeon HD 6000 Series]
~$ sudo lspci -s 00:1b.0 -vv
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset
Family High Definition Audio Controller (rev 05)
Subsystem: Giga-byte Technology Device a132
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort-
MAbort- SERR- PERR- INTx-
Latency: 0, Cache Line Size: 4 bytes
Interrupt: pin A routed to IRQ 46
Region 0: Memory at fbff8000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: feeff00c Data: 4199
Capabilities: [70] Express (v1) Root Complex Integrated Endpoint, MSI 00
Re: After updating wheezy, sound card not properly recognized anymore
-BEGIN PGP SIGNED MESSAGE- Hash: SHA224 On 09/11/12 10:47, Ralf Mardorf wrote: Check your DE's Pulseaudio settings too. Hi, Using PulseAudio Volume control: Nothing is muted, all volume settings are 100%. But it lists Dummy Output as output device. Using PulseAudio Manager: As sink only auto_null (Description - Dummy Output) is listed and when I play music (e.g. from Rhythmbox) it is listed for that sink and the volume meters are active, indicating the music to be played. Server Information: Server Name: pulseaudio Server Version: 2.0 Default Sample Type: s16le 2ch 44100Hz Host Name: [ok] Use Name:simon Default Sink:auto_null Default Source: auto_null.monitor Client Information: Linked to Library Version: 2.0.0 Compiled with Library Version: 0.9.8 The client information looks odd to me. I've attached the pulse configuration files. In the .conf files, everything seems to be commented out. I've had a quick look at the .pa files but decided I better not mess with them. Best, Simon -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iFYEARELAAYFAlCc5gQACgkQE8ykjYCSVs4+bQDfY83rPniGlOHvmyV95i+VxJCf syE7JK7q5j9rbQDbBa8R+NSx3Pl9/D9E78/2ExVoETmfAZpzFWJhqQ== =OeTg -END PGP SIGNATURE- # This file is part of PulseAudio. # # PulseAudio is free software; you can redistribute it and/or modify # it under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version. # # PulseAudio is distributed in the hope that it will be useful, but # WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU # General Public License for more details. # # You should have received a copy of the GNU Lesser General Public License # along with PulseAudio; if not, write to the Free Software # Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 # USA. ## Configuration file for PulseAudio clients. See pulse-client.conf(5) for ## more information. Default values are commented out. Use either ; or # for ## commenting. ; default-sink = ; default-source = ; default-server = ; default-dbus-server = ; autospawn = yes ; daemon-binary = /usr/bin/pulseaudio ; extra-arguments = --log-target=syslog ; cookie-file = ; enable-shm = yes ; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 MiB ; auto-connect-localhost = no ; auto-connect-display = no # This file is part of PulseAudio. # # PulseAudio is free software; you can redistribute it and/or modify # it under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version. # # PulseAudio is distributed in the hope that it will be useful, but # WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU # General Public License for more details. # # You should have received a copy of the GNU Lesser General Public License # along with PulseAudio; if not, write to the Free Software # Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 # USA. ## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for ## more information. Default values are commented out. Use either ; or # for ## commenting. ; daemonize = no ; fail = yes ; allow-module-loading = yes ; allow-exit = yes ; use-pid-file = yes ; system-instance = no ; local-server-type = user ; enable-shm = yes ; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 MiB ; lock-memory = no ; cpu-limit = no ; high-priority = yes ; nice-level = -11 ; realtime-scheduling = yes ; realtime-priority = 5 ; exit-idle-time = 20 ; scache-idle-time = 20 ; dl-search-path = (depends on architecture) ; load-default-script-file = yes ; default-script-file = /etc/pulse/default.pa ; log-target = auto ; log-level = notice ; log-meta = no ; log-time = no ; log-backtrace = 0 ; resample-method = speex-float-3 ; enable-remixing = yes ; enable-lfe-remixing = no ; flat-volumes = yes ; rlimit-fsize = -1 ; rlimit-data = -1 ; rlimit-stack = -1 ; rlimit-core = -1 ; rlimit-as = -1 ; rlimit-rss = -1 ; rlimit-nproc = -1 ; rlimit-nofile = 256 ; rlimit-memlock = -1 ; rlimit-locks = -1 ; rlimit-sigpending = -1 ; rlimit-msgqueue = -1 ; rlimit-nice = 31 ; rlimit-rtprio = 9 ; rlimit-rttime = 100 ; default-sample-format = s16le ; default-sample-rate = 44100 ; alternate-sample-rate = 48000 ; default-sample-channels = 2 ; default-channel-map = front-left,front-right ; default-fragments = 4 ; default-fragment-size-msec = 25 ; enable-deferred-volume = yes ; deferred-volume-safety-margin-usec = 8000 ; deferred-volume-extra-delay-usec = 0 #!/usr/bin/pulseaudio -nF
Re: Comment ralentir la bande passante.
Avec les cgroups on peut (avec un kernel assez recent) Le 19/09/2012 09:34, Sébastien NOBILI a écrit : Le mardi 18 septembre 2012 à 18:02, Gerald a écrit : Tout est dans le titre... J'ai récemment découvert iprelay qui a le mérite d'être simple à configurer. Il fait proxy vers un port d'une machine et ralentit le débit. Seb smime.p7s Description: S/MIME Cryptographic Signature
squid on other box than iptables NAT?
Hi group, I thought I could run squid (3.1.20) on one box, and iptables with DNAT on another box with iptables -t nat -A PREROUTING -p tcp --dport 80 -i $LOCIF ! -s $squidbox ! -d $localnet -j DNAT --to-destination $squidbox:3128 squid.conf snip: http_port 192.x.x.x:3128 intercept But on the squidbox /var/var/log/squid3/cache.log says: IpIntercept.cc(137) NetfilterInterception: NF getsockopt(SO_ORIGINAL_DST) failed on FD 45: (92) Protocol not available Some manuals on the internet suggest that this setup should be possible [1], while others claim squid must run on the same box performing NAT [2]. Can anybody help me out with this? Cheers, Simon [1] http://tldp.org/HOWTO/TransparentProxy-6.html [2] http://squid-web-proxy-cache.1019090.n4.nabble.com/external-NAT-and-quot-Protocol-not-available-quot-td3173494.html -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/k37ctf$s3o$1...@news.albasani.net
Re: EeePC and Debian
Chen Wei weichen302 at aol.com writes: it could be a video model problem, try press TAB and custom the boot option, *avoid* any fancy vga= parameter. My 4g was hanging on the install screen as soon as I chose an install option. Your solution sorted it out, I changed the vga parameter to vga=766 - which I got from one of the debian eeepc pages. Thank you. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/loom.20120731t005652-...@post.gmane.org
Re: Backup2l config
Hi, On 11/5/2012 11:30 Bastien Rocheron wrote: I'm trying to backup a directory with backup2l and I don't understand the 'Backup parameters'. I don't understand the levels, max full backups... because with the current settings I end up with my disk filled very quickly. The directory is 1GB approx and every day backup2l eats up another GB so I guess this is not quite differential. What about the man page: The method of hierarchical differential backups is a generalization to the concept of the daily, weekly and monthly backups. Each backup has a level and a serial number. Maximum-level backups are comparable with daily differential backups, level-0 backups are full backups. For example, let MAX_LEVEL be 4 and MAX_PER_LEVEL be 5. After 5 level-4 backups (e. g. after 5 days), a new level-3 backup is made. After 5 level-3 backups (and 5*5 at level-4), a new level-2 backup is made, and so on. Each differential backup contains the changes towards the previous backup of the same or a lower level. Cheers, Simon -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jojh4f$q54$1...@news.albasani.net
Re: When will Debian 7.0 with Linux Kernel 3.x be Released?
On 27/3/2012 07:10 Teo En Ming (Zhang Enming) wrote: When will Debian 7.0 be released? When it's done. SCNR. Simon -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jkv95k$6ij$1...@news.albasani.net
Re: Gnome3 login failure
Jon Dowland jmtd at debian.org writes: On 24/01/12 14:56, Richard wrote: Out of the blue, when I try to login to the shell I get after a few second that dreaded something has gone wrong message and to logout. Is Gnome3 similar in behaviour to Gnome2 that removing the .gnome files will cause them to be recreated on login ? Or any other ideas ??? Can you use the GNOME classic session? Can a freshly-created test user use the normal GNOME session? Me too. I fixed it by editing /etc/profile. It seems that one of the commands did not complete successfully. When I disabled it, I could login successfully again. Normal logins did not suffer from this problem. Simon -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/loom.20120126t105432-...@post.gmane.org
Re: [Xen-users] debian squeeze, xen and a very big problem.
Mauro wrote: I can't believe that a serious distribution like debian do not do tests before suggest an upgrade. As Scott says, for production systems you either have to test things yourself, or you accept that possibly an upgrade may break your system. Debian (and the other distributions) do do a **LOT** of testing - they have a whole QA setup just to handle testing etc. BUT they rely on the package maintainers/contributors to do most of the functional testing - the distribution testing is (I believe) mostly to ensure everything installs cleanly, there aren't broken dependencies, etc. The thing is, once you get past the trivial (and both the Linux kernel and Xen are very much non-trivial) it is simply impossible to test every possible combination of software and usage cases. That's not difficult, but impossible - unless you have a near infinite number of systems and people to run the test scenarios. I understand how frustrating it is for you, I've been hit by this sort of thing before. You either have to have a test/QA setup and test all upgrades before going live, or you upgrade live systems and have a plan to backtrack what you upgraded. The last one I had was an incompatibility between (IIRC) Squirrelmail and (IIRC) one of the Perl elements it depends on - leading to inability to log in as a user. I had to downgrade the bits I'd upgraded, then upgrade them one at a time until I found the problem. Fortunately it got fixed at some point. Guy Roussin wrote: Use http://snapshot.debian.org/ Wow, I wish I'd known about that before - several times I've found myself needing older packages and struggled to find them. -- Simon Hobson Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed author Gladys Hobson. Novels - poetry - short stories - ideal as Christmas stocking fillers. Some available as e-books. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/p06240844cabd8ed63...@simon.thehobsons.co.uk
Re: usb failure
On 10/9/2011 17:30 Gareth de Vaux wrote: Hi guys, I've been having usb issues on and off for about 2 years with my SUN W1100z workstation. The keyboard, mouse, flash stick etc. are all currently unresponsive. (The machine only has usb ports, all of which I've tried). Maybe related to: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634023 Cheers, Simon -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/j4hrb5$dpc$1...@news.albasani.net
Re: nano and color
On 08/09/11 20:22, Bonno Bloksma wrote: Hi, When using nano on a Squeeze system and I open a file with name.sh I will see color coded script Lines. When I open a file line name.xxx with the same content there is no color coding. On a Lenny system I never have color coding. 1) Where is this behaviour defined on my Squeeze system? 2) Can I enable it on my Lenny systems? Bonno Bloksma I am not fully aware of the details regarding nano(1) operation, and I believe the secret lies in the configuration files which reside in /usr/share/nano/ that may be referenced from /etc/nanorc. You may also learn more from manpage nanorc(5). I have copied the files from one system to another using scp(1) previously. -- Simon Tibble si...@tibble.net -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e6a5ae8.5020...@tibble.net
Re: Re: demande d'aide
-- KORNOG computing Simon TOSSER TEL. +33(0)2 98 63 25 74 GSM. +33(0)6 61 46 30 99 FAX: +33(0)2 98 63 25 74 Web: http://www.kornog-computing.com Mail: si...@kornog-computing.com JabberID: si...@kornog-computing.com 26b rue d'Aiguillon 29600 Morlaix France Siren: 479 230 252 Pensez environnement ! N'imprimez ce mail que si c'est vraiment nécessaire L'integrite de ce message n'etant pas assuree sur internet, KORNOG computing ne peut etre tenu responsable de son contenu. Toute utilisation ou diffusion non autorisee est interdite. Si vous n'etes pas destinataire de ce message, merci de le detruire et d'avertir l'expediteur. The integrity of this message cannot be guaranteed on the Internet. KORNOG computing can not therefore be considered responsible for the contents. Any unauthorized use or dissemination is prohibited. If you are not the intended recipient of this message, then please delete it and notify the sender.-- signature.asc Description: This is a digitally signed message part
Re: history
On 03/09/11 00:05, shawn wilson wrote:
what does this mean:
706 perl -e '$str = a b c; my $a = /(\s+)/; print $a\n;'
707* perl -e '$str = a b c; my $a = /(\s+)/; print $a\n;'
708 perl -e '$str = a; (my $a, $b = $str) =~ /{.)(.)/ ? ( $1, $2
) : ( $_, $_ ); print $a\n;'
ie, 707* - i've never seen this before.
btw, i don't remember wtf i was trying to do here so pay no attention
to my code :)
When using the history(3) command to display command line history in
bash(1) a sequential listing appears. On your line 707, the asterisk
* is present to indicate the line was modified before execution.
(Ref: Manual page bash(1) line 2598)
--
Simon Tibble
si...@tibble.net
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4e61f1d0.7040...@tibble.net
disappeared hard disk space
Hi, all. I need your help to find out what happened to my hard disk. The problem I've met is according to the used space in my /dev/sda8, there should be 6G left. But there's only 1G now. I can't move a file larger to 1G to that partition. Tried, but failed. I've also run some test and repairs. Unfortunately nothing's changed. Now I show you the results. deva@kyley:~$ df -h FilesystemSize Used Avail Use% Mounted on /dev/sda3 9.2G 7.3G 1.5G 84% / tmpfs 5.0M 0 5.0M 0% /lib/init/rw tmpfs 200M 872K 199M 1% /run udev 992M 0 992M 0% /dev tmpfs 399M 84K 399M 1% /run/shm /dev/sda4 184M 32M 143M 19% /boot /dev/sda6 5.0G 1.8G 3.0G 38% /home /dev/sda8 91G 85G 937M 99% /home/deva/iwish /dev/sda1 9.4G 6.1G 3.3G 66% /home/deva/deka /dev/sda5 33G 30G 2.6G 93% /home/deva/kon deva@kyley:~$ df -h /dev/sda8 FilesystemSize Used Avail Use% Mounted on /dev/sda8 91G 85G 937M 99% /home/deva/iwish root:/home/deva# du -sh iwish/ 85Giwish/ root:/home/deva# umount iwish/ root:/home/deva# e2fsck -f /dev/sda8 e2fsck 1.42-WIP (02-Jul-2011) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information Iwish: 89788/6012928 files (2.0% non-contiguous), 22591653/24033024 blocks root:/home/deva# parted /dev/sda8 GNU Parted 2.3 Using /dev/sda8 Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) print Model: Unknown (unknown) Disk /dev/sda8: 98.4GB Sector size (logical/physical): 512B/512B Partition Table: loop Number Start End SizeFile system Flags 1 0.00B 98.4GB 98.4GB ext4 root:/home/deva# cat /etc/mtab | grep sda8 /dev/sda8 /home/deva/iwish ext4 rw 0 0 5G space's just vanished. It cannot be journal. At least before yesterday sum of used and free sizes always equaled total size, refered to df. So far as I could recall, the mistake may be that I deleted a directory in that partition when a extraction of files was running unnoticed into the same directory. Anyhow it was deleted afterwards. -- Mit freundlichen Grüßen Zichen Chen
oss4-dkms failed after upgrade to kernel 3.0
I was a little surprised kernel3.0 came to wheezy so quickly.
Anyway, after I upgraded from 2.6.39-2-686-pae to 3.0.0-1-686-pae, I got the
scarlet error message:
Unloading Open Sound System kernel modules: done (OSS not loaded).
Starting Open Sound System: failed (No kernel modules detected).
When refered to
/var/lib/dkms/oss4/4.2-build2004/3.0.0-1-686-pae/i686/module, however, oss
module files were all there. Nothing important looked wrong in make.log
neither. I tried copying all .ko files to /lib/modules, didn't work.
--
Mit freundlichen Grüßen
Zichen Chen
DKMS make.log for oss4-4.2-build2004 for kernel 3.0.0-1-686-pae (i686)
Wed Aug 10 18:28:54 CEST 2011
make: Entering directory `/usr/src/linux-headers-3.0.0-1-686-pae'
CC [M] /var/lib/dkms/oss4/4.2-build2004/build/core/oss_core.o
/var/lib/dkms/oss4/4.2-build2004/build/core/oss_core.c: In function ‘alloc_fop’:
/var/lib/dkms/oss4/4.2-build2004/build/core/oss_core.c:964:14: warning: assignment from incompatible pointer type
/var/lib/dkms/oss4/4.2-build2004/build/core/oss_core.c: In function ‘oss_pci_read_devpath’:
/var/lib/dkms/oss4/4.2-build2004/build/core/oss_core.c:1638:3: warning: return discards qualifiers from pointer target type
/var/lib/dkms/oss4/4.2-build2004/build/core/oss_core.c: In function ‘oss_cmn_err’:
/var/lib/dkms/oss4/4.2-build2004/build/core/oss_core.c:675:1: warning: the frame size of 1056 bytes is larger than 1024 bytes
CC [M] /var/lib/dkms/oss4/4.2-build2004/build/core/os_linux.o
CC [M] /var/lib/dkms/oss4/4.2-build2004/build/core/oss_ac97.o
CC [M] /var/lib/dkms/oss4/4.2-build2004/build/core/oss_audio_core.o
CC [M] /var/lib/dkms/oss4/4.2-build2004/build/core/oss_audiofmt.o
CC [M] /var/lib/dkms/oss4/4.2-build2004/build/core/oss_grc3.o
CC [M] /var/lib/dkms/oss4/4.2-build2004/build/core/oss_spdif.o
CC [M] /var/lib/dkms/oss4/4.2-build2004/build/core/oss_default_timer.o
CC [M] /var/lib/dkms/oss4/4.2-build2004/build/core/oss_midi_core.o
CC [M] /var/lib/dkms/oss4/4.2-build2004/build/core/oss_midi_mapper.o
CC [M] /var/lib/dkms/oss4/4.2-build2004/build/core/oss_midi_parser.o
CC [M] /var/lib/dkms/oss4/4.2-build2004/build/core/oss_midi_queue.o
CC [M] /var/lib/dkms/oss4/4.2-build2004/build/core/oss_midi_timers.o
CC [M] /var/lib/dkms/oss4/4.2-build2004/build/core/oss_midi_stubs.o
CC [M] /var/lib/dkms/oss4/4.2-build2004/build/core/oss_mixer_core.o
CC [M] /var/lib/dkms/oss4/4.2-build2004/build/core/oss_core_options.o
CC [M] /var/lib/dkms/oss4/4.2-build2004/build/core/oss_core_services.o
CC [M] /var/lib/dkms/oss4/4.2-build2004/build/core/oss_memblk.o
CC [M] /var/lib/dkms/oss4/4.2-build2004/build/core/oss_remux.o
CC [M] /var/lib/dkms/oss4/4.2-build2004/build/core/oss_sndstat.o
CC [M] /var/lib/dkms/oss4/4.2-build2004/build/core/oss_uart401.o
CC [M] /var/lib/dkms/oss4/4.2-build2004/build/core/vmix_core.o
CC [M] /var/lib/dkms/oss4/4.2-build2004/build/core/vmix_input.o
/var/lib/dkms/oss4/4.2-build2004/build/core/vmix_input.c: In function ‘vmix_record_callback’:
/var/lib/dkms/oss4/4.2-build2004/build/core/vmix_input.c:320:1: warning: the frame size of 1068 bytes is larger than 1024 bytes
CC [M] /var/lib/dkms/oss4/4.2-build2004/build/core/vmix_output.o
/var/lib/dkms/oss4/4.2-build2004/build/core/vmix_output.c: In function ‘vmix_play_callback’:
/var/lib/dkms/oss4/4.2-build2004/build/core/vmix_output.c:471:1: warning: the frame size of 1068 bytes is larger than 1024 bytes
LD [M] /var/lib/dkms/oss4/4.2-build2004/build/core/osscore.o
Building modules, stage 2.
MODPOST 1 modules
CC /var/lib/dkms/oss4/4.2-build2004/build/core/osscore.mod.o
LD [M] /var/lib/dkms/oss4/4.2-build2004/build/core/osscore.ko
make: Leaving directory `/usr/src/linux-headers-3.0.0-1-686-pae'
make: Entering directory `/var/lib/dkms/oss4/4.2-build2004/build/drivers'
echo static const struct modversion_info versions[] osscore_symbols.inc
echo __attribute__((used)) osscore_symbols.inc
echo __attribute__((section(\__versions\))) = { osscore_symbols.inc
sed -e s:^:{: -e s:\t:, \: -e s:\t\(.\)*:\},: Module.symvers osscore_symbols.inc
echo }; osscore_symbols.inc
make: Leaving directory `/var/lib/dkms/oss4/4.2-build2004/build/drivers'
make: Entering directory `/usr/src/linux-headers-3.0.0-1-686-pae'
CC [M] /var/lib/dkms/oss4/4.2-build2004/build/drivers/oss_ali5455driver.o
CC [M] /var/lib/dkms/oss4/4.2-build2004/build/drivers/oss_ali5455module.o
/var/lib/dkms/oss4/4.2-build2004/build/drivers/oss_ali5455module.c: In function ‘osspci_probe’:
/var/lib/dkms/oss4/4.2-build2004/build/drivers/pci_wrapper.inc:54:21: warning: ignoring return value of ‘pci_enable_device’, declared with attribute warn_unused_result
In file included from /var/lib/dkms/oss4/4.2-build2004/build/drivers/oss_ali5455module.c:21:0:
/var/lib/dkms/oss4/4.2-build2004/build/drivers/module.inc: In function ‘oss_cmn_err’:
/var/lib/dkms/oss4/4.2-build2004/build/drivers/module.inc:243:1: warning: the frame size of 1068 bytes is
