Re: How to disable automatic core dumps in Debian 9?
Reco, thanks for reply! > rgrep core /etc/security/limits* > Would be more correct. Files at /etc/security/limits.d/ can override > limits.conf. Indeed. Output of "rgrep core /etc/security/limits*" is following: $ rgrep core /etc/security/limits* /etc/security/limits.conf:#- core - limits the core file size (KB) /etc/security/limits.conf:* hardcore0 /etc/security/limits.conf:roothardcore0 /etc/security/limits.conf:#roothardcore10 $ So in short, the configuration in my initial e-mail was enough to disable core dumps? After reading the "man 5 core", I also set the "kernel.core_uses_pid" to 0. thanks, Martin
How to disable automatic core dumps in Debian 9?
Hi, how to disable all automatic core dumps upon the process termination in Debian 9? As Debian does not seem to use systemd-coredump, then I set the "kernel.core_pattern=|/bin/false" kernel configuration in sysctl.conf and following pam_limits.so module configuration: $ grep -w core /etc/security/limits.conf #- core - limits the core file size (KB) * hardcore0 roothardcore0 #roothardcore10 $ When I execute a program, which crashes, then while the "core dumped" is printed: $ ./testprogram Floating point exception (core dumped) $ ..then no actual core dump does not seem to be created. Is the configuration above enough to disable core dumps or am I missing something? thanks, Martin
Re: unattended-upgrades downloaded package information only from the sources in sources.list.d directory ignoring sources.list file
Hi, looks like the culprit is a /etc/cron.daily/do-agent cron-job which executes the /opt/digitalocean/do-agent/scripts/update.sh script which includes following if statement: if command -v apt-get 2&>/dev/null; then apt-get -qq update -o Dir::Etc::sourcelist="sources.list.d/digitalocean-agent.list" -o Dir::Etc::sourceparts="-" -o APT::Get::List-Cleanup="1" apt-get -qq install -y --only-upgrade do-agent /* output removed for brevity */ '-o APT::Get::List-Cleanup="1"' flushes other repositories.. Martin
Re: unattended-upgrades downloaded package information only from the sources in sources.list.d directory ignoring sources.list file
> I did some further debugging and it is the > /usr/lib/apt/apt.systemd.daily script executed by apt-daily systemd > service unit which updates the package index from the sources: I configured cron with one minute interval to log the output of "apt policy" with a timestamp into a log file in order to understand when exactly the repository list is messed up. Turns out, that /usr/lib/apt/apt.systemd.daily script executed by apt-daily systemd service unit does not mess up the repository list. It happened between "Sat Jun 8 06:25:01 UTC 2019" and "Sat Jun 8 06:26:01 UTC 2019". When I check the logs for 06:00 to 06:30 time-period, then following was logged: $ sudo journalctl --since "2019-06-08 06:00:00" --until "2019-06-08 06:30:00" -- Logs begin at Mon 2019-05-13 19:38:07 UTC, end at Sat 2019-06-08 08:11:24 UTC. -- Jun 08 06:25:04 vps systemd[1]: Reloading The Apache HTTP Server. Jun 08 06:25:05 vps systemd[1]: Reloaded The Apache HTTP Server. Jun 08 06:25:05 vps liblogging-stdlog[556]: [origin software="rsyslogd" swVersion="8.24.0" x-pid="556" x-info="http://www.rsyslog.com;] rsyslogd was HUPed $ What and why is sending those signals to processes? Could it somehow affect the repository list..? thanks, Martin
Re: unattended-upgrades downloaded package information only from the sources in sources.list.d directory ignoring sources.list file
> Looks like the "apt update" or equivalent ran by unattended-upgrades > ignored the /etc/apt/sources.list file and used only > /etc/apt/sources.list.d/digitalocean-agent.list as a source for > repositories. > What might cause this behavior? I did some further debugging and it is the /usr/lib/apt/apt.systemd.daily script executed by apt-daily systemd service unit which updates the package index from the sources: # update package lists UPDATED=0 UPDATE_STAMP=/var/lib/apt/periodic/update-stamp if check_stamp $UPDATE_STAMP $UpdateInterval; then if eval apt-get $XAPTOPT -y update $XSTDERR; then /* output removed fro brevity */ Now I set the APT::Periodic::Verbose value to "2": $ apt-config dump APT::Periodic::Verbose APT::Periodic::Verbose "2"; $ ..and actually the entries in /etc/apt/sources.list file are not ignored: $ sudo journalctl --since today --no-pager -u apt-daily -- Logs begin at Mon 2019-05-13 19:38:07 UTC, end at Thu 2019-06-06 08:40:31 UTC. -- Jun 06 00:49:10 vps systemd[1]: Starting Daily apt download activities... Jun 06 00:49:10 vps apt.systemd.daily[31062]: verbose level 2 Jun 06 00:49:10 vps apt.systemd.daily[31062]: Reading package lists... Jun 06 00:49:10 vps apt.systemd.daily[31062]: Building dependency tree... Jun 06 00:49:10 vps apt.systemd.daily[31062]: Reading state information... Jun 06 00:49:10 vps apt.systemd.daily[31062]: check_stamp: interval=86400, now=1559779200, stamp=1559692800, delta=86400 (sec) Jun 06 00:49:10 vps apt.systemd.daily[31062]: Get:1 http://security.debian.org stretch/updates InRelease [94.3 kB] Jun 06 00:49:10 vps apt.systemd.daily[31062]: Ign:2 http://mirrors.digitalocean.com/debian stretch InRelease Jun 06 00:49:10 vps apt.systemd.daily[31062]: Get:3 http://mirrors.digitalocean.com/debian stretch-updates InRelease [91.0 kB] Jun 06 00:49:10 vps apt.systemd.daily[31062]: Hit:4 http://mirrors.digitalocean.com/debian stretch Release Jun 06 00:49:10 vps apt.systemd.daily[31062]: Get:5 http://security.debian.org stretch/updates/main Sources [205 kB] Jun 06 00:49:10 vps apt.systemd.daily[31062]: Get:6 http://security.debian.org stretch/updates/main amd64 Packages [492 kB] Jun 06 00:49:10 vps apt.systemd.daily[31062]: Get:7 https://repos.insights.digitalocean.com/apt/do-agent main InRelease [5,132 B] Jun 06 00:49:10 vps apt.systemd.daily[31062]: Fetched 888 kB in 0s (1,643 kB/s) Jun 06 00:49:11 vps apt.systemd.daily[31062]: Reading package lists... Jun 06 00:49:11 vps apt.systemd.daily[31062]: download updated metadata (success). Jun 06 00:49:11 vps apt.systemd.daily[31062]: send dbus signal (success) Jun 06 00:49:11 vps apt.systemd.daily[31062]: check_stamp: interval=0 Jun 06 00:49:11 vps apt.systemd.daily[31062]: download upgradable (not run) Jun 06 00:49:11 vps apt.systemd.daily[31062]: unattended-upgrade -d (not run) Jun 06 00:49:11 vps systemd[1]: Started Daily apt download activities. $ However, again, at the morning "apt policy" listed only the repository in /etc/apt/sources.list.d/digitalocean-agent.list file: $ apt policy Package files: 100 /var/lib/dpkg/status release a=now 500 https://repos.insights.digitalocean.com/apt/do-agent main/main amd64 Packages release o=. main,a=main,n=main,l=. main,c=main,b=amd64 origin repos.insights.digitalocean.com Pinned packages: $ After running manually the "sudo apt update" command, the apt downloaded >50MiB of packages data and output of "apt policy" listed all the repositories. Log files in /var/log/apt/ directory have not been updated. What could cause such behavior? How to debug this further? thanks, Martin
unattended-upgrades downloaded package information only from the sources in sources.list.d directory ignoring sources.list file
Hi, in order to test unattended-upgrades I downgraded yesterday(4.06) packages iceweasel, qemu-utils and thunderbird: # # "apt list --upgradable" command below was executed on 4.06 # apt list --upgradable Listing... Done iceweasel/stable 60.7.0esr-1~deb9u1 all [upgradable from: 52.9.0esr-1~deb9u1] qemu-utils/stable 1:2.8+dfsg-6+deb9u6 amd64 [upgradable from: 1:2.8+dfsg-6+deb9u5] thunderbird/stable 1:60.7.0-1~deb9u1 amd64 [upgradable from: 1:60.6.1-1~deb9u1] # As expected, the unattended-upgrades ran today(5.06) morning, but it reported, that "No packages found that can be upgraded unattended and no pending auto-removals". Indeed, when I checked for example "apt policy iceweasel", then the apt saw the installed version as the latest one: $ sudo apt policy iceweasel iceweasel: Installed: 52.9.0esr-1~deb9u1 Candidate: 52.9.0esr-1~deb9u1 Version table: *** 52.9.0esr-1~deb9u1 100 100 /var/lib/dpkg/status $ "apt policy" listed only the repository configured in /etc/apt/sources.list.d/digitalocean-agent.list while ignoring the ones in sources.list: # apt policy Package files: 100 /var/lib/dpkg/status release a=now 500 https://repos.insights.digitalocean.com/apt/do-agent main/main amd64 Packages release o=. main,a=main,n=main,l=. main,c=main,b=amd64 origin repos.insights.digitalocean.com Pinned packages: # After executing "apt update", the rest of the repositories were again seen in the output of "apt policy" and for example, the iceweasel was again upgradable to 60.7.0esr-1~deb9u1: $ sudo apt policy iceweasel iceweasel: Installed: 52.9.0esr-1~deb9u1 Candidate: 60.7.0esr-1~deb9u1 /* output removed for brevity */ $ Looks like the "apt update" or equivalent ran by unattended-upgrades ignored the /etc/apt/sources.list file and used only /etc/apt/sources.list.d/digitalocean-agent.list as a source for repositories. What might cause this behavior? thanks, Martin
Re: use mailx instead of sendmail in apt-listchanges
Dan, > You could do the wrapper, or you could install nullmailer, which > is an extremely simple MTA that always hands off mail to a > relayhost (i.e. somebody else's problem). I ended up with a following wrapper: $ cat /usr/sbin/sendmail #!/usr/bin/env bash # As header fields are at the top of the message, then following substitutions # should work reliably. sed '0,/^Subject: =?utf-8?q?apt-listchanges=3A_changelogs_for_vps?=$/ s//Subject: apt-listchanges: changelogs for vps/' | \ sed '0,/^From: root$/ s//From: nore...@example.com (VPS)/' | \ recode -f /qp | \ /usr/bin/mailx -t $ Andrew, I guess it works for you because bsd-mailx depends on virtual packet mail-transport-agent. regards, Martin
use mailx instead of sendmail in apt-listchanges
Hi, I have apt-listchanges installed and registered in apt system: # apt-config dump | grep apt-listchanges DPkg::Pre-Install-Pkgs:: "/usr/bin/apt-listchanges --apt || test $? -lt 10"; DPkg::Tools::Options::/usr/bin/apt-listchanges ""; DPkg::Tools::Options::/usr/bin/apt-listchanges::Version "2"; DPkg::Tools::Options::/usr/bin/apt-listchanges::InfoFD "20"; # "frontend" in /etc/apt/listchanges.conf is set to "mail" and valid e-mail address is set with "email_address" configuration option. Now when I upgrade a package which has NEWS/changelog present, then I get the "apt-listchanges: The mail frontend needs an installed 'sendmail', using pager" error message. This is because I don't have /usr/sbin/sendmail binary installed. I prefer to use mail/mailx and an external MTA. What could be the most elegant workaround in this situation? Create a /usr/sbin/sendmail wrapper script which processes the "/usr/sbin/sendmail -oi -t" command called by apt_listchanges.py and sends the mail using mailx? Modify the apt_listchanges.py? Something else? thanks, Martin
Re: How to make networking dependent on firewall configuration?
Hi Reco! Thanks for reply! I changed from /lib/systemd/system/networking.service.d/networking.service.conf to /etc/systemd/system/networking.service.d/networking.service.conf. > One can specify hostnames in netfilter rules. Trying to load such rules > without a working resolver can lead to weird results. Yes, I thought about this. However, I use strictly IP addresses or prefixes in my firewall rules. Martin
How to make networking dependent on firewall configuration?
Hi, I have a /lib/systemd/system/networking.service.d/networking.service.conf configuration file which specifies, that my custom iptables.service is a requirement for networking.service: # systemctl show networking -p Requires Requires=system.slice iptables.service # Is there a better or more correct way to do this? Are there any general disadvantages of such approach? thanks, Martin
Re: processing order for configuration files in /etc/network/interfaces.d
Hi David, > You need to post your evidence, starting with your /etc/network/interfaces > file. You say you're using ifup, so we can perhaps discount this paragraph: > >Currently, "source-directory" isn't supported by >network-manager and guessnet. > > but we don't know whether you're using "source-directory" or "source", > for example. I'm using "source": # cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # > If you care about the order in which these files are sourced, > for the time being I would source them individually in the order you > want. Yes, this is probably a good idea. However, ideally, "man interfaces" should state in which order files in /etc/network/interfaces.d/ are processed. Martin
Re: "accept_ra 1" vs "accept_ra 2" in interfaces configuration-file
On Wed, Aug 22, 2018 at 2:02 AM Andy Smith wrote: > > Hi Martin, > > On Wed, Aug 22, 2018 at 01:06:32AM +0300, Martin T wrote: > > In addition, "accept_ra" with a value of 2 should ensure that RA > > messages are accepted even if forwarding for that interface is > > enabled, shouldn't it? > > Yes, it should. > > That's the way it's documented and our use case is what it's meant > to serve, so if it's not behaving that way for you then I think it > is a bug and should be reported upstream in the kernel bugzilla. > > Cheers, > Andy > Hi Andy, I did some additional tests and made following observations: 1) For IPv6 one can't enable/disable routing for specific interface(s). It is either off(/proc/sys/net/ipv6/conf/all/forwarding is 0) or on(/proc/sys/net/ipv6/conf/all/forwarding is 1). 2) /proc/sys/net/ipv6/conf//forwarding controls simply if interface sends out RS messages and accepts RA messages Also, I found a post from David Miller in 2001(!) where he told pretty much the same: https://bugzilla.redhat.com/show_bug.cgi?id=38533 This means that I set the accept_ra in interfaces file to 1 for eth0(ISP-facing interface) and added those two lines to sysctl.conf: net.ipv6.conf.all.forwarding=1 net.ipv6.conf.eth0.forwarding=0 Martin
Re: processing order for configuration files in /etc/network/interfaces.d
On Thu, Aug 23, 2018 at 6:04 PM wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Thu, Aug 23, 2018 at 05:31:57PM +0300, Martin T wrote: > > Hi! > > > > According to "man interfaces", the ifup brings the named interfaces up > > in the order listed in /etc/network/interfaces file. However, what is > > the order for files in /etc/network/interfaces.d/? Alphabetical, i.e > > same as "ls -l /etc/network/interfaces.d/"? > > I assume the files there are invoked by run-parts (man interfaces(5) at > least hints at that). In that case yes, they are run in lexical order. > > But I'd double-check the run-parts part (heh). I've been caught spewing > nonsense here ;-) > > Cheers > - -- tomás > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.12 (GNU/Linux) > > iEYEARECAAYFAlt+zN8ACgkQBcgs9XrR2kbV9wCeKwl3eILQA2d5rA6QgDKIIwQy > 5scAn1NM68w35jLdQxrcD6F1dqCNpRpI > =JRHj > -END PGP SIGNATURE- > Tomas, I added "pre-up echo $IFACE >> /tmp/interfaces_test" line to each interface configuratio file in /etc/network/interfaces.d/ and looks like the invoke order is not lexical. I have four files in /etc/network/interfaces.d/: # ls -l /etc/network/interfaces.d/ total 16 -rw-r--r-- 1 root root 338 Aug 26 14:10 br0 -rw-r--r-- 1 root root 555 Aug 26 14:10 eth0 -rw-r--r-- 1 root root 96 Aug 26 14:09 eth0.100 -rw-r--r-- 1 root root 109 Aug 26 14:09 lo # However, the content of the /tmp/interfaces_test is alwayse(I rebooted the machine 5 times) following: # cat /tmp/interfaces_test br0 lo eth0 eth0.100 # I thought that ifup processes those files in order which they appear in /etc/network/interfaces.d/*, but this does not seem to be true. Any other ideas? thanks, Martin
processing order for configuration files in /etc/network/interfaces.d
Hi! According to "man interfaces", the ifup brings the named interfaces up in the order listed in /etc/network/interfaces file. However, what is the order for files in /etc/network/interfaces.d/? Alphabetical, i.e same as "ls -l /etc/network/interfaces.d/"? thanks, Martin
Re: "accept_ra 1" vs "accept_ra 2" in interfaces configuration-file
On Tue, Aug 21, 2018 at 1:23 AM Andy Smith wrote: > > Hi Martin, > > On Mon, Aug 20, 2018 at 03:58:36PM +0300, Martin T wrote: > > On Mon, Aug 20, 2018 at 7:55 AM Andy Smith wrote: > > > Back in 2011 this was a hard-won battle: > > > > > > > > > http://strugglers.net/~andy/blog/2011/09/04/linux-ipv6-router-advertisements-and-forwarding/ > > […] > > > Thanks for this very informative blog post! However, setting the > > "net.ipv6.conf.all.forwarding" to 1 in /etc/sysctl.conf and > > "accept_ra" to 2 in /etc/network/interfaces for ISP facing > > interface(eth0) didn't work for me. I expected SLAAC to work, but it > > didn't. I'm running kernel version 4.9.0. > > Strange. I've had a look and it seems I continued to use the > workaround mentioned in the blog post even though supposedly I no > longer need to. If you use that workaround, does it (SLAAC) start > working for you? > > Also, is it just address assignment that doesn't work or is it also > default router assignment that doesn't work? On my servers that > forward v6 I don't use dynamic assignment of addresses, I statically > assign them, but I do use dynamic assignment of default route. > > Cheers, > Andy > Hi Andy, Thanks for your reply! > If you use that workaround, does it (SLAAC) start working for you? Do you mean the pre-up statements in /etc/network/interfaces? If yes, then with those workarounds the SLAAC works, i.e I get the default route. My ISP-facing interface is eth0 and it has forwarding disabled: # cat /proc/sys/net/ipv6/conf/eth0/forwarding 0 # Rest of the options are set: # cd /proc/sys/net/ipv6/conf/ # cat default/forwarding 1 # cat all/forwarding 1 # cat eth0/accept_ra 2 # cat all/accept_ra 1 # cat default/accept_ra 1 # However, I quite do not understand how returned IPv6 traffic(ingress traffic to eth0) is routed to my LAN-facing interface when I have disabled it in /proc/sys/net/ipv6/conf/eth0/forwarding? If I do the same for IPv4 traffic(echo 0 > /proc/sys/net/ipv4/conf/eth0/forwarding), then returned traffic is dropped because forwarding for eth0 is disabled. In addition, "accept_ra" with a value of 2 should ensure that RA messages are accepted even if forwarding for that interface is enabled, shouldn't it? > Also, is it just address assignment that doesn't work or is it also > default router assignment that doesn't work? On my servers that > forward v6 I don't use dynamic assignment of addresses, I statically > assign them, but I do use dynamic assignment of default route. I have exactly the same case. I use dynamic assignment only for default route and this doesn't work even if "accept_ra" has a value of 2. thanks, Martin
Re: "accept_ra 1" vs "accept_ra 2" in interfaces configuration-file
On Mon, Aug 20, 2018 at 7:55 AM Andy Smith wrote: > > Hi Martin, > > On Mon, Aug 20, 2018 at 05:12:56AM +0300, Martin T wrote: > > According to "man interfaces" "accept_ra 1" makes interface to accept > > IPv6 RA messages. "accept_ra 2" does the same and in addition, it also > > enables forwarding. What does the forwarding mean in this context? One > > could think, that it modifies the /proc/sys/net/ipv6/conf/*/forwarding > > file(s), but this does not seem to be the case. > > If forwarding = 1 then by default RAs will not be accepted. Setting > accept_ra to 2 allows RAs to be accepted even when forwarding = 1. > > Changing the values of either forwarding or accept_ra does not alter > the values of the other. Only the behaviour of the system. > > Back in 2011 this was a hard-won battle: > > > http://strugglers.net/~andy/blog/2011/09/04/linux-ipv6-router-advertisements-and-forwarding/ > > Cheers, > Andy > Hi Andy! Thanks for this very informative blog post! However, setting the "net.ipv6.conf.all.forwarding" to 1 in /etc/sysctl.conf and "accept_ra" to 2 in /etc/network/interfaces for ISP facing interface(eth0) didn't work for me. I expected SLAAC to work, but it didn't. I'm running kernel version 4.9.0. Settings can be seen below: # sysctl net.ipv6.conf.all.forwarding net.ipv6.conf.all.forwarding = 1 # # sysctl net.ipv6.conf.eth0.accept_ra net.ipv6.conf.eth0.accept_ra = 2 # When I set the "net.ipv6.conf.all.forwarding" to 0 and reboot the router, then SLAAC works. What might cause this? thanks, Martin
"accept_ra 1" vs "accept_ra 2" in interfaces configuration-file
Hi! According to "man interfaces" "accept_ra 1" makes interface to accept IPv6 RA messages. "accept_ra 2" does the same and in addition, it also enables forwarding. What does the forwarding mean in this context? One could think, that it modifies the /proc/sys/net/ipv6/conf/*/forwarding file(s), but this does not seem to be the case. thanks, Martin
Re: "libstdc++6:i386" package breaks "libstdc++6"
Hi, sorry, my mistake. I had installed libstdc++6:amd64 version 6.3.0-16 from Debian testing. regards, Martin On Thu, May 11, 2017 at 5:19 PM, Henrique de Moraes Holschuh <h...@debian.org> wrote: > On Thu, 11 May 2017, Martin T wrote: >> I need to install "openjdk-7-jre-headless:i386" package in my amd64 >> Debian 8 system. However, it depends on "libstdc++6:i386" package > > Check the full binary package versions of libstdc++6 for i386 and amd64. > They must match. > > apt-cache policy libstdc++6:i386 libstdc++6:amd64 > > If they don't match, wait 24 hours, do an apt update, and check again. > > Also, ensure you did not install a rogue libstdc++6 from some random > place, and that whatever mirror you are using _is_ getting properly > updated. > >> Is there a way to install "libstdc++6:i386" package without breaking >> "libstdc++6"? > > Yes, it should just work. > > However, it is possible for a temporary version synchronization issue to > exist when one arch is updated, and another is delayed for some reason. > When that happens, it is typically automatically fixed in one or two > mirror pulses (there are several mirror pulses per day), plus whatever > time it takes for *your* mirror to get the update (so I typically tell > people to wait for 24 hours). > > -- > Henrique Holschuh >
"libstdc++6:i386" package breaks "libstdc++6"
Hi, I need to install "openjdk-7-jre-headless:i386" package in my amd64 Debian 8 system. However, it depends on "libstdc++6:i386" package which seems to break my system: # apt-cache depends libstdc++6:i386 libstdc++6:i386 Depends: gcc-4.9-base:i386 Depends: libc6:i386 Depends: libgcc1:i386 PreDepends: multiarch-support:i386 multiarch-support Conflicts: scim Conflicts: scim:i386 Breaks: Breaks: Breaks: Breaks: Breaks: Breaks: Replaces: libstdc++6-4.9-dbg Replaces: libstdc++6-4.9-dbg:i386 Replaces: libstdc++6 Breaks: libstdc++6 # # apt-get install libstdc++6:i386 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: efibootmgr gimp-data ipxe-qemu libaa1 libaio1 libamd2.3.1 libasyncns0 libavresample2 libavutil54 libbabl-0.1-0 libbiniou-ocaml libbluetooth3 libbrlapi0.6 libbz2-dev libbz2-ocaml libcacard0 libcamd2.3.1 libccolamd2.8.0 libcholmod2.1.2 libcolamd2.8.0 libconfig-file-perl libcupsfilters1 libcupsimage2 libdirectfb-1.2-9 libdjvulibre-text libeasy-format-ocaml libefivar0 libfdt1 libfindlib-ocaml libflac8 libfuse2 libgimp2.0 libgs9 libgs9-common libgsm1 libgudev-1.0-0 libijs-0.35 libjbig2dec0 liblist-moreutils-perl libmng1 libmp3lame0 libogg0 libopencore-amrnb0 libopencore-amrwb0 liborc-0.4-0 libpaper1 libpulse0 libregexp-assemble-perl libseccomp2 libsndfile1 libspeex1 libspice-server1 libtheora0 libumfpack5.6.2 libusbredirparser1 libva1 libvdeplug2 libvo-aacenc0 libvo-amrwbenc0 libvorbis0a libvorbisenc2 libvpx1 libwmf0.2-7 libx264-142 libxen-4.4 libxenstore3.0 libxvidcore4 libyajl2 libyojson-ocaml libzip-ocaml linux-headers-3.16.0-4-common linux-kbuild-3.16 ocaml-findlib openbios-ppc openbios-sparc openhackware os-prober qemu-slof qemu-system-common qemu-utils seabios Use 'apt-get autoremove' to remove them. The following packages will be REMOVED: adwaita-icon-theme apt apt-file apt-show-versions apt-utils apvlv build-essential chromium debhelper firefox-esr g++ g++-4.9 gcc gcc-4.8 gcc-4.9 gdisk gettext gettext-base gimp glib-networking glib-networking-services groff-base grub-common grub-efi-amd64 grub-efi-amd64-bin grub2-common iceweasel intltool-debian iperf libapt-inst1.5 libapt-pkg-perl libapt-pkg4.12 libasan0 libasan1 libasprintf0c2 libavcodec56 libavformat56 libbiniou-ocaml-dev libboost-iostreams1.55.0 libbz2-ocaml-dev libcaca0 libcilkrts5 libdjvulibre21 libeasy-format-ocaml-dev libegl1-mesa libgbm1 libgcc-4.8-dev libgcc-4.9-dev libgegl-0.2-0 libgtk-3-0 libgtk-3-bin libgtk-3-common libhunspell-1.3-0 libicu52 libilmbase6 libjack-jackd2-0 liblinear1 libllvm3.5 liblsan0 libopenexr6 libopenraw1 libpoppler-glib8 libpoppler46 libportaudio2 libproxy1 libpsl0 librest-0.7-0 libschroedinger-1.0-0 libsdl1.2debian libsoup-gnome2.4-1 libsoup2.4-1 libstdc++-4.9-dev libstdc++6 libtool libtsan0 libubsan0 libxatracker2 libyojson-ocaml-dev libzip-ocaml-dev linux-compiler-gcc-4.8-x86 linux-headers-3.16.0-4-amd64 man-db nmap ocaml-compiler-libs ocaml-interp ocaml-nox po-debconf poppler-utils qemu qemu-system qemu-system-arm qemu-system-mips qemu-system-misc qemu-system-ppc qemu-system-sparc qemu-system-x86 qemu-user snmp-mibs-downloader tasksel tasksel-data telnet unrar wget wireshark xpdf xserver-xorg xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev xserver-xorg-input-mouse xserver-xorg-input-synaptics xserver-xorg-input-vmmouse xserver-xorg-video-all xserver-xorg-video-ati xserver-xorg-video-cirrus xserver-xorg-video-fbdev xserver-xorg-video-intel xserver-xorg-video-mach64 xserver-xorg-video-mga xserver-xorg-video-modesetting xserver-xorg-video-neomagic xserver-xorg-video-nouveau xserver-xorg-video-openchrome xserver-xorg-video-r128 xserver-xorg-video-radeon xserver-xorg-video-savage xserver-xorg-video-siliconmotion xserver-xorg-video-sisusb xserver-xorg-video-tdfx xserver-xorg-video-trident xserver-xorg-video-vesa xserver-xorg-video-vmware xvnc4viewer The following NEW packages will be installed: libstdc++6:i386 WARNING: The following essential packages will be removed. This should NOT be done unless you know exactly what you are doing! apt libapt-pkg4.12 (due to apt) libstdc++6 (due to apt) 0 upgraded, 1 newly installed, 133 to remove and 0 not upgraded. Need to get 288 kB of archives. After this operation, 971 MB disk space will be freed. You are about to do something potentially harmful. To continue type in the phrase 'Yes, do as I say!' ?] n Abort. # Is there a way to install "libstdc++6:i386" package without breaking "libstdc++6"? thanks, Martin
real interface MTU different than seen in the output of "ip link show" command
Hi, today I noticed an interesting behavior where the PC NIC does not discard a received Ethernet frame, although it is larger than MTU on this NIC. For example, I made PC1[eth0] <-> [eth0]PC2 and PC1[eth0] <-> [eth0]PC3 connections and set the MTU on PC1 eth0 interface to 9000 bytes and MTU on PC2 and PC3 eth0 interfaces to 1500 bytes(confirmed with "ip link show" command). I expected PC2 and PC3 to drop frames >1500 bytes, but instead PC2 processed frames up to 4210 bytes and PC3 up to 8166 bytes. eth0 in PC2 uses e1000e driver and eth0 in PC3 uses r8169 driver included with jessie. On the other hand, Cisco switch works as expected. For example, if its port Fa0/30 MTU is 1998 bytes and I send >1998 byte frames, then those are dropped and counted as giants: c2960#sh int Fa0/30 counters errors PortAlign-Err FCS-ErrXmit-Err Rcv-Err UnderSize OutDiscards Fa0/30 0 0 0 0 0 0 Port Single-Col Multi-Col Late-Col Excess-Col Carri-Sen Runts Giants Fa0/30 0 0 0 0 0 0 4 c2960# How to explain this behavior? thanks, Martin
Re: understanding how localization works in Debian
On Mon, Dec 12, 2016 at 3:47 PM, Greg Wooledge <wool...@eeg.ccf.org> wrote:
> On Mon, Dec 12, 2016 at 01:58:12PM +0200, Martin T wrote:
>> 1) pam_env.so sets the environmental variables seen in the output of
>> locale command based on configuration files(for example
>> /etc/default/locale) when user logs in
>
> Maybe, maybe not. The LC_* and LANG variables can come from many
> different places. I think, however, that you are focusing on the
> libc/application level that uses these variables, and not their
> origin. So for your purposes, "LC_* and LANG are set somehow".
>
>> 2) nl_langinfo(), setlocale() and (some) other glibc functions used in
>> programs ask environment variables seen in the output of locale
>> command
>>
>> 3) based on those environment variables nl_langinfo(), setlocale(),
>> etc functions check the locale information in
>> /usr/lib/locale/locale-archive database and change their output
>> accordingly
>>
>> 4) /usr/lib/locale/locale-archive database is generated with
>> locale-gen utility based on entries in /etc/locale.gen file and locale
>> template/configuration files in /usr/share/i18n/locales/
>>
>> Did I understand this correctly?
>
> I am confused. There are basically three interaction points between
> you and the locale system, and you don't seem to have focused on any
> of them.
>
> 1) LC_* and LANG are set somehow by the end user or by the local OS.
>
> 2) The local system admin runs "dpkg-reconfigure locales" to determine
>which locales are "generated". End users can only receive translations
>from locales that are generated on the local system.
>
> 3) Applications are written with localization (l10n) support using the
>features of whichever language they're written in, e.g. _("...").
>
> For a more detailed look at #1, see https://wiki.debian.org/Locale
> (And even that is woefully incomplete thanks to the proliferation
> of Desktop Environments, and the ridiculous inadequacy of the PAM
> environment variable system.)
>
> For a more detailed look at #3, see
> https://www.gnu.org/software/gettext/manual/gettext.html
>
Greg,
thank you for reply! I do understand that LC_* and LANG variables can
come from various places. For example even pushed by SSH client.
However, were my other three points incorrect? As I understand it,
some glibc functions(for example nl_langinfo(), setlocale()) use those
LC_* and LANG variables to change the program output(for example first
day of the week in cal command) based on locale data in
/usr/lib/locale/locale-archive database.
thanks,
Martin
understanding how localization works in Debian
Hi, I read the "Configuring the System for Another Language" paragraph in "The Debian Administrator's Handbook" and am I correct that localization works in a way that: 1) pam_env.so sets the environmental variables seen in the output of locale command based on configuration files(for example /etc/default/locale) when user logs in 2) nl_langinfo(), setlocale() and (some) other glibc functions used in programs ask environment variables seen in the output of locale command 3) based on those environment variables nl_langinfo(), setlocale(), etc functions check the locale information in /usr/lib/locale/locale-archive database and change their output accordingly 4) /usr/lib/locale/locale-archive database is generated with locale-gen utility based on entries in /etc/locale.gen file and locale template/configuration files in /usr/share/i18n/locales/ Did I understand this correctly? thanks, Martin
potential damage to Debian "stable" when installing packages from "testing"
Hi, let's say that I need a package named "weechat"(version 1.6-1) from Debian "testing": # apt-get install -t testing weechat Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: binutils libc-bin libc-dev-bin libc-l10n libc6 libc6-dev libgcrypt20 libgnutls30 libhogweed4 libncurses5 libn weechat-curses Suggested packages: binutils-doc glibc-doc rng-tools gnutls-bin weechat-doc Recommended packages: manpages-dev weechat-plugins The following NEW packages will be installed: libc-l10n libgnutls30 libhogweed4 libnettle6 The following packages will be upgraded: binutils libc-bin libc-dev-bin libc6 libc6-dev libgcrypt20 libncurses5 libncursesw5 libp11-kit0 libtasn1-6 li 16 upgraded, 4 newly installed, 0 to remove and 511 not upgraded. Need to get 18.7 MB of archives. After this operation, 8,111 kB of additional disk space will be used. Do you want to continue? [Y/n] n Abort. # I guess one should not worry about new packages? However, as seen above, such operation would upgrade some packages which are dependencies for many other packages. For example libc6, libgcrypt20 or libncurses5. What are the consequences with that? I would guess it shouldn't cause problems because (usually) dependencies require version x OR higher. For example libc6 (>= 2.14) or libgcrypt20 (>= 1.6.1). thanks, Martin
Re: Advantages of Debian "backports" over "testing"?
Ok, understood. Thank you!
Martin
On Thu, Dec 8, 2016 at 1:30 PM, Lisi Reisz <lisi.re...@gmail.com> wrote:
> On Thursday 08 December 2016 11:06:55 Martin T wrote:
>> One more question regarding Debian backports- is it a good practice to
>> prefer latest versions from backports(jessie-backports) by default
>> while using stable(jessie) distribution?
>
> Definitely not.
>
> [snip]
>> Or is it a better practice to cherry-pick packages from "jessie-backports"?
>
> Yes.
>
> Lisi
>>
>>
>> thanks,
>> Martin
>>
>> On Wed, Dec 7, 2016 at 4:25 PM, maderios <mader...@gmail.com> wrote:
>> > On 12/07/2016 12:45 AM, Martin T wrote:
>> >> Hi,
>> >>
>> >> what are advantages of using Debian "backports"("jessie-backports" in
>> >> sources.list file) over "testing"("testing" in sources.list file)? As
>> >
>> > Hi
>> > You can't compare, they are completely different. Backport packages have
>> > stable/Jessie compatibility. Testing/Stretch and Sid are very close to
>> > each other. Very far from stable/jessie-backports/Jessie.
>> >
>> > --
>> > Maderios
>
Re: Advantages of Debian "backports" over "testing"?
One more question regarding Debian backports- is it a good practice to
prefer latest versions from backports(jessie-backports) by default
while using stable(jessie) distribution? I mean something like this:
# cat /etc/apt/preferences.d/00_jessie-backports
Explanation: Change pin-priority to
Explanation: 500 for all backported
Explanation: packages.
Package: *
Pin: release n=jessie-backports
Pin-Priority: 500
#
Configuration above would change the priority of "jessie-backports"
from 100 to 500 and thus versions from jessie-backports would be
installed because those are newer than the versions in stable(jessie).
Or is it a better practice to cherry-pick packages from "jessie-backports"?
thanks,
Martin
On Wed, Dec 7, 2016 at 4:25 PM, maderios <mader...@gmail.com> wrote:
> On 12/07/2016 12:45 AM, Martin T wrote:
>>
>> Hi,
>>
>> what are advantages of using Debian "backports"("jessie-backports" in
>> sources.list file) over "testing"("testing" in sources.list file)? As
>
>
> Hi
> You can't compare, they are completely different. Backport packages have
> stable/Jessie compatibility. Testing/Stretch and Sid are very close to each
> other. Very far from stable/jessie-backports/Jessie.
>
> --
> Maderios
>
Re: default "Default-Release" for APT
This makes sense, thanks! A good example would be libapparmor1: # apt-cache policy libapparmor1 libapparmor1: Installed: 2.9.0-3 Candidate: 2.10.95-7 Version table: 2.10.95-7 0 500 http://ftp.se.debian.org/debian/ unstable/main amd64 Packages 2.10.95-6 0 500 http://ftp.se.debian.org/debian/ testing/main amd64 Packages 2.10.95-4~bpo8+2 0 100 http://ftp.se.debian.org/debian/ jessie-backports/main amd64 Packages *** 2.9.0-3 0 500 http://ftp.se.debian.org/debian/ jessie/main amd64 Packages 100 /var/lib/dpkg/status # As seen above, version 2.10.95-7 from "unstable" would get installed because it is the highest version(checked with "dpkg --compare-versions") from all three sources with priority 500. Martin On Thu, Dec 8, 2016 at 1:35 AM, Mark Fletcher <mark2...@gmail.com> wrote: > > On Thu, 8 Dec 2016 at 08:11, Martin T <m4rtn...@gmail.com> wrote: >> >> Hi, >> >> as I showed in my initial post, I don't have that file: >> >> # ls -l /etc/apt/apt.conf >> ls: cannot access /etc/apt/apt.conf: No such file or directory >> # >> >> That's what made me wondering what is the default release if >> "APT::Default-Release" is not configured and based on what this >> default release is determined. >> >> >> thanks, >> Martin >> >> On Thu, Dec 8, 2016 at 12:03 AM, maderios <mader...@gmail.com> wrote: >> > On 12/07/2016 07:26 PM, Martin T wrote: >> >> >> >> Hi, >> >> >> >> I read the apt_preferences man page and it says that "To configure the >> >> default release in the configuration file, use: APT::Default-Release >> >> "stable";". While I have multiple distributions in sources.list >> >> file(stable, testing, unstable, jessie-backports), then I don't have >> >> the "Default-Release" configured: >> >> >> >> # grep -R Default-Release /etc/apt/ >> >> # >> >> >> >> What is the default "Default-Release"? How is this determined? >> >> >> > Hi >> > Look at your /etc/apt/apt.conf >> > >> > My apt.conf for testing: >> > >> > APT::Install-Recommends "false"; >> > APT::Install-Suggests "false"; >> > APT::Default-Release "testing"; >> > >> > -- >> > Maderios >> > >> > > It's using all of them, in that case. Then, newest versions of packages > supersede older ones. Net effect -- you get sid. > > Mark
Re: default "Default-Release" for APT
Hi, as I showed in my initial post, I don't have that file: # ls -l /etc/apt/apt.conf ls: cannot access /etc/apt/apt.conf: No such file or directory # That's what made me wondering what is the default release if "APT::Default-Release" is not configured and based on what this default release is determined. thanks, Martin On Thu, Dec 8, 2016 at 12:03 AM, maderios <mader...@gmail.com> wrote: > On 12/07/2016 07:26 PM, Martin T wrote: >> >> Hi, >> >> I read the apt_preferences man page and it says that "To configure the >> default release in the configuration file, use: APT::Default-Release >> "stable";". While I have multiple distributions in sources.list >> file(stable, testing, unstable, jessie-backports), then I don't have >> the "Default-Release" configured: >> >> # grep -R Default-Release /etc/apt/ >> # >> >> What is the default "Default-Release"? How is this determined? >> > Hi > Look at your /etc/apt/apt.conf > > My apt.conf for testing: > > APT::Install-Recommends "false"; > APT::Install-Suggests "false"; > APT::Default-Release "testing"; > > -- > Maderios >
default "Default-Release" for APT
Hi, I read the apt_preferences man page and it says that "To configure the default release in the configuration file, use: APT::Default-Release "stable";". While I have multiple distributions in sources.list file(stable, testing, unstable, jessie-backports), then I don't have the "Default-Release" configured: # grep -R Default-Release /etc/apt/ # What is the default "Default-Release"? How is this determined? thanks, Martin
Re: Advantages of Debian "backports" over "testing"?
Understood. Thanks! Martin On Wed, Dec 7, 2016 at 4:07 PM, Mark Fletcher <mark2...@gmail.com> wrote: > On Wed, Dec 07, 2016 at 03:25:17PM +0200, Martin T wrote: >> Dan, >> >> > On the other hand, upgrade your webserver to a backports version, >> > and the webserver has been compiled against the libs you already have. >> >> thanks! Is this also one of the reasons why not all packages in >> testing are available via backports? I mean I could imagine that there >> are packages which require some features which are provided only by >> libraries available for "testing" and thus the package can not be >> available via backports. >> >> > > That, and the fact that it takes effort to backport things, it can > sometimes be quite hard, and the people doing it aren't getting paid to. > So the things that get backported tend to be the things that either the > package maintainer wants, or that there is a lot of demand (and hence a > high chance of appreciation) for. > > Mark >
Re: Advantages of Debian "backports" over "testing"?
Dan,
> On the other hand, upgrade your webserver to a backports version,
> and the webserver has been compiled against the libs you already have.
thanks! Is this also one of the reasons why not all packages in
testing are available via backports? I mean I could imagine that there
are packages which require some features which are provided only by
libraries available for "testing" and thus the package can not be
available via backports.
thanks,
Martin
On Wed, Dec 7, 2016 at 2:37 AM, Dan Ritter <d...@randomstring.org> wrote:
> On Wed, Dec 07, 2016 at 01:45:45AM +0200, Martin T wrote:
>>
>> what are advantages of using Debian "backports"("jessie-backports" in
>> sources.list file) over "testing"("testing" in sources.list file)? As
>> I understand, "backports" does not have all the packages from
>> "testing". On the other hand, packages in "backports" are specially
>> recompiled for "stable" so I guess they might provide better
>> stability(?).
>>
>
> Suppose that you have a webserver that depends on OpenSSL, libc,
> and, oh, libasn1.
>
> All of those libraries are likely to get new versions in
> testing. If you upgrade your webserver to testing, they all come
> along for the ride.
>
> On the other hand, upgrade your webserver to a backports
> version, and the webserver has been compiled against the libs
> you already have.
>
> Meanwhile, your mail server also needs OpenSSL and libc, and
> you don't want to push that to new versions yet...
>
> -dsr-
Advantages of Debian "backports" over "testing"?
Hi,
what are advantages of using Debian "backports"("jessie-backports" in
sources.list file) over "testing"("testing" in sources.list file)? As
I understand, "backports" does not have all the packages from
"testing". On the other hand, packages in "backports" are specially
recompiled for "stable" so I guess they might provide better
stability(?).
thanks,
Martin
Detect upgradable packages in shell script ran as a non-root user
Hi,
I would like to run a cron job which periodically checks if I have
upgradable packages. One way to do it is probably like this:
$ apt-get upgrade -s | grep -q "^0 upgraded"
In case exit code is >0, then there are upgradable packages. The
second solution I came up with is:
$ for package in $(dpkg-query -f '${binary:Package}\n' -W); do\
apt-show-versions -u "$package" &>/dev/null && break;\
done
Again, if exit code is >0, then there is at least one upgradable
package. Of course, a solution like "apt-show-versions | grep -q
"upgradeable"" would also work.
For me the "apt-get upgrade -s | grep -q "^0 upgraded"" seems to be
the most reasonable solution, but maybe there is even a better way?
thanks,
Martin
Re: USB mouse and keyboard disconnected
Mark, thank you for your reply! > Random thought -- if ehci_pci is already loaded for some other device > early in the boot process, in a way that doesn't require the ehci_hcd > module, and then udev detects the keyboard and mouse, determines it > needs ehci_pci... and concludes all is well because that module is > already loaded... But the ehci_hcd piece isn't And then removing it > and re-loading it looks at the dependencies again in the light of all > the hardware udev is aware of by that stage, and so loads the > sub-module, and the keyboard and mouse start working... Maybe I misunderstood you, but at the time of the issue when I SSH into the machine, I can see that "ehci_hcd" is loaded. > OR, perhaps less far-fetched, could your running kernel somehow have > access to 2 versions of the ehci_pci module, one with a dependency on > ehci_hcd and one not? And at boot it is picking up the wrong one and > when you run modprobe from the command line it is picking up the other? As far as I can tell, there is only one ehci-pci module: # find / ! -type d -iname "ehci*pci*" /sys/module/ehci_hcd/holders/ehci_pci /sys/module/usbcore/holders/ehci_pci /lib/modules/3.16.0-4-amd64/kernel/drivers/usb/host/ehci-pci.ko # Any other ideas? thanks, Martin On Fri, Nov 4, 2016 at 12:48 AM, Mark Fletcher <mark2...@gmail.com> wrote: > On Thu, Nov 03, 2016 at 06:18:59PM +0200, Martin T wrote: >> Hi, >> >> looks like the problem is either with ehci_pci or ehci_hcd because if >> I do "modprobe -rv ehci_pci" and "modprobe -v ehci_pci", then both >> keyboard and mouse start to work. "ehci_hcd" is used by "ehci_pci": >> >> ehci_pci 12512 0 >> ehci_hcd 69837 1 ehci_pci >> >> > Random thought -- if ehci_pci is already loaded for some other device > early in the boot process, in a way that doesn't require the ehci_hcd > module, and then udev detects the keyboard and mouse, determines it > needs ehci_pci... and concludes all is well because that module is > already loaded... But the ehci_hcd piece isn't And then removing it > and re-loading it looks at the dependencies again in the light of all > the hardware udev is aware of by that stage, and so loads the > sub-module, and the keyboard and mouse start working... > > OR, perhaps less far-fetched, could your running kernel somehow have > access to 2 versions of the ehci_pci module, one with a dependency on > ehci_hcd and one not? And at boot it is picking up the wrong one and > when you run modprobe from the command line it is picking up the other? > > Mark >
Re: USB mouse and keyboard disconnected
Hi, looks like the problem is either with ehci_pci or ehci_hcd because if I do "modprobe -rv ehci_pci" and "modprobe -v ehci_pci", then both keyboard and mouse start to work. "ehci_hcd" is used by "ehci_pci": ehci_pci 12512 0 ehci_hcd 69837 1 ehci_pci Modinfo output for above-mentioned modules can be seen below: # modinfo ehci_pci filename: /lib/modules/3.16.0-4-amd64/kernel/drivers/usb/host/ehci-pci.ko license:GPL author: Alan Stern author: David Brownell description:EHCI PCI platform driver alias: pci:v104AdCC00sv*sd*bc*sc*i* alias: pci:v*d*sv*sd*bc0Csc03i20* depends:usbcore,ehci-hcd intree: Y vermagic: 3.16.0-4-amd64 SMP mod_unload modversions # # modinfo ehci_hcd filename: /lib/modules/3.16.0-4-amd64/kernel/drivers/usb/host/ehci-hcd.ko license:GPL author: David Brownell description:USB 2.0 'Enhanced' Host Controller (EHCI) Driver depends:usbcore intree: Y vermagic: 3.16.0-4-amd64 SMP mod_unload modversions parm: log2_irq_thresh:log2 IRQ latency, 1-64 microframes (int) parm: park:park setting; 1-3 back-to-back async packets (uint) parm: ignore_oc:ignore bogus hardware overcurrent indications (bool) # Any ideas what might cause this issue? thanks, Martin On Mon, Sep 19, 2016 at 4:47 PM, Martin T <m4rtn...@gmail.com> wrote: > Hi, > > I made a fresh minimal(no desktop environment, open-source "radeon" > driver, CEDAR firmware, X and dwm) Debian 8.5 installation few days > ago. Since that I have had two occasions where all of the sudden USB > devices(USB keyboard and mouse) no longer work. I'm able to access my > PC over SSH(or use PS/2 keyboard) and at the time of the issue nothing > is logged(I checked kernel ring buffer, X log files, etc). When I > remove(modprobe -r) USB related modules(ehci_hcd, ehci_pci, usbhid, > usbcore, usb_common, hid) and then again load those modules, the USB > mouse and keyboard start to work. At the time of the issue power to > the USB ports is present, because mouse LED is lit and for example > magic SysRq key-combinations work. Kernel version is 3.16.0-4-amd64. I > also noticed that for example around three days and then again 5 hours > ago, since this issue, USB mouse was disconnected for a second: > > > [11206.404325] usb 1-1.1: USB disconnect, device number 3 > [11206.629417] usb 1-1.1: new low-speed USB device number 5 using ehci-pci > [11206.727526] usb 1-1.1: New USB device found, idVendor=046d, idProduct=c03e > [11206.727539] usb 1-1.1: New USB device strings: Mfr=1, Product=2, > SerialNumber=0 > [11206.727542] usb 1-1.1: Product: USB-PS/2 Optical Mouse > [11206.727544] usb 1-1.1: Manufacturer: Logitech > [11206.731189] input: Logitech USB-PS/2 Optical Mouse as > /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/0003:046D:C03E.0004/input/input14 > [11206.731608] hid-generic 0003:046D:C03E.0004: input,hidraw0: USB HID > v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on > usb-:00:1a.0-1.1/input0 > [18378.452226] ip_tables: (C) 2000-2006 Netfilter Core Team > [110547.411844] perf interrupt took too long (2565 > 2500), lowering > kernel.perf_event_max_sample_rate to 5 > [241801.649235] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) > [243524.775521] usb 1-1.1: USB disconnect, device number 5 > [243525.022937] usb 1-1.1: new low-speed USB device number 6 using ehci-pci > [243525.120715] usb 1-1.1: New USB device found, idVendor=046d, idProduct=c03e > [243525.120719] usb 1-1.1: New USB device strings: Mfr=1, Product=2, > SerialNumber=0 > [243525.120722] usb 1-1.1: Product: USB-PS/2 Optical Mouse > [243525.120724] usb 1-1.1: Manufacturer: Logitech > [243525.124970] input: Logitech USB-PS/2 Optical Mouse as > /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/0003:046D:C03E.0005/input/input15 > [243525.125355] hid-generic 0003:046D:C03E.0005: input,hidraw0: USB > HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on > usb-:00:1a.0-1.1/input0 > > > I didn't physically unplug the mouse. However, I'm not sure if those > are related to this issue. As I told, at the time of this issue > nothing is logged. > > Last but not least, output of "lsusb" can be seen below: > > # lsusb > Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 001 Device 005: ID 046d:c03e Logitech, Inc. Premium Optical Wheel > Mouse (M-BT58) > Bus 001 Device 003: ID 046d:c313 Logitech, Inc. Internet 350 Keyboard > Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > # > > > Please let me know if anything was unclear or additional information is > needed. > > > thanks, > Martin
USB mouse and keyboard disconnected
Hi, I made a fresh minimal(no desktop environment, open-source "radeon" driver, CEDAR firmware, X and dwm) Debian 8.5 installation few days ago. Since that I have had two occasions where all of the sudden USB devices(USB keyboard and mouse) no longer work. I'm able to access my PC over SSH(or use PS/2 keyboard) and at the time of the issue nothing is logged(I checked kernel ring buffer, X log files, etc). When I remove(modprobe -r) USB related modules(ehci_hcd, ehci_pci, usbhid, usbcore, usb_common, hid) and then again load those modules, the USB mouse and keyboard start to work. At the time of the issue power to the USB ports is present, because mouse LED is lit and for example magic SysRq key-combinations work. Kernel version is 3.16.0-4-amd64. I also noticed that for example around three days and then again 5 hours ago, since this issue, USB mouse was disconnected for a second: [11206.404325] usb 1-1.1: USB disconnect, device number 3 [11206.629417] usb 1-1.1: new low-speed USB device number 5 using ehci-pci [11206.727526] usb 1-1.1: New USB device found, idVendor=046d, idProduct=c03e [11206.727539] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [11206.727542] usb 1-1.1: Product: USB-PS/2 Optical Mouse [11206.727544] usb 1-1.1: Manufacturer: Logitech [11206.731189] input: Logitech USB-PS/2 Optical Mouse as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/0003:046D:C03E.0004/input/input14 [11206.731608] hid-generic 0003:046D:C03E.0004: input,hidraw0: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-:00:1a.0-1.1/input0 [18378.452226] ip_tables: (C) 2000-2006 Netfilter Core Team [110547.411844] perf interrupt took too long (2565 > 2500), lowering kernel.perf_event_max_sample_rate to 5 [241801.649235] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [243524.775521] usb 1-1.1: USB disconnect, device number 5 [243525.022937] usb 1-1.1: new low-speed USB device number 6 using ehci-pci [243525.120715] usb 1-1.1: New USB device found, idVendor=046d, idProduct=c03e [243525.120719] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [243525.120722] usb 1-1.1: Product: USB-PS/2 Optical Mouse [243525.120724] usb 1-1.1: Manufacturer: Logitech [243525.124970] input: Logitech USB-PS/2 Optical Mouse as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/0003:046D:C03E.0005/input/input15 [243525.125355] hid-generic 0003:046D:C03E.0005: input,hidraw0: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-:00:1a.0-1.1/input0 I didn't physically unplug the mouse. However, I'm not sure if those are related to this issue. As I told, at the time of this issue nothing is logged. Last but not least, output of "lsusb" can be seen below: # lsusb Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 005: ID 046d:c03e Logitech, Inc. Premium Optical Wheel Mouse (M-BT58) Bus 001 Device 003: ID 046d:c313 Logitech, Inc. Internet 350 Keyboard Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub # Please let me know if anything was unclear or additional information is needed. thanks, Martin
Re: How to install init scripts manually?
In addition to symlinks to /etc/rc.d/ directories, insserv
adds a ":" line to /etc/init.d/.depend.start file. My
mistake was that I added ":" line to
/etc/init.d/.depend.start file.
regards,
Martin
On 8/9/14, Andrei POPESCU <andreimpope...@gmail.com> wrote:
> On Lu, 04 aug 14, 13:30:54, Martin T wrote:
>>
>> As a next step, I made the /etc/init.d/test-script file executable and
>> added a symlink to /etc/rc3.d/("ln -s ../init.d/test-script
>> /etc/rc3.d/S23test-script") directory and changed my runlevel from
>> 2(default) to 3 with "init 3". However, the test-script was not
>> started. Then I made a symlink to /etc/rc2.d/ directory:
>>
>> # file /etc/rc2.d/S23test-script
>> /etc/rc2.d/S23test-script: symbolic link to `../init.d/test-script'
>> #
>>
>> ..and reloaded the machine, but still the script was not started. If I
>> install the script with insserv("insserv /etc/init.d/test-script")
>> then the script is started if I reload the machine. Am I correct that
>> both insserv and update-rc.d take some additional steps when enabling
>> the script besides installing the symlinks and those steps are
>> required by /sbin/init? I guess one thing is .depend.boot,
>> .depend.start and .depend.stop files, but something else?
>
> Most probably. Just run 'update-rc.d test-script defaults' to install
> your initscript.
>
> 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
>
Re: apt-get dist-upgrade shows kept back packages
On 8/27/15, David Wright deb...@lionunicorn.co.uk wrote: Quoting Martin T (m4rtn...@gmail.com): Hi, as far as I know, kept back packages in Debian are shown in case package can not be upgraded with apt-get upgrade because upgrade requires to install new packages. Usually this can be fixed with apt-get dist-upgrade because this will install new packages if needed. Now for some reason db5.1-util package is kept back despite the fact that I execute apt-get dist-upgrade: I'm not sure which distribution you're running. [snip] Am I correct that db5.1-util is kept back because it replaces libdb5.1 which is required by python2.6 which I have installed? Output of apt-cache can be seen below: So what depends on python2.6 that won't be satisfied with 2.7? My wheezy shows libdb5.1:i386 5.1.29-5 and jessie has libdb5.3:i386 5.3.28-9 (assuming they're related). Neither has python2.6. Cheers, David. How would you check the packages which depend on python2.6 that won't be satisfied with python2.7? Simply compare the outputs of apt-cache rdepends python2.6 and apt-cache rdepends python2.7? thanks, Martin
apt-get dist-upgrade shows kept back packages
Hi, as far as I know, kept back packages in Debian are shown in case package can not be upgraded with apt-get upgrade because upgrade requires to install new packages. Usually this can be fixed with apt-get dist-upgrade because this will install new packages if needed. Now for some reason db5.1-util package is kept back despite the fact that I execute apt-get dist-upgrade: root@server:~# apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: db5.1-util 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. root@server:~# I even don't need the db5.1-util package because it satisfies dependencies for packages(partimage-server and db-upgrade-util) which I don't have installed: root@server:~# apt-cache rdepends db5.1-util db5.1-util Reverse Depends: partimage-server db-upgrade-util root@server:~# apt-cache policy db5.1-util partimage-server db-upgrade-util db5.1-util: Installed: 5.1.29-5 Candidate: 5.1.29-9 Version table: 5.1.29-9 0 500 http://ftp.debian.org/debian/ stable/main i386 Packages *** 5.1.29-5 0 100 /var/lib/dpkg/status partimage-server: Installed: (none) Candidate: 0.6.8-3 Version table: 0.6.8-3 0 500 http://ftp.debian.org/debian/ stable/main i386 Packages db-upgrade-util: Installed: (none) Candidate: 5.3.0 Version table: 5.3.0 0 500 http://ftp.debian.org/debian/ stable/main i386 Packages root@server:~# Am I correct that db5.1-util is kept back because it replaces libdb5.1 which is required by python2.6 which I have installed? Output of apt-cache can be seen below: root@server:~# apt-cache depends db5.1-util db5.1-util Depends: libc6 Breaks: libdb5.1 Replaces: libdb5.1 root@server:~# apt-cache rdepends libdb5.1 libdb5.1 Reverse Depends: python2.6 db5.1-util db5.1-util db5.1-util root@server:~# apt-cache policy python2.6 python2.6: Installed: 2.6.8-1.1 Candidate: 2.6.8-1.1 Version table: *** 2.6.8-1.1 0 100 /var/lib/dpkg/status root@server:~# thanks, Martin
qemu with KVM support compared to professional virtualization products from VMware or Oracle
Hi, I need to virtualize few dozen virtual-machines for production environment under Debian host-machine. I like the KISS principle provided by qemu with KVM support where each utility has its own specific purpose. For example I set up the virtual switch with ip/brctl utility or use single qemu executable to crate virtual-machines. However, is qemu with KVM support as suitable(stability, reliability) for production environment as so to say professional virtualization products from VMware or Oracle? thanks, Martin -- 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/CAJx5YvFeq3LCaDocztX5YgYjnficG7mEJp1w_yHo1=+3ex7...@mail.gmail.com
Re: How well-maintained are NEWS and changelog files in deb packages?
Don, thanks for explaining this! Martin On Fri, Feb 13, 2015 at 7:20 PM, Don Armstrong d...@debian.org wrote: On Fri, 13 Feb 2015, Martin T wrote: apt-listchanges uses NEWS and changelog files in Debian packages. Are NEWS and changelog files always or at list usually updated, i.e. is it safe to trust those? changelog.Debian.gz files are updated on every new version which is present in Debian, however, they are primarily used for reporting changes in Debian packaging, and only occasionally report changes by upstream. Upstream changelog files (usually /usr/share/doc/foopkg/changelog.gz or similar) are copied straight from upstream, and may be up to date or not depending on upstream's policies. NEWS.Debian.gz files are only updated when there is something significant to report; it's perfectly normal for these not to be updated for months or years (or not be present at all). -- Don Armstrong http://www.donarmstrong.com I shall require that [a scientific system's] logical form shall be such that it can be singled out, by means of empirical tests, in a negative sense: it must be possible for an empirical scientific system to be refuted by experience. -- Sir Karl Popper _Logic of Scientific Discovery_ §6 -- 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/20150213172057.go27...@teltox.donarmstrong.com -- 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/cajx5yvgxanpjvp8rppynnfbebtl6bltrdmen+ff_nousbey...@mail.gmail.com
How well-maintained are NEWS and changelog files in deb packages?
Hi, apt-listchanges uses NEWS and changelog files in Debian packages. Are NEWS and changelog files always or at list usually updated, i.e. is it safe to trust those? thanks, Martin -- 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/cajx5yvhz1hfdnpwfe3fjt6-azqss8vdngggqylx0hbpwoc1...@mail.gmail.com
Re: Software compatibility between different architectures?
how compatible are drivers on ports for different CPU architectures, e.g. I have a USB HSDPA modem which works great on Wheezy port for x86 architecture, but can I expect it to work on Wheezy port for ARM? If your ARM platform's USB driver works, then yes, you can expect the exact same support for any USB device you plug into it. I see. So usually there are no driver or other software issues because of different CPU architecture, i.e. once the kernel successfully boots up on ARM platform one can expect everything work exactly same as on wide-spread x86/x86-64 architecture? thanks, Martin -- 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/CAJx5YvGD3zUhoVKCxgSF=fNDOuoLDjHO6wnx2w6+pON=vhs...@mail.gmail.com
Re: understanding Debian support on ARM architecture
Reco, thanks for this explanation! Could you please explain this hardware enumeration provided by x86/x86-64 CPU's to kernel bit more? What kind of information is provided to kernel in case of x86/x86-64 CPU? thanks, Martin On Sun, Aug 10, 2014 at 9:39 AM, Reco recovery...@gmail.com wrote: Hi. On Sun, 10 Aug 2014 04:40:05 +0300 Martin T m4rtn...@gmail.com wrote: Hi, according to wiki, Debian is supported on little-endian ARM architecture. However, then wiki lists some sub-architectures which are supported. For example iop32x, ixp4xx, kirkwood and orion5x. Does this mean that Debian ARM port works on fairly limited number of sub-architectures? For example all the ARM-based embedded boards would probably not work with Debian ARM port? There's a difference between x86 and ARM, and that difference is hardware enumeration. x86 provides OS with one, ARM does not. To boot any Linux on ARM and to work with any hardware, one does need so called 'device tree' ([1]) compiled into the kernel. So, to answer your question - you have 100% guarantee that booting any of armel Debian kernel won't be successful and will end with kernel panic in the best case for any of those ARM-based embedded boards. Now, if you manage to build a working kernel for that specific board and boot it - sure you can use any part of Debian with the board short of the stock kernel(s). [1] http://lwn.net/Articles/448502/ PS I'm happy user of kirkwood family Debian kernel :) Reco -- 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/20140810103916.2c514ecf0f51a27855c6d...@gmail.com -- 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/cajx5yvh0ffp8zqqkfrbq6ejvh+ohcs3t4qio4jqo85c4vx9...@mail.gmail.com
Re: NFS and iptables during bootup
Yes, I erroneously used lo0 instead of lo in iptables rules. I use FreeBSD on daily basis :) However, once I allowed traffic to loopback interface and started NFS(/etc/init.d/nfs-common start), I saw some traffic on loopback interface: 48 560 ACCEPT all -- lo * 0.0.0.0/0 0.0.0.0/0 During the statd start following traffic is seen on loopback interface: 20:39:48.789936 00:00:00:00:00:00 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 98: 127.0.0.1.997 127.0.0.1.111: UDP, length 56 20:39:48.790044 00:00:00:00:00:00 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 70: 127.0.0.1.111 127.0.0.1.997: UDP, length 28 20:39:48.790221 00:00:00:00:00:00 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 98: 127.0.0.1.997 127.0.0.1.111: UDP, length 56 20:39:48.790250 00:00:00:00:00:00 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 70: 127.0.0.1.111 127.0.0.1.997: UDP, length 28 20:39:48.790649 00:00:00:00:00:00 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 98: 127.0.0.1.997 127.0.0.1.111: UDP, length 56 20:39:48.790759 00:00:00:00:00:00 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 70: 127.0.0.1.111 127.0.0.1.997: UDP, length 28 20:39:48.791156 00:00:00:00:00:00 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 98: 127.0.0.1.997 127.0.0.1.111: UDP, length 56 20:39:48.791278 00:00:00:00:00:00 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 70: 127.0.0.1.111 127.0.0.1.997: UDP, length 28 Once I save the iptables rules and restart the machine, it boots up without issues. Thanks! In addition, I will look into iptables-persistent package. However, last but not least, in which situations one firewalls loopback interface? Or is it a best practice just to allow everything through the loopback interface like I did? Martin On Sat, Aug 9, 2014 at 6:33 AM, Tom H tomh0...@gmail.com wrote: On Fri, Aug 8, 2014 at 11:47 AM, Martin T m4rtn...@gmail.com wrote: I moved the script from /etc/init.d to /etc/network directory and changed the shebang line from /bin/bash to /bin/sh. /bin/sh on my system points to /bin/dash. Thanks for those tips! Content of firewall rule-files can be seen here: # cat /etc/firewall.conf /etc/firewall6.conf # Generated by iptables-save v1.4.8 on Tue Jul 1 10:41:45 2014 *filter :INPUT DROP [17:1605] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [259:30520] -A INPUT -s 10.10.10.0/24 -j ACCEPT -A INPUT -s 8.8.8.8/32 -j ACCEPT -A INPUT -s 8.8.4.4/32 -j ACCEPT COMMIT # Completed on Tue Jul 1 10:41:45 2014 # Generated by ip6tables-save v1.4.8 on Tue Jul 1 10:41:56 2014 *filter :INPUT DROP [10518:992304] :FORWARD DROP [0:0] :OUTPUT DROP [0:0] COMMIT # Completed on Tue Jul 1 10:41:56 2014 If I comment out just the iptables-restore .. line from firewall-script and leave the ip6tables-restore .. line uncommented, the machine also boots without problems, i.e. it's the IPv4 iptables rules which seem to cause the statd to fail. I modified the IPv4 rules(/etc/firewall.conf file) in a following manner: # cat /etc/firewall.conf # Generated by iptables-save v1.4.8 on Fri Aug 8 17:08:22 2014 *filter :INPUT DROP [1:146] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [50:7006] -A INPUT -s 10.10.10.0/24 -i eth0 -j ACCEPT -A INPUT -s 8.8.8.8/32 -i eth0 -j ACCEPT -A INPUT -s 8.8.4.4/32 -i eth0 -j ACCEPT -A INPUT -i lo0 -j ACCEPT COMMIT # Completed on Fri Aug 8 17:08:22 2014 Your problem's probably that there's no lo0 (a BSD loopback device name?). It's lo. -- 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/CAOdo=sxevvfggwlj5suae-6vfbjwkqm8gsbpjfgukxt5vno...@mail.gmail.com -- 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/cajx5yvh+vagoegeyqu5ga2jpguxgrtzyp7gptmu90vog2c3...@mail.gmail.com
Software compatibility between different architectures?
Hi, how compatible are drivers on ports for different CPU architectures, e.g. I have a USB HSDPA modem which works great on Wheezy port for x86 architecture, but can I expect it to work on Wheezy port for ARM? Can one expect the same options(modprobe parameters) for drivers on all platforms? What about firmware(for example firmware files for warious Wi-Fi adapters)? I guess all more or less not so hardware-related software(for example iptables/netfilter) works exactly the same between different ports? regards, Martin -- 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/cajx5yve47sdkflgxufjmoff9yhdtpp3hyrxwgkfruo_qyxj...@mail.gmail.com
understanding Debian support on ARM architecture
Hi, according to wiki, Debian is supported on little-endian ARM architecture. However, then wiki lists some sub-architectures which are supported. For example iop32x, ixp4xx, kirkwood and orion5x. Does this mean that Debian ARM port works on fairly limited number of sub-architectures? For example all the ARM-based embedded boards would probably not work with Debian ARM port? thanks, Martin -- 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/cajx5yvgewxdqnlco4og8edpqnrcdd1ems4-0bpkmeraz1kx...@mail.gmail.com
Re: How to install init scripts manually?
On 8/4/14, Gary Dale garyd...@torfree.net wrote:
On 04/08/14 11:04 AM, Martin T wrote:
On 8/4/14, Gary Dalegaryd...@torfree.net wrote:
On 04/08/14 06:30 AM, Martin T wrote:
Hi,
I played around with a LSB init script under Squeeze(init is from
sysvinit package version 2.88dsf-13.1+squeeze1) for learning purposes.
My script is following:
# cat /etc/init.d/test-script
#! /bin/sh
### BEGIN INIT INFO
# Provides: test
# Required-Start:$all
# Required-Stop: $all
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: test script
# Description: test script
### END INIT INFO
# always executes
touch /tmp/test-file
case $1 in
start)
echo Starting script test
touch /tmp/test-file-start
;;
stop)
echo Stopping script test
touch /tmp/test-file-stop
;;
restart)
echo Restarting script test
touch /tmp/test-file-restart
;;
force-reload)
echo Force-reloading script test
touch /tmp/test-file-force-reload
;;
status)
echo Status of test
touch /tmp/test-file-status
;;
*)
echo Usage: /etc/init.d/test {start|stop}
exit 1
;;
esac
exit 0
#
As a next step, I made the /etc/init.d/test-script file executable and
added a symlink to /etc/rc3.d/(ln -s ../init.d/test-script
/etc/rc3.d/S23test-script) directory and changed my runlevel from
2(default) to 3 with init 3. However, the test-script was not
started. Then I made a symlink to /etc/rc2.d/ directory:
# file /etc/rc2.d/S23test-script
/etc/rc2.d/S23test-script: symbolic link to `../init.d/test-script'
#
..and reloaded the machine, but still the script was not started. If I
install the script with insserv(insserv /etc/init.d/test-script)
then the script is started if I reload the machine. Am I correct that
both insserv and update-rc.d take some additional steps when enabling
the script besides installing the symlinks and those steps are
required by /sbin/init? I guess one thing is .depend.boot,
.depend.start and .depend.stop files, but something else?
regards,
Martin
Not sure what you mean by reloaded the machine. However check out the
Debian wiki athttps://wiki.debian.org/RunLevel and
https://wiki.debian.org/LSBInitScripts.
Did you try telinit instead of init?
Hi,
by reloaded the machine I meant that I executed the reboot
command. I did try with telinit, but at least on Squeeze this is just
a symlink to init:
# file /sbin/telinit
/sbin/telinit: symbolic link to `init'
#
OK. On Jessie it is a symbolic link to /bin/systemctl. The difference is
likely important to provide a standard way to change run levels despite
not everyone using init. Ditto for insserv which seems to have been
created to allow upstart and init to coexist. update-rc.d seems to be an
attempt to make updating the run-levels easier.
I'd recommend staying with the tools and not doing it directly for the
simple reason that the old init system seems to be on its way out. The
LSB comment mechanism may become obsolete too with systemd apparently on
track to be the universal replacement for init and upstart.
As for your specific problem, did you look at ownership and specific
permission differences between your manual s-links and the ones inserv
and update-rc.d created? That's the only thing I can think of that would
prevent a script from running when the symbolic links point to the
correct file.
--
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/53dfa8a4.3040...@torfree.net
Gary,
yes I checked the ownership and permission differences between
manually created symlinks and the ones created by insserv, but there
were none. Both the actual script in /etc/init.d directory and
symlinks in /etc/rc*.d directories are owned by root. I even tried
this under the Wheezy:
root@vserver:~# cat /etc/issue
Debian GNU/Linux 7 \n \l
root@vserver:~#
..but still init(version 2.88) ignored the manually created symlinks.
I know that one should use insserv instead, but I was just curious why
init ignores manually created symlinks. In addition, I looked into
/etc/init.d/rc script which should be used to start scripts in
/etc/rc*.d directories and according to this script the actual utility
starting the services is startpar. Command is startpar -p 4 -t 20 -T
3 -M $1 -P $previous -R $runlevel where $1 is either start, stop or
boot and $previous is a previous runlevel and $runlevel is a
runlevel where one enters.
Maybe someone who is an expert on SystemV init and startpar on
Squeeze/Wheezy could look into it and explain how does the bootup
process work and why manual symlinks do not work?
regards,
Martin
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
Re: NFS and iptables during bootup
Reco,
I moved the script from /etc/init.d to /etc/network directory and
changed the shebang line from /bin/bash to /bin/sh. /bin/sh on my
system points to /bin/dash. Thanks for those tips!
Content of firewall rule-files can be seen here:
# cat /etc/firewall.conf /etc/firewall6.conf
# Generated by iptables-save v1.4.8 on Tue Jul 1 10:41:45 2014
*filter
:INPUT DROP [17:1605]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [259:30520]
-A INPUT -s 10.10.10.0/24 -j ACCEPT
-A INPUT -s 8.8.8.8/32 -j ACCEPT
-A INPUT -s 8.8.4.4/32 -j ACCEPT
COMMIT
# Completed on Tue Jul 1 10:41:45 2014
# Generated by ip6tables-save v1.4.8 on Tue Jul 1 10:41:56 2014
*filter
:INPUT DROP [10518:992304]
:FORWARD DROP [0:0]
:OUTPUT DROP [0:0]
COMMIT
# Completed on Tue Jul 1 10:41:56 2014
#
If I comment out just the iptables-restore .. line from
firewall-script and leave the ip6tables-restore .. line uncommented,
the machine also boots without problems, i.e. it's the IPv4 iptables
rules which seem to cause the statd to fail. I modified the IPv4
rules(/etc/firewall.conf file) in a following manner:
# cat /etc/firewall.conf
# Generated by iptables-save v1.4.8 on Fri Aug 8 17:08:22 2014
*filter
:INPUT DROP [1:146]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [50:7006]
-A INPUT -s 10.10.10.0/24 -i eth0 -j ACCEPT
-A INPUT -s 8.8.8.8/32 -i eth0 -j ACCEPT
-A INPUT -s 8.8.4.4/32 -i eth0 -j ACCEPT
-A INPUT -i lo0 -j ACCEPT
COMMIT
# Completed on Fri Aug 8 17:08:22 2014
#
..but this didn't help. Any other ideas?
Tom,
I suspect iptables because if I comment out the pre-up .. line from
/etc/network/interfaces file, the machine will boot without issues. In
addition, if I comment out just the iptables-restore .. line from
firewall-script and leave the ip6tables-restore .. line uncommented,
the machine also boots without problems, i.e. it's the IPv4 iptables
rules which seem to cause the statd to fail.
/usr is not a separate file-system mount and all I could find
regarding NFS and statd were the rpc.statd[1039]: unable to register
(statd, 1, udp). messages.
Last but not least, starting the /etc/init.d/nfs-common
script(/etc/init.d/nfs-common start) took few minutes to start even
if the OS is running.
regards,
Martin
On 8/4/14, Tom H tomh0...@gmail.com wrote:
On Mon, Aug 4, 2014 at 10:52 AM, Martin T m4rtn...@gmail.com wrote:
I made a very simple bash script which loads the iptables
configuration from /etc/firewall.conf and /etc/firewall6.conf files:
# cat /etc/init.d/firewall
#!/bin/bash
iptables-restore /etc/firewall.conf
ip6tables-restore /etc/firewall6.conf
Script is stored in /etc/init.d/ directory, but I haven't configured
init to load this script directly. I use the pre-up option in
/etc/network/interfaces instead:
# grep pre-up /etc/network/interfaces
pre-up /etc/init.d/firewall
/etc/firewall.conf and /etc/firewall6.conf contain few simple
allow-rules to input chain and set default policies for chains in
input table to drop.
Now if I reload the machine, the bootup takes more than 6 minutes.
Bootlog can be seen below:
...
Mon Aug 4 15:43:39 2014: Starting portmap daemon
Mon Aug 4 15:43:39 2014: Starting NFS common utilities: statdSetting
kernel variables ...done.
Mon Aug 4 15:46:39 2014: ^[[31mfailed!^[[39;49m
...
Mon Aug 4 15:46:40 2014: startpar: service(s) returned failure:
nfs-common ... ^[[31mfailed!^[[39;49m
...
Mon Aug 4 15:46:40 2014: Starting portmap daemon...Already running..
...
Mon Aug 4 15:46:40 2014: Starting NFS common utilities: statd
^[[31mfailed!^[[39;49m
...
Once the system is started, the iptables and ip6tables rules are
properly installed. According to log messages seen above, the problem
seems to be with NFS. Has anyone seen something like this before?
What makes you think that it's iptables that's preventing statd?
Do you have this problem when you comment out pre-up ...?
Is there more info about nfs/statd in /var/log/?
Is /usr a separate filesystem mount?
Can you start nfs after the system boots?
Small style nitpick: Since /etc/init.d/firewall isn't integrated
into sysvinit, you might as well move it to
/etc/{,firewall,network}; or move it to /etc/network/pre-up.d/ and
remove the pre-up ... line. I prefer installing iptables-persistent
but you might not want to or be allowed to...
--
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/CAOdo=sxtvdsbnc6k7ssavoq-em_b7uekzgdzph_sjxtkqyn...@mail.gmail.com
--
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/CAJx5YvEZhv7W6eH17XZFTMD5wGVU_+eBcM1DeW9612j4=nq...@mail.gmail.com
How to install init scripts manually?
Hi,
I played around with a LSB init script under Squeeze(init is from
sysvinit package version 2.88dsf-13.1+squeeze1) for learning purposes.
My script is following:
# cat /etc/init.d/test-script
#! /bin/sh
### BEGIN INIT INFO
# Provides: test
# Required-Start:$all
# Required-Stop: $all
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: test script
# Description: test script
### END INIT INFO
# always executes
touch /tmp/test-file
case $1 in
start)
echo Starting script test
touch /tmp/test-file-start
;;
stop)
echo Stopping script test
touch /tmp/test-file-stop
;;
restart)
echo Restarting script test
touch /tmp/test-file-restart
;;
force-reload)
echo Force-reloading script test
touch /tmp/test-file-force-reload
;;
status)
echo Status of test
touch /tmp/test-file-status
;;
*)
echo Usage: /etc/init.d/test {start|stop}
exit 1
;;
esac
exit 0
#
As a next step, I made the /etc/init.d/test-script file executable and
added a symlink to /etc/rc3.d/(ln -s ../init.d/test-script
/etc/rc3.d/S23test-script) directory and changed my runlevel from
2(default) to 3 with init 3. However, the test-script was not
started. Then I made a symlink to /etc/rc2.d/ directory:
# file /etc/rc2.d/S23test-script
/etc/rc2.d/S23test-script: symbolic link to `../init.d/test-script'
#
..and reloaded the machine, but still the script was not started. If I
install the script with insserv(insserv /etc/init.d/test-script)
then the script is started if I reload the machine. Am I correct that
both insserv and update-rc.d take some additional steps when enabling
the script besides installing the symlinks and those steps are
required by /sbin/init? I guess one thing is .depend.boot,
.depend.start and .depend.stop files, but something else?
regards,
Martin
--
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/CAJx5YvFN8SaaW32esaFEu=qd5bwvhuvhrhmutyphecgxr3e...@mail.gmail.com
NFS and iptables during bootup
Hi, I made a very simple bash script which loads the iptables configuration from /etc/firewall.conf and /etc/firewall6.conf files: # cat /etc/init.d/firewall #!/bin/bash iptables-restore /etc/firewall.conf ip6tables-restore /etc/firewall6.conf # Script is stored in /etc/init.d/ directory, but I haven't configured init to load this script directly. I use the pre-up option in /etc/network/interfaces instead: # grep pre-up /etc/network/interfaces pre-up /etc/init.d/firewall # /etc/firewall.conf and /etc/firewall6.conf contain few simple allow-rules to input chain and set default policies for chains in input table to drop. Now if I reload the machine, the bootup takes more than 6 minutes. Bootlog can be seen below: Mon Aug 4 15:43:37 2014: Setting preliminary keymap...done. Mon Aug 4 15:43:37 2014: Activating swap...done. Mon Aug 4 15:43:37 2014: Checking root file system...fsck from util-linux-ng 2.17.2 Mon Aug 4 15:43:37 2014: /dev/sda1: clean, 28387/3057824 files, 396742/12231168 blocks Mon Aug 4 15:43:37 2014: done. Mon Aug 4 15:43:37 2014: Cleaning up ifupdown Mon Aug 4 15:43:37 2014: Loading kernel modules...done. Mon Aug 4 15:43:37 2014: Activating lvm and md swap...done. Mon Aug 4 15:43:37 2014: Checking file systems...fsck from util-linux-ng 2.17.2 Mon Aug 4 15:43:38 2014: /dev/sda2: clean, 11/11968512 files, 799103/47851520 blocks Mon Aug 4 15:43:38 2014: done. Mon Aug 4 15:43:38 2014: Setting up networking Mon Aug 4 15:43:38 2014: Mounting local filesystems...done. Mon Aug 4 15:43:38 2014: Activating swapfile swap...done. Mon Aug 4 15:43:38 2014: Cleaning up temporary files Mon Aug 4 15:43:38 2014: Configuring network interfaces...done. Mon Aug 4 15:43:39 2014: Starting portmap daemon Mon Aug 4 15:43:39 2014: Starting NFS common utilities: statdSetting kernel variables ...done. Mon Aug 4 15:46:39 2014: ^[[31mfailed!^[[39;49m Mon Aug 4 15:46:39 2014: Cleaning up temporary files Mon Aug 4 15:46:40 2014: Setting console screen modes. Mon Aug 4 15:46:40 2014: ^[]R^[[9;30]^[[14;30]Skipping font and keymap setup (handled by console-setup). Mon Aug 4 15:46:40 2014: Setting up console font and keymap...done. Mon Aug 4 15:46:40 2014: Setting sensors limits. Mon Aug 4 15:46:40 2014: startpar: service(s) returned failure: nfs-common ... ^[[31mfailed!^[[39;49m Mon Aug 4 15:46:40 2014: INIT: Entering runlevel: 2 Mon Aug 4 15:46:40 2014: Using makefile-style concurrent boot in runlevel 2. Mon Aug 4 15:46:40 2014: Starting portmap daemon...Already running.. Mon Aug 4 15:46:40 2014: Starting enhanced syslogd: rsyslogd. Mon Aug 4 15:46:40 2014: Starting ACPI services Mon Aug 4 15:46:40 2014: Starting NFS common utilities: statd ^[[31mfailed!^[[39;49m Mon Aug 4 15:49:41 2014: Starting web server: apache2apache2: apr_sockaddr_info_get() failed for R61e Mon Aug 4 15:49:41 2014: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName Mon Aug 4 15:49:41 2014: . Mon Aug 4 15:49:41 2014: Starting deferred execution scheduler: atd. Mon Aug 4 15:49:41 2014: Starting periodic command scheduler: cron. Mon Aug 4 15:49:41 2014: Starting MTA:Starting internet superserver: inetd. Mon Aug 4 15:49:42 2014: exim4. Mon Aug 4 15:49:42 2014: Starting OpenBSD Secure Shell server: sshd. Once the system is started, the iptables and ip6tables rules are properly installed. According to log messages seen above, the problem seems to be with NFS. Has anyone seen something like this before? regards, Martin -- 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/cajx5yvgktc0ez_xhxagrtqb5pvy09bx12ut65ko5kdeaupp...@mail.gmail.com
Re: How to install init scripts manually?
Hi,
by reloaded the machine I meant that I executed the reboot
command. I did try with telinit, but at least on Squeeze this is just
a symlink to init:
# file /sbin/telinit
/sbin/telinit: symbolic link to `init'
#
regards,
Martin
On 8/4/14, Gary Dale garyd...@torfree.net wrote:
On 04/08/14 06:30 AM, Martin T wrote:
Hi,
I played around with a LSB init script under Squeeze(init is from
sysvinit package version 2.88dsf-13.1+squeeze1) for learning purposes.
My script is following:
# cat /etc/init.d/test-script
#! /bin/sh
### BEGIN INIT INFO
# Provides: test
# Required-Start:$all
# Required-Stop: $all
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: test script
# Description: test script
### END INIT INFO
# always executes
touch /tmp/test-file
case $1 in
start)
echo Starting script test
touch /tmp/test-file-start
;;
stop)
echo Stopping script test
touch /tmp/test-file-stop
;;
restart)
echo Restarting script test
touch /tmp/test-file-restart
;;
force-reload)
echo Force-reloading script test
touch /tmp/test-file-force-reload
;;
status)
echo Status of test
touch /tmp/test-file-status
;;
*)
echo Usage: /etc/init.d/test {start|stop}
exit 1
;;
esac
exit 0
#
As a next step, I made the /etc/init.d/test-script file executable and
added a symlink to /etc/rc3.d/(ln -s ../init.d/test-script
/etc/rc3.d/S23test-script) directory and changed my runlevel from
2(default) to 3 with init 3. However, the test-script was not
started. Then I made a symlink to /etc/rc2.d/ directory:
# file /etc/rc2.d/S23test-script
/etc/rc2.d/S23test-script: symbolic link to `../init.d/test-script'
#
..and reloaded the machine, but still the script was not started. If I
install the script with insserv(insserv /etc/init.d/test-script)
then the script is started if I reload the machine. Am I correct that
both insserv and update-rc.d take some additional steps when enabling
the script besides installing the symlinks and those steps are
required by /sbin/init? I guess one thing is .depend.boot,
.depend.start and .depend.stop files, but something else?
regards,
Martin
Not sure what you mean by reloaded the machine. However check out the
Debian wiki at https://wiki.debian.org/RunLevel and
https://wiki.debian.org/LSBInitScripts.
Did you try telinit instead of init?
--
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/cajx5yvfhsscpsh8y+jow0qyspzg-nta6elpavigwvv6+7mc...@mail.gmail.com
atftpd listens on wrong UDP port
Hi, When I start an atftpd daemon with /usr/sbin/atftpd --port 69 --bind-address 10.10.10.2 --daemon /srv/tftp/ command, the TFTP server listens on ephimeral port(58418 in this example) instead of port 69: # atftpd --version atftp-0.7 (server) # /usr/sbin/atftpd --port 69 --bind-address 10.10.10.2 --daemon /srv/tftp/ # ss -a -u -p | grep -i tftpd UNCONN 0 0 10.10.10.2:58418 *:*users((atftpd,30612,0)) # lsof -n | grep UDP | grep tftp atftpd30612 nobody0u IPv4 17845338 0t0 UDP 10.10.10.2:58418 # Why is that so? Am I doing something wrong? Or is this a bug? regards, Martin -- 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/CAJx5YvEd+dGTOeGjyRd=AFpDXbO=45B6=jdwj1zaojp6fed...@mail.gmail.com
Does anyone have mimic-tools1.0.1.deb package?
Hi, aMSN(free open source MSN Messenger clone) allowed one to store web-cam sessions, but saved those into cam files. There is an utility called mimic2rgb which allows one to convert those cam files into RGB video stream. At some point, there even were some Debian packages around(mimic-tools1.0.1.deb) which contained the mimic2rgb utility. However, at nowadays, it seems nearly impossible to find the Debian package(mimic-tools1.0.1.deb) or the source tarball(mimictools-1.0.1.tar.gz). Does anyone have an old repo mirrored somewhere which still has this package? However, I'm not sure if this package has ever been in any official repository.. regards, Martin -- 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/CAJx5YvHR=b3T_gbFco=ug6_u4b7agvocxru20vrysswl6qt...@mail.gmail.com
Re: Does anyone have mimic-tools1.0.1.deb package?
Hi, thank you for the reply, but looks the mimic-tools1.0.1.deb installation package has never been in official Debian repositories. regards, Martin On Tue, Jul 29, 2014 at 12:10 AM, Andrei POPESCU andreimpope...@gmail.com wrote: On Lu, 28 iul 14, 11:49:44, Martin T wrote: Hi, aMSN(free open source MSN Messenger clone) allowed one to store web-cam sessions, but saved those into cam files. There is an utility called mimic2rgb which allows one to convert those cam files into RGB video stream. At some point, there even were some Debian packages around(mimic-tools1.0.1.deb) which contained the mimic2rgb utility. However, at nowadays, it seems nearly impossible to find the Debian package(mimic-tools1.0.1.deb) or the source tarball(mimictools-1.0.1.tar.gz). Does anyone have an old repo mirrored somewhere which still has this package? However, I'm not sure if this package has ever been in any official repository.. If it was you can find it on snapshot.debian.org. 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 -- 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/CAJx5YvHuRKW==03PK4STHXiE10wtQ0v4J7SD=ogMtvarb=z...@mail.gmail.com
Re: minimal X.org xserver installation on Debian Wheezy
Thank you for replies! As I understand, xserver-xorg will install /usr/bin/X binary, which is a X Window Server itself and xinit installs the /usr/bin/xinit utility which starts the X Window Server and window manager(dwm in my case) as a X Windows Server client. As I have Intel 945GM video card, I need to install xserver-xorg-video-intel package, but why exactly is this needed? I mean at the moment, according to lspci -vvv, I use i915.ko driver and it's able to show the picture. Or is the performance lot better with intel_drv.so driver which will be installed with xserver-xorg-video-intel package? Or is it a problem for xserver if the driver module runs in kernel space? In addition, am I correct that xserver-xorg-input-evdev just installs the necessary user-space driver for handling mouse and keyboard input to xserver? regards, Martin On Sun, May 11, 2014 at 11:51 AM, Brian a...@cityscape.co.uk wrote: On Sun 11 May 2014 at 12:16:33 +0200, Sven Joachim wrote: On 2014-05-11 11:43 +0200, Brian wrote: If my notes are accurate ; from the last time I did it: xinit xserver-org xserver-xorg-input-kbd xserver-xorg-input-mouse Those are obsoleted by xserver-xorg-input-evdev. Thank you. xserver-xorg-video-radeon xserver-xorg-video-ati I'm fairly sure I installed the Recommends:. You may need to have different video packages. I would also install the -vesa and -fbdev packages in case there are problems with the native driver. Even though I've experienced no problems I suppose I could install them. After all, I now have a free 300K of space after purging -kbd and -mouse. :) -- 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/11052014124714.47ed4e857...@desktop.copernicus.demon.co.uk -- 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/CAJx5YvEjkxu1F=rnciasvhaeov3yctlug4hqe_bck18jwwh...@mail.gmail.com
Re: free space before the first and after the last partition if GPT partition scheme is used
Sven, I see. Thanks! Are those bios_grub or EFI system partitions located inside the GPT scheme, i.e. inside the first ~16KiB of the disk and it is not seen with gdisk? In addition, if this small area after the last partition is also for alignment purposes, then where is the backup GPT stored? regards, Martin On Sun, May 11, 2014 at 1:05 PM, Sven Hartge s...@svenhartge.de wrote: Martin T m4rtn...@gmail.com wrote: 2) Am I correct that boot loaders use their code on this area after the primary GPT and before the first partition? No. Bootloaders store their code in a special bios_grub partition (type EF02) when using the CSM/BIOS boot mode or inside a EFI System partion when using EFI boot mode. There is no free space like in the MBR where the bootloaders store their code. The free space you are seeing is to align the partitions on 1MB boundaries. 3) Are the last 689 sectors after the last partition used for storing the backup GPT? No. This is for alignment as well. Grüße, S° -- Sigmentation fault. Core dumped. -- 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/2alqh8v9v...@mids.svenhartge.de -- 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/CAJx5YvGFtqn6-MXRe2i9Qj4mUVsNdJx4eee9DhXy�iir+...@mail.gmail.com
Re: free space before the first and after the last partition if GPT partition scheme is used
Sven, for some reason, I do not see those partitions with gdisk: http://i.imgur.com/4BlDQx7.jpg On the other hand, I'm also using older version(0.8.5 vs 0.8.8) of gdisk than you.. Or is there some other reason? In addition, while your gdisk output says that you have 0B of free space, then I have 1.3MiB of free space- I guess it's because you aligned your partitions on 8 sector boundaries and there was no need to leave free space for alignment? regards, Martin On Sun, May 11, 2014 at 6:30 PM, Sven Hartge s...@svenhartge.de wrote: Martin T m4rtn...@gmail.com wrote: I see. Thanks! Are those bios_grub or EFI system partitions located inside the GPT scheme, i.e. inside the first ~16KiB of the disk and it is not seen with gdisk? In addition, if this small area after the last partition is also for alignment purposes, then where is the backup GPT stored? It is located somewhere inside the GPT. Those partitions do not need to be in the first 16KiB of a disk, they can be everywhere. (Though some UEFI implementations have problems if the boot partition is beyond the 2TiB mark.) And of course they are seen by gdisk, as they are normal partitions like every other partition. There are no magic disk spaces inside a GPT. # gdisk -l /dev/sda GPT fdisk (gdisk) version 0.8.8 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Disk /dev/sda: 3907029168 sectors, 1.8 TiB Logical sector size: 512 bytes Disk identifier (GUID): A2890495-0F45-4BA9-BA69-598347F489B9 Partition table holds up to 128 entries First usable sector is 34, last usable sector is 3907029134 Partitions will be aligned on 8-sector boundaries Total free space is 0 sectors (0 bytes) Number Start (sector)End (sector) Size Code Name 1 342047 1007.0 KiB EF02 primary 22048 195311615 93.1 GiBFD00 primary 3 195311616 3907029134 1.7 TiB FD00 primary Grüße, Sven. -- Sigmentation fault. Core dumped. -- 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/9alr4cs9v...@mids.svenhartge.de -- 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/CAJx5YvE2kELEuoJMEPdF=ymxx23vw4b-odpt8fsa59fxsy0...@mail.gmail.com
minimal X.org xserver installation on Debian Wheezy
Hi, I installed Debian Wheezy with no desktop environment as I would like to use lightweight dwm window manager instead. However, as a first step, I need to install xserver. I would like to install minimal components needed for running the xserver. What are the exact components(binaries, libraries, configuration files, etc) needed to run xserver? Obviously xinit(starts X server session), but what else? Or are the components needed for running xserver so scattered that practically one needs to install xserver-xorg package which will handle all the dependencies needed? regards, Martin -- 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/CAJx5YvEh6u7J-o7sYyb6e-KLMqpL1da=b82t0b9akz0hath...@mail.gmail.com
free space before the first and after the last partition if GPT partition scheme is used
Hi, DebianInstaller shows FREE SPACE before the first partition and after the last partition if GPT scheme is used: http://i.imgur.com/qjNrdAx.jpg While there is nothing wrong with that as there is indeed some free space before the first partition and after the last partition(http://i.imgur.com/4BlDQx7.jpg), such information is not displayed if I choose the MBR partitioning scheme(http://i.imgur.com/x4Ycl9q.jpg) while actually modern MBR editors(for example newer fdisk versions) should start the first partition also from sector 2048. 1) Am I correct that technically DebianInstaller should display the FREE SPACE area before the first partition also in case the MBR partition scheme is chosen? 2) Am I correct that boot loaders use their code on this area after the primary GPT and before the first partition? 3) Are the last 689 sectors after the last partition used for storing the backup GPT? regards, Martin -- 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/CAJx5YvFh7TM49ukbhp46cpWq2hbqAbtg-pax_YjkWZF9nvS_=a...@mail.gmail.com
domain-name option during the installation of Debian
Hi,
during the installation of Debian, one is asked for domain name.
Only place where it seems to be used is for completing the FQDN's:
root@localhost:~# find / \( \( -path /proc -o -path /sys \) -a
-prune \) -o \( -type f -a -exec grep -iH lab.net {} \; \)
/var/log/installer/status:Maintainer: Rémi Denis-Courmont r...@remlab.net
/var/log/installer/status:Maintainer: Rémi Denis-Courmont r...@remlab.net
/var/log/installer/cdebconf/questions.dat:Value: lab.net
/etc/network/interfaces: dns-search lab.net
root@localhost:~#
So in case I execute ping www, it is translated automatically to
ping www.lab.net.
However, where and how is the domain-name used during/after Debian installation?
regards,
Martin
--
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/CAJx5YvE70=RH6sa7M2NoacW9aKRdh8p4V=y8sq8o7ymgbfa...@mail.gmail.com
Re: domain-name option during the installation of Debian
Scott,
what I meant with this ping example is that domain name provided
during the installation(lab.net in my case) seems to be in use only in
one place which is the /etc/network/interfaces file dns-search line.
This means that if I execute host www, it asks DNS server for A
record for www.lab.net or if I execute ping mail, then I'm actually
executing ping mail.lab.net. You can read more about this from
manual page of resolv.conf.
However, the question itself is simple- where and how is the domain
name, which I inserted during the installation, used? So far it seems
to be used only for completing the domain names.
regards,
Martin
On Sat, Mar 8, 2014 at 2:04 AM, Scott Ferguson
scott.ferguson.debian.u...@gmail.com wrote:
On 08/03/14 12:40, Martin T wrote:
Hi,
during the installation of Debian, one is asked for domain name.
If it's not set automatically (by arping?)
Only place where it seems to be used is for completing the FQDN's:
root@localhost:~# find / \( \( -path /proc -o -path /sys \) -a
-prune \) -o \( -type f -a -exec grep -iH lab.net {} \; \)
/var/log/installer/status:Maintainer: Rémi Denis-Courmont r...@remlab.net
/var/log/installer/status:Maintainer: Rémi Denis-Courmont r...@remlab.net
/var/log/installer/cdebconf/questions.dat:Value: lab.net
/etc/network/interfaces: dns-search lab.net
root@localhost:~#
So in case I execute ping www, it is translated automatically to
ping www.lab.net.
? Do you mean when running ping from the local machine? (www. should be
a subdomain). The only way I'd see that was if it was registered in a
local dns, /etc/hosts, or as a result of .htaccess (in a web server).
However, where and how is the domain-name used during/after Debian
installation?
I'm having a particularly thick day and don't understand the question.
Do you mean where is it stored, and an exhaustive list of it's
applications?
regards,
Martin
Puzzled by question and your results from ping.
Kind regards
--
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/531a7aaa.6030...@gmail.com
--
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/cajx5yvfr0js+pap7zez-ntmswdnmeznvpozfuvabt+1zdpz...@mail.gmail.com
questions regarding file-system(ext3 or ext4) optimization for sortware-RAID array
Hi, I created a RAID1 array of two physical HDD's with chunk size of 64KiB under Debian wheezy. As a next step, I would like to create a file-system(ext3 or ext4) to this RAID1 array using mke2fs utility. Questions: 1) Should I use physical HDD sector size(512B in case of my HDD's) or file system cluster size(4096B as I use -b 4096) for calculating the value for stride= option? I guess it's the file-system cluster size so I should use stride=16? 2) If the stride size in my case is 16, then the stripe_width= should be 32 because there are two drives in the array which contain the actual data. Manual page of the mkfs.ext4 explain this option as This allows the block allocator to prevent read-modify-write of the parity in a RAID stripe if possible when the data is written.. How to understand this? What is this read-modify-write behavior? Could somebody explain this with an example? regards, Martin
How to understand which access control mechanism is in use for X server?
Hi, there are multiple access control mechanisms for X server like access based on host(xhost) or access based on cookie(xauth). Are both usually enabled at the same time? If yes, then which one is checked first? Are both active? I mean for example once I enable host with xhost, then do I need to configure xauth as well? regards, Martin
How and where lspci utility gathers information about hardware components?
Hi, lspci utility shows information regarding devices on various buses like PCI or PCI Express. For example on IBM ThinkPad T42 laptop: T42 ~ # lspci 00:00.0 Host bridge: Intel Corporation 82855PM Processor to I/O Controller (rev 03) 00:01.0 PCI bridge: Intel Corporation 82855PM Processor to AGP Controller (rev 03) 00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01) 00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01) 00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01) 00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 01) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 81) 00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge (rev 01) 00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev 01) 00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 01) 00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01) 00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 01) 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500] 02:00.0 CardBus bridge: Texas Instruments PCI4520 PC card Cardbus Controller (rev 01) 02:00.1 CardBus bridge: Texas Instruments PCI4520 PC card Cardbus Controller (rev 01) 02:01.0 Ethernet controller: Intel Corporation 82540EP Gigabit Ethernet Controller (Mobile) (rev 03) 02:02.0 Network controller: Intel Corporation PRO/Wireless 2915ABG [Calexico2] Network Connection (rev 05) T42 ~ # Am I correct that lspci uses SMBus which is present both on PCI and PCI Express? In addition, how are the model numbers detected? For example Intel Corporation PRO/Wireless 2915ABG Wi-Fi adapter. Is there a small non-volatile memory on each device which stores information about particular hardware device? regards, Martin
Re: understanding the role/relationship of the firmware and driver in case of Wi-Fi adapters
Bob, thank you for this exhaustive reply! 1) Are there Wi-Fi adapters which do not need firmware? I guess there are if manufacturer does not use semi-general purpose hardware? 2) Is the RAM built into the Wi-Fi card chipset? If I inspect my Ralink W-Fi card, which loads the 4096 byte /lib/firmware/rt2870.bin firmware file once the interface is brought up, then I don't see a separate RAM chip: https://www.dropbox.com/s/9z5rir3byfr9sg2/TEW-624UB-front.png https://www.dropbox.com/s/8p4iw8dpnfiphqb/TEW-624UB-back.png So in this case the RAM which stores the rt2870.bin firmware file is probably part of the RT2870F chip? regards, Martin 2013/1/2 Bob Proulx b...@proulx.com: Martin T wrote: some Wi-Fi adapters(for example Intel ipw2200 family and many Ralink cards) require both firmware and drivers in order to operate properly. Yes. 1) As I understand, firmware is usually a closed-source binary image provided by Wi-Fi card manufacturer? Yes. And because of this it doesn't meet the Debian Free Software Guidelines and can't be part of Debian. Packages of this firmware can only go in the non-free repository. 2) What happens with the firmware when card becomes operational? I mean by definition it should be written to device non-volatile memory(for example flash memory), but I doubt that this is the case for Wi-Fi adapters.. Or is it? No. The image is simply loaded into the adapter's ram. After the device loses power the memory evaporates. When power is applied again the device is once again blank or back to the default power on state and the firmware must be loaded again. 3) Last but not least, which aspects are controlled by Wi-Fi card firmware and what role plays the Wi-Fi adapter driver? Most devices today are designed using semi-general purpose hardware which includes a firmware part to configure and program the device. Vendors do this because it allows them to ship hardware early and to fix hardware bugs by making changes to the firmware later. They can do this very late and often after shipping the product. They simply update the device driver and put it on their web site and their customers load the new driver. This can effectively fix an incorrectly designed piece of hardware in the field. And that is why vendors like to design devices that use a firmware component. That they are programmable does not make them a computer. They are usually simply logic devices with memory to program the operation of them. There are various techniques such as state machines implemented with FPGAs and so forth. Programmable state machines almost always play a huge part in any electronic chip design. There isn't a simple rule that says every adapter behaves a certain way and the firmware does a certain thing on every one of them. Every vendor designs their device independently. Every one of them may be different. Which makes it hard to produce a generally correct answer. All that can really be said is that the firmware is used by the device to set itself up for the operation it was designed to do. After loading the device firmware then the kernel device driver has the task of interacting with the device. It provides the software layer that translates between a physical hardware device and the kernel's software. Bob Speaking as a past chip designer. -- 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/cajx5yvfdncsygshjs-1dp6uqun7ampcbc7jurzcxlhjlp8x...@mail.gmail.com
understanding the role/relationship of the firmware and driver in case of Wi-Fi adapters
Hello, some Wi-Fi adapters(for example Intel ipw2200 family and many Ralink cards) require both firmware and drivers in order to operate properly. 1) As I understand, firmware is usually a closed-source binary image provided by Wi-Fi card manufacturer? 2) What happens with the firmware when card becomes operational? I mean by definition it should be written to device non-volatile memory(for example flash memory), but I doubt that this is the case for Wi-Fi adapters.. Or is it? 3) Last but not least, which aspects are controlled by Wi-Fi card firmware and what role plays the Wi-Fi adapter driver? regards, Martin -- 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/cajx5yvf1qvgftwoviaoo3hejkf3sjzokvkz7f7ocnrtmsd9...@mail.gmail.com
Re: hostname question during Debian installation
Hello, in order to wrap this hostname question up, then hostname set during the Debian installation is: 1) mapped to an address from 127.0.0.0/8 range in /etc/hosts file. Specifically to IPv4 address 127.0.1.1 2) written to MTA(for example exim4) configuration file 3) written to /etc/mailname 4) written to /etc/hostname file Are there any local services which listen on hostname(127.0.1.1) address? As much as I have seen, they(for example Internet Printing Protocol or SMTP) all use localhost(127.0.0.1) address instead. Last but not least, is somebody able to name few utilities which use hostname for various purposes? I could name mail transfer agents. regards, Martin 2012/3/20 Bob Proulx b...@proulx.com: Tom H wrote: What I find somewhat weird is that when you install Debian, /etc/hostname and /etc/mailname are the same. So if it's box.company.internal and bob runs mail tom, bob's address'll be bob@box.company.internal. Yes. Seems reasonable to me. That is exactly what I want. It is traditional BSD/Unix behavior. But the address should be bob@company.internal! If that is what you desire (it isn't what I want) then it is probably easiest to set myorigin through /etc/mailname. There are also a number of other possibilities including masquading and various Postfix addresses rewriting processes. It would be perfectly nice if the package installation dialog were to ask the user if they want to set up address masquerading and to do it automatically. But for anyone who wants it the configuration is very easily accomplished with one of the above. I prefer to leave /etc/mailname along and to configure postfix explicitly. Then I can control over masquerade_classes and local_header_rewrite_clients too. IIUC, what you mean by masquerading is that if you send an email from box.company.internal, the email address is bob@company.internal rather than bob@box.company.internal. Yes. That is correct. But not sure if we are poking at the box removal part or the .internal part. I guess pedantically I would say yes to both if that is the hostname and fqdn. But I would probably have a different domain name and not be using an .internal name. If I were actually using a .internal name then I would probably be wanting to do address rewriting. But it is my turn to say that I have never been in an environment that actually used that type of name strategy. I've never worked in or set up an environment where the sender's address is bob@box.company.internal. But this explains why you didn't think bob@box.company.internal above was wrong. If company.internal is the name of the dns domain then that seems a reasonable default to me. Because 99.44% of the time it will be something really reasonable such as example.com which is actually a real domain name. I figure anyone that is actually using a literal .internal domain name would also know what they are doing and set up some type of address translation for it. But if they are setting up a box trouble.proulx.com for example then I would expect the mail to come from u...@trouble.proulx.com. :-) Anyway, I don't think that their argument was about masquerading; it was about what the canonical form of /etc/mailname should be. Whatever the result it is easy to change /etc/mailname to be correct. But if it should be enhanced to have a specific question then an enhancement request to exim and postfix both would probably be in order since neither of them ask about it but just assume and set it. dpkg-reconfigure postfix doesn't change myhostname either with a prompt for a hostname or through a hostname call so if you change the box's hostname, you have to edit /etc/postfix.main.cf by hand. It doesn't seem to. I suppose it should. But it does edit /etc/mailname and that is probably enough. I am sure that is what the postfix maintainer is thinking. You can then change /etc/hostname Changing /etc/hostname has no effect for postfix. and /etc/mailname, install postfix, and see what gets pulled in as myhostname into /etc/postfix/main.cf. Changing mailname doesn't really have an effect on the /etc/postfix/main.cf configuration. Because there is a Debian specific patch to in enable reading myorigin from a file. So it has an effect only through the patched code that pulls in the value dynamically when postfix starts from /etc/mailname instead of needing to specify myorigin in the main.cf file explicitly. I don't follow. Changing /etc/mailname changes myorigin because of that patch. Right. But it doesn't cause the postinst script or any other process to change main.cf. So above you postulated that setting hostname and mailname could possibly affect the settings in main.cf. But they don't. The main.cf file won't be changed regardless of what is set in mailname due to using the contents dynamically. (I usually change myorigin = /etc/mailname to its actual value on my
unable to install Debian using syslinux 4.05(stuck in Load installer components from CD step)
Hi, I'm trying to install debian-6.0.5-amd64-CD-1.iso from USB memory-stick. The problem is, that Debian-Installer is not able to Detect and mount CD-ROM during the installation process. The USB memory-stick is a 2GB model containing MBR and FAT32 file system: # fdisk -lu /dev/sdb Disk /dev/sdb: 2013 MB, 2013265920 bytes 62 heads, 62 sectors/track, 1022 cylinders, total 3932160 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x4a02df63 Device Boot Start End Blocks Id System /dev/sdb1 * 62 3928567 1964253b W95 FAT32 # file -s /dev/sdb1 /dev/sdb1: x86 boot sector, code offset 0x58, OEM-ID SYSLINUX, sectors/cluster 8, Media descriptor 0xf8, heads 62, sectors 3928506 (volumes 32 MB) , FAT (32 bit), sectors/FAT 3832, serial number 0x4373da42, label: debian64 # MBR has code needed for booting(first 440 bytes) and syslinux(4.05) is installed to mentioned partition. Syslinux configuration(syslinux.cfg) is very simple: # cat syslinux.cfg DEFAULT vmlinuz APPEND initrd=initrd.gz iso-scan/filename=/debian-6.0.5-amd64-CD-1.iso # Debian-Installer starts successfully and I'm able to specify locales and keyboard layout, but Detect and mount CD-ROM fails. If I start the ash(Execute a shell option in Debian-Installer menu) and mount memory-stick FAT32 partition to /cdrom using BusyBox mount utility, I'm able to pass the Detect and mount CD-ROM step, but then I'm stuck in Load installer components from CD. I even copied entire content of the debian-6.0.5-amd64-CD-1.iso image to a debian-6.0.5-amd64-CD-1.iso_content directory in memory-stick and then mounted this debian-6.0.5-amd64-CD-1.iso_content directory to /cdrom using the Debian-Installer shell(goo.gl/v2OgU), but this didn't help either to pass the Load installer components from CD step. Any ideas how to proceed here? Am I doing something wrong? regards, Martin -- 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/CAJx5YvFdcO=LxYCiCPt0f06WYYR-bdnL34W58i+SKsVKg6=j...@mail.gmail.com
which errors are critical for integrity of ext[234] file system?
I was playing with dd conv=noerror option. It continues reading the input file(for example HDD/SSD partition) even in case there are read errors. Which errors are critical for integrity of ext[234] file system? As I understand, Linux views the file system as a common set of objects- superblock(maintains and describes the state of the file system), inode(unique identifier for all the file system objects and contains necessary metadata), dentry(glues together inode number and file name), and file(bunch of bytes arranged in a certain order). Am I correct that if the main superblock is damaged, the spare one is used by fsck? In addition, am I correct that if sectors which hold content of a file(for example .avi movie) are damaged, then only this file is corrupted but file system itself is in good shape? regards, martin -- 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/CAJx5YvEG6gPQbwscg-Qs1LSaD=v76dmd-rfxh9b7m2q0sne...@mail.gmail.com
ICMP handling in Linux
It's a well known fact that even most(with exceptions like ASR1K) of the high-end Cisco or Juniper routers handle ICMP traffic in routing engines not in ASIC's which means that they share the CPU time with other processes. How prioritized is ICMP handling in modern Linux 2.6 and newer kernels? Is it possible to prioritize ICMP handling in kernel? regards, martin -- 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/cajx5yvg0rsuyi-walzvc2zpezk7+5xzb7qnradesyxbt6ze...@mail.gmail.com
Re: shrink ext3 filesystem using e2fsprogs and fdisk
Stefan: I'm afraid you can't use dd for this because as far as I know dd(1) reads and writes one block at a time and in case new position for file system overlaps with the present one, using dd you will start overwriting the end of the file system with the readings from the start of the file system. In addition, both parted and Gparted don't have dd as a dependency. However, it should be doable if current and new position don't overlap using the skip= and seek= options of dd..or how did you think? Jochen, Darac: here is what Gparted did: GParted 0.6.2 Libparted 2.3 Move /dev/sda9 to the right and shrink it from 904.37 GiB to 611.40 GiB 06:02:27( SUCCESS ) calibrate /dev/sda9 00:00:00( SUCCESS ) path: /dev/sda9 start: 56924160 end: 1953523711 size: 1896599552 (904.37 GiB) check file system on /dev/sda9 for errors and (if possible) fix them 00:02:16( SUCCESS ) e2fsck -f -y -v /dev/sda9 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 308 inodes used (0.00%) 18 non-contiguous files (5.8%) 0 non-contiguous directories (0.0%) # of inodes with ind/dind/tind blocks: 20/9/0 3363494 blocks used (2.57%) 0 bad blocks 1 large file 169 regular files 130 directories 0 character device files 0 block device files 0 fifos 0 links 0 symbolic links (0 fast symbolic links) 0 sockets 299 files e2fsck 1.41.12 (17-May-2010) shrink file system 00:01:31( SUCCESS ) resize2fs /dev/sda9 641099775K Resizing the filesystem on /dev/sda9 to 160274943 (4k) blocks. The filesystem on /dev/sda9 is now 160274943 blocks long. resize2fs 1.41.12 (17-May-2010) shrink partition from 904.37 GiB to 611.40 GiB 00:00:01( SUCCESS ) old start: 56924160 old end: 1953523711 old size: 1896599552 (904.37 GiB) new start: 56924160 new end: 1339123711 new size: 1282199552 (611.40 GiB) check file system on /dev/sda9 for errors and (if possible) fix them 00:02:47( SUCCESS ) e2fsck -f -y -v /dev/sda9 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 308 inodes used (0.00%) 18 non-contiguous files (5.8%) 0 non-contiguous directories (0.0%) # of inodes with ind/dind/tind blocks: 20/9/0 3821982 blocks used (2.38%) 0 bad blocks 1 large file 169 regular files 130 directories 0 character device files 0 block device files 0 fifos 0 links 0 symbolic links (0 fast symbolic links) 0 sockets 299 files e2fsck 1.41.12 (17-May-2010) grow file system to fill the partition 00:01:03( SUCCESS ) resize2fs /dev/sda9 Resizing the filesystem on /dev/sda9 to 160274944 (4k) blocks. The filesystem on /dev/sda9 is now 160274944 blocks long. resize2fs 1.41.12 (17-May-2010) check file system on /dev/sda9 for errors and (if possible) fix them 00:02:46( SUCCESS ) e2fsck -f -y -v /dev/sda9 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 308 inodes used (0.00%) 18 non-contiguous files (5.8%) 0 non-contiguous directories (0.0%) # of inodes with ind/dind/tind blocks: 20/9/0 3821982 blocks used (2.38%) 0 bad blocks 1 large file 169 regular files 130 directories 0 character device files 0 block device files 0 fifos 0 links 0 symbolic links (0 fast symbolic links) 0 sockets 299 files e2fsck 1.41.12 (17-May-2010) grow partition from 611.40 GiB to 904.37 GiB 00:00:02( SUCCESS ) old start: 56924160 old end: 1339123711 old size: 1282199552 (611.40 GiB) new start: 56924160 new end: 1953523711 new size: 1896599552 (904.37 GiB) move file system to the right 05:48:52( SUCCESS ) perform read-only test 01:54:58( SUCCESS ) using internal algorithm read 611.40 GiB finding optimal block size read 16.00 MiB using a block size of 2.00 MiB 00:00:00( SUCCESS ) 16.00 MiB of 16.00 MiB read 0.215304 seconds read 16.00 MiB using a block size of 4.00 MiB 00:00:00( SUCCESS ) 16.00 MiB of 16.00 MiB read 0.250469 seconds read 16.00 MiB using a block size of 8.00 MiB 00:00:01( SUCCESS ) 16.00 MiB of 16.00 MiB read 0.215766 seconds read 16.00 MiB using a block size of 16.00 MiB 00:00:00( SUCCESS ) 16.00 MiB of 16.00 MiB read 0.253064 seconds optimal block size is 2.00 MiB read 611.34 GiB using a block size of 2.00 MiB 01:54:57( SUCCESS ) 611.34 GiB of 611.34 GiB read 611.40 GiB (656486170624 B) read perform real move 03:53:54( SUCCESS ) using internal algorithm copy 611.40 GiB finding optimal block size copy 16.00
Re: shrink ext3 filesystem using e2fsprogs and fdisk
Jochen, Darac: thanks for replies! Is it possible to slide partition using the tools included with e2fsprogs package as well? Or is the GNU Parted only option here if I want to make changes over CLI? regards, martin Kuupäeval 26. märts 2012 17:28 kirjutas Darac Marjal mailingl...@darac.org.uk: On Sun, Mar 25, 2012 at 10:50:27PM +, Martin T wrote: I have a 500GB((131072000*4096)/1024^3) ext3 filesystem: [cut] Is it possible to make partition smaller starting from the beginning? If yes, do I need to somehow start file system from the end of the partition? Not directly. Try installing gparted (package: gparted). This will give you a graphical interface which will allow you to resize the partition as you're wanting. You will probably become aware that, no, taking space off the beginning of the partition is not possible, but it IS possible to take space off the END of the partition and then slide the partition towards the end of the space. The same is possible (I think) using the CLI parted, if you don't have X. Note also that ext3 does NOT support online shrinking (you can make it larger, but to make it smaller you MUST umount it). -- Darac Marjal -- 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/20120326142808.ga18...@darac.org.uk -- 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/CAJx5YvEnEV4+xCPZVLm-oH0ZUsgPBDYEK0=xpm7mhoscktm...@mail.gmail.com
shrink ext3 filesystem using e2fsprogs and fdisk
I have a 500GB((131072000*4096)/1024^3) ext3 filesystem: root@debian:~#dumpe2fs /dev/sda9 | egrep Block count|Block size dumpe2fs 1.41.12 (17-May-2010) Block count: 131072000 Block size: 4096 root@debian:~# ..on a 904GB((1953523711-56924160)*512)/(1024^3) partition(sda9): root@debian:~#fdisk -cul /dev/sda Disk /dev/sda: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00062a0f Device Boot Start End Blocks Id System /dev/sda1 *2048 684031 340992 83 Linux /dev/sda2 686078 1953523711 9764188175 Extended /dev/sda5 68608018262015 8787968 83 Linux /dev/sda61826406424121343 2928640 83 Linux /dev/sda7241233925614182316009216 82 Linux swap / Solaris /dev/sda85614387256922111 389120 83 Linux /dev/sda956924160 1953523711 948299776 83 Linux root@debian:~# At the moment everything works, but if I shrink the size of the /dev/sda9 partition from the beginning of the partition like this(sda9 is now 693GB which is more than enough to hold the 500GB file system): root@debian:~#fdisk -cul /dev/sda Disk /dev/sda: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00062a0f Device Boot Start End Blocks Id System /dev/sda1 *2048 684031 340992 83 Linux /dev/sda2 686078 1953523711 9764188175 Extended /dev/sda5 68608018262015 8787968 83 Linux /dev/sda61826406424121343 2928640 83 Linux /dev/sda7241233925614182316009216 82 Linux swap / Solaris /dev/sda85614387256922111 389120 83 Linux /dev/sda9 5 1953523711 726761856 83 Linux root@debian:~# ..then file system is broken: root@debian:~#dumpe2fs /dev/sda9 dumpe2fs 1.41.12 (17-May-2010) dumpe2fs: Bad magic number in super-block while trying to open /dev/sda9 Couldn't find valid filesystem superblock. root@debian:~# Is it possible to make partition smaller starting from the beginning? If yes, do I need to somehow start file system from the end of the partition? regards, martin -- 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/CAJx5YvHKWV_b5X_G=j4dG7F=av8tk-cwdrqetwe+iowuzpk...@mail.gmail.com
Re: hostname question during Debian installation
Andrei, Tom:
thank you for replies! So am I correct, that hostname set during the
installation is:
1) mapped to an address from 127.0.0.0/8 range in /etc/hosts file
2) written to /etc/mailname
3) written to message of the day file
4) usually used in shell prompt(for example \[\e]0;\u@\h:
\w\a\]${debian_chroot:+($debian_chroot)}\u@\h:\w\$)
..and this is it? Or did I miss any other uses of the hostname? For
some reason I always thought that hostname is definitely used by at
least other hosts in the LAN and local processing running in the
server, but turns out out was wrong(?). I mean one needs to configure
local processes(for example cupsd or snmpd) to use hostname IP
address if he wants to- by default they all use 127.0.0.1 which is
mapped to localhost in /etc/hosts file.
regards,
martin
Kuupäeval 13. veebruar 2012 15:21 kirjutas Tom H tomh0...@gmail.com:
On Sun, Feb 12, 2012 at 8:16 PM, Martin T m4rtn...@gmail.com wrote:
During Debian installation there is a question about hostname using
expert installation mode.
In both modes but I don't think that regular mode asks you for a domain.
Am I correct, that hostname inserted during Debian installation is
associated with a local(address from 127.0.0.0/8 range) IP address:
If you choose DHCP.
martin@martin-ThinkPad-T60:~$ hostname
martin-ThinkPad-T60
martin@martin-ThinkPad-T60:~$ grep martin-ThinkPad-T60 /etc/hosts
192.168.1.67 martin-ThinkPad-T60
::1 martin-ThinkPad-T60 localhost6.localdomain6 localhost6
127.0.1.1 martin-ThinkPad-T60
martin@martin-ThinkPad-T60:~$
You must've set a static IP address after installation because the
installer doesn't have the 127.0.1.1 line if you set a static IP
address within it.
..and it's used by few software programs(for example Apache, MySQL),
but hostname is usable only locally and not reachable from any other
machine even inside the LAN? In addition, aren't most of the programs
using 127.0.0.1 address which is mapped to localhost in /etc/hosts
file not to hostname I set:
martin@martin-desktop:~$ sudo netstat -lnpt
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address
State PID/Program name
tcp 0 0 127.0.0.1:8118 0.0.0.0:*
LISTEN 1233/polipo
tcp 0 0 127.0.0.1:631 0.0.0.0:*
LISTEN 1057/cupsd
tcp6 0 0 ::1:631 :::*
LISTEN 1057/cupsd
martin@martin-desktop:~$
If yes, then changing the hostname shouldn't break any
services/programs associated with it?
You're getting 127.0.0.1 in your netstat output because you're using
the -n switch. Without -n you'll get localhost.
To change your hostname, check /etc/hostname, /etc/hosts, and
/etc/mailname.
--
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/caodosylf4vhbyqz+epwq3n2f-196rd6-nogtkf_q2wudpq...@mail.gmail.com
--
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/cajx5yvgjmrqkagh+uqj-mamunb7q3wabsjosbsjdbanl1s3...@mail.gmail.com
hostname question during Debian installation
During Debian installation there is a question about hostname using expert installation mode. Am I correct, that hostname inserted during Debian installation is associated with a local(address from 127.0.0.0/8 range) IP address: martin@martin-ThinkPad-T60:~$ hostname martin-ThinkPad-T60 martin@martin-ThinkPad-T60:~$ grep martin-ThinkPad-T60 /etc/hosts 192.168.1.67martin-ThinkPad-T60 ::1 martin-ThinkPad-T60 localhost6.localdomain6 localhost6 127.0.1.1 martin-ThinkPad-T60 martin@martin-ThinkPad-T60:~$ ..and it's used by few software programs(for example Apache, MySQL), but hostname is usable only locally and not reachable from any other machine even inside the LAN? In addition, aren't most of the programs using 127.0.0.1 address which is mapped to localhost in /etc/hosts file not to hostname I set: martin@martin-desktop:~$ sudo netstat -lnpt Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp0 0 127.0.0.1:8118 0.0.0.0:* LISTEN 1233/polipo tcp0 0 127.0.0.1:631 0.0.0.0:* LISTEN 1057/cupsd tcp6 0 0 ::1:631 :::* LISTEN 1057/cupsd martin@martin-desktop:~$ If yes, then changing the hostname shouldn't break any services/programs associated with it? All the explanations and clarifications are most welcome! regards, martin -- 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/cajx5yvhvwdztdxeoj25wwevaymk2ux4uirottmzwhs3jj+q...@mail.gmail.com
