Re: OT: Help with a search and replace script in Perl for a big file with no line breaks
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Jan 26, 2018 at 03:31:37PM -0800, David Christensen wrote: [...] > I've "cleaned up" more files than I care to remember. (Perl s/// is the > road to madness for anything but the most trivial cases.) I wanted to give > the OP an idea of what needs to be done and the level of effort involved. Pretty arrogant, if you don't even know OP's problem, much less the OP himself? Perhaps the language he is dealing with is a regular language, in which case regex is... just what the doctor ordered? Perhaps the OP has a proof for that? What do you know? Regex is a sharp tool. Much more Perl's variant, which is a tad beyond regex. You gotta learn what it's good for and what ain't. Like a good cook's knife. You might cut off your toe with it, but if you want to dig a trench in your back yard, you better use something else. BTW, you can build fine parsers with Perl regex. It just makes for the first stage (lexer) (and a bit, see above), but it works a charm. Cheers - -- tomás -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlpsPyYACgkQBcgs9XrR2kbo6wCfTX1cXYkAtYgVSPu1gJDjrF4C xHcAnRR/OFvLH9wMn6daRTJLLeSIF8cC =mQWd -END PGP SIGNATURE-
Re: kernel 4.14.15 compilation using GCC 8 in unstable.......
On 26 January 2018 at 22:59, Michael Lange wrote: > On Fri, 26 Jan 2018 23:41:07 +0100 > Michael Lange wrote: > > > When I check /proc/cpuinfo I see that "msr" is listed in the "flags" > > section. So why doesn't the driver load automagically? > > But then, at least with the version of the checker-script here, it > > doesn't seem to make any difference, at least for whatever the script > > tries. > > Don't know if enabling msr will do me any good otherwise. > > Update: > just checked with my laptop (Intel/Baytrail); it is the same with msr, > module not loaded automatically, when loaded manually the contents > of /dev/cpu/0 look just as on my AMD desktop machine. The output of the > checker script still says "No" in the lines referring to msr. > *BUT*, since I finally managed to compile 4.15.rc9 with gcc-7.3, the > script claims the laptop is no longer vulnerable to "Spectre2". > I think I'll count that as success and call it a night now :-) > You could run this command: djt /home/mikef # !424 grep . /sys/devices/system/cpu/vulnerabilities/* /sys/devices/system/cpu/vulnerabilities/meltdown:Not affected /sys/devices/system/cpu/vulnerabilities/spectre_v1:Vulnerable /sys/devices/system/cpu/vulnerabilities/spectre_v2:Vulnerable: Minimal AMD ASM retpoline or use the checker (I assume you already are) https://github.com/speed47/spectre-meltdown-checker Cheers MF > > Best regards > > Michael > > > .-.. .. ...- . .-.. --- -. --. .- -. -.. .--. .-. --- ... .--. . .-. > > I realize that command does have its fascination, even under > circumstances such as these, but I neither enjoy the idea of command > nor am I frightened of it. It simply exists, and I will do whatever > logically needs to be done. > -- Spock, "The Galileo Seven", stardate 2812.7 > >
Re: kernel 4.14.15 compilation using GCC 8 in unstable.......
On 25 January 2018 at 23:28, Michael Lange wrote: > Hi, > > On Thu, 25 Jan 2018 22:23:38 + > Michael Fothergill wrote: > > > Dear All, > > > > I am continuing the discussion of the kernel 4.14.15 compilation in the > > Question on CVE-2017-5754 on Debian 8.9 post in a new post. > > > > The reason I am running with this kernel and not the 4.15.0 rc9 kernel > > that is now available on kernel.org is that: > > > > 1. It is stable > > > > 2. I have never tried to compile a kernel in Debian before and want to > > make it a bit easier for me the first time would try. > > > > 3. kernel 4.14.15 does have the KPTI and retpoline patches in it, so > > it is a fair candidate for the GCC8 compiler to produce a kernel that > > the patch checker could confirm has these meltdown and spectre fixes > > are properly set up and active. > > Ok, my advice if you don't want to give up yet :-) > I installed libelf-dev and did make clean. Then I copied over the config file and did you "Alas poor Yorick" Yes""|oldconfig command followed by make.kpkg again and I think it worked: root@mikef-PC:/usr/src/linux-4.14.15# !498 make-kpkg exec make kpkg_version=13.018+nmu1 -f /usr/share/kernel-package/ruleset/ minimal.mk debian == making target debian/stamp/conf/minimal_debian [new prereqs: ]== This is kernel package version 13.018+nmu1. test -d debian || mkdir debian test ! -e stamp-building || rm -f stamp-building install -p -m 755 /usr/share/kernel-package/rules debian/rules for file in ChangeLog Control Control.bin86 config templates.in rules; do \ cp -f /usr/share/kernel-package/$file ./debian/; \ done cp: cannot stat '/usr/share/kernel-package/ChangeLog': No such file or directory for dir in Config docs examples ruleset scripts pkg po; do \ cp -af /usr/share/kernel-package/$dir ./debian/; \ done test -f debian/control || sed -e 's/=V/4.14.15/g' \ -e 's/=D/4.14.15-10.00.Custom/g' -e 's/=A/amd64/g' \ -e 's/=SA//g' \ -e 's/=I//g'\ -e 's/=CV/4.14/g'\ -e 's/=M/Unknown Kernel Package Maintainer /g'\ -e 's/=ST/linux/g' -e 's/=B/x86_64/g'\ -e 's/=R//g'/usr/share/kernel-package/Control > debian/control test -f debian/changelog || sed -e 's/=V/4.14.15/g' \ -e 's/=D/4.14.15-10.00.Custom/g'-e 's/=A/amd64/g' \ -e 's/=ST/linux/g' -e 's/=B/x86_64/g' \ -e 's/=M/Unknown Kernel Package Maintainer /g' \ /usr/share/kernel-package/changelog > debian/changelog chmod 0644 debian/control debian/changelog test -d ./debian/stamp || mkdir debian/stamp make -f debian/rules debian/stamp/conf/kernel-conf make[1]: Entering directory '/usr/src/linux-4.14.15' == making target debian/stamp/conf/kernel-conf [new prereqs: ]== makeARCH=x86_64 \ oldconfig; make[2]: Entering directory '/usr/src/linux-4.14.15' scripts/kconfig/conf --oldconfig Kconfig # # configuration written to .config # make[2]: Leaving directory '/usr/src/linux-4.14.15' makeARCH=x86_64 prepare make[2]: Entering directory '/usr/src/linux-4.14.15' scripts/kconfig/conf --silentoldconfig Kconfig SYSTBL arch/x86/include/generated/asm/syscalls_32.h SYSHDR arch/x86/include/generated/asm/unistd_32_ia32.h SYSHDR arch/x86/include/generated/asm/unistd_64_x32.h SYSTBL arch/x86/include/generated/asm/syscalls_64.h HYPERCALLS arch/x86/include/generated/asm/xen-hypercalls.h SYSHDR arch/x86/include/generated/uapi/asm/unistd_32.h SYSHDR arch/x86/include/generated/uapi/asm/unistd_64.h SYSHDR arch/x86/include/generated/uapi/asm/unistd_x32.h HOSTCC arch/x86/tools/relocs_32.o HOSTCC arch/x86/tools/relocs_64.o HOSTCC arch/x86/tools/relocs_common.o HOSTLD arch/x86/tools/relocs CHK include/config/kernel.release UPD include/config/kernel.release WRAParch/x86/include/generated/asm/clkdev.h WRAParch/x86/include/generated/asm/dma-contiguous.h WRAParch/x86/include/generated/asm/early_ioremap.h WRAParch/x86/include/generated/asm/mcs_spinlock.h WRAParch/x86/include/generated/asm/mm-arch-hooks.h CHK include/generated/uapi/linux/version.h UPD include/generated/uapi/linux/version.h CHK include/generated/utsrelease.h UPD include/generated/utsrelease.h CC arch/x86/purgatory/purgatory.o AS arch/x86/purgatory/stack.o AS arch/x86/purgatory/setup-x86_64.o CC arch/x86/purgatory/sha256.o AS arch/x86/purgatory/entry64.o CC arch/x86/purgatory/string.o LD arch/x86/purgatory/purgatory.ro BIN2C arch/x86/purgatory/kexec-purgatory.c CC kernel/bounds.s CHK include/generated/bounds.h UPD include/generated/bounds.h CHK include/g
Re: kernel 4.14.15 compilation using GCC 8 in unstable.......
When you install the kernel, the following page ( https://www.debian.org/releases/jessie/i386/ch08s06.html.en) says you must run the following command: *dpkg -i ../linux-image-3.16-subarchitecture_1.0.custom_i386.deb*. Do I need to run mrproper beforehand? I can't see any linux-image file in the /usr/src/4.14.15 directory: root@mikef-PC:/usr/src/linux-4.14.15# ls -l total 724 drwxrwxr-x 32 root root 4096 Jan 23 18:58 arch drwxrwxr-x 3 root root 4096 Jan 23 18:58 block drwxrwxr-x 2 root root 4096 Jan 23 18:58 certs -rw-rw-r-- 1 root root 18693 Jan 23 18:58 COPYING -rw-rw-r-- 1 root root 98556 Jan 23 18:58 CREDITS drwxrwxr-x 4 root root 4096 Jan 23 18:58 crypto drwxr-xr-x 10 root root 4096 Jan 27 11:00 debian drwxrwxr-x 121 root root 12288 Jan 23 18:58 Documentation drwxrwxr-x 131 root root 4096 Jan 23 18:58 drivers drwxrwxr-x 2 root root 4096 Jan 23 18:58 firmware drwxrwxr-x 74 root root 4096 Jan 23 18:58 fs drwxrwxr-x 29 root root 4096 Jan 25 21:13 include drwxrwxr-x 2 root root 4096 Jan 23 18:58 init drwxrwxr-x 2 root root 4096 Jan 23 18:58 ipc -rw-rw-r-- 1 root root 2293 Jan 23 18:58 Kbuild -rw-rw-r-- 1 root root287 Jan 23 18:58 Kconfig drwxrwxr-x 17 root root 4096 Jan 27 11:00 kernel drwxrwxr-x 13 root root 12288 Jan 23 18:58 lib -rw-rw-r-- 1 root root 430471 Jan 23 18:58 MAINTAINERS -rw-rw-r-- 1 root root 59978 Jan 23 18:58 Makefile drwxrwxr-x 3 root root 4096 Jan 23 18:58 mm drwxrwxr-x 69 root root 4096 Jan 23 18:58 net -rw-rw-r-- 1 root root722 Jan 23 18:58 README drwxrwxr-x 28 root root 4096 Jan 23 18:58 samples drwxrwxr-x 14 root root 4096 Jan 23 18:58 scripts drwxrwxr-x 10 root root 4096 Jan 23 18:58 security drwxrwxr-x 24 root root 4096 Jan 23 18:58 sound drwxrwxr-x 30 root root 4096 Jan 23 18:58 tools drwxrwxr-x 2 root root 4096 Jan 23 18:58 usr drwxrwxr-x 4 root root 4096 Jan 23 18:58 virt root@mikef-PC:/usr/src/linux-4.14.15# Where would the default location of such a file be if were created using the make-kpkg command? Cheers MF
Re: kernel 4.14.15 compilation using GCC 8 in unstable.......
Hi, On Sat, 27 Jan 2018 11:26:25 + Michael Fothergill wrote: > > Where would the default location of such a file be if were created using > the make-kpkg command? the package should be in the source's parent directory, in your case I guess in /usr/src . Regards Michael .-.. .. ...- . .-.. --- -. --. .- -. -.. .--. .-. --- ... .--. . .-. Vulcans never bluff. -- Spock, "The Doomsday Machine", stardate 4202.1
Re: kernel 4.14.15 compilation using GCC 8 in unstable.......
On 27 January 2018 at 11:26, Michael Fothergill < michael.fotherg...@gmail.com> wrote: > When you install the kernel, the following page ( > https://www.debian.org/releases/jessie/i386/ch08s06.html.en) says you > must run the following command: > > *dpkg -i ../linux-image-3.16-subarchitecture_1.0.custom_i386.deb*. > > Do I need to run mrproper beforehand? > > I can't see any linux-image file in the /usr/src/4.14.15 directory: > > root@mikef-PC:/usr/src/linux-4.14.15# ls -l > total 724 > drwxrwxr-x 32 root root 4096 Jan 23 18:58 arch > drwxrwxr-x 3 root root 4096 Jan 23 18:58 block > drwxrwxr-x 2 root root 4096 Jan 23 18:58 certs > -rw-rw-r-- 1 root root 18693 Jan 23 18:58 COPYING > -rw-rw-r-- 1 root root 98556 Jan 23 18:58 CREDITS > drwxrwxr-x 4 root root 4096 Jan 23 18:58 crypto > drwxr-xr-x 10 root root 4096 Jan 27 11:00 debian > drwxrwxr-x 121 root root 12288 Jan 23 18:58 Documentation > drwxrwxr-x 131 root root 4096 Jan 23 18:58 drivers > drwxrwxr-x 2 root root 4096 Jan 23 18:58 firmware > drwxrwxr-x 74 root root 4096 Jan 23 18:58 fs > drwxrwxr-x 29 root root 4096 Jan 25 21:13 include > drwxrwxr-x 2 root root 4096 Jan 23 18:58 init > drwxrwxr-x 2 root root 4096 Jan 23 18:58 ipc > -rw-rw-r-- 1 root root 2293 Jan 23 18:58 Kbuild > -rw-rw-r-- 1 root root287 Jan 23 18:58 Kconfig > drwxrwxr-x 17 root root 4096 Jan 27 11:00 kernel > drwxrwxr-x 13 root root 12288 Jan 23 18:58 lib > -rw-rw-r-- 1 root root 430471 Jan 23 18:58 MAINTAINERS > -rw-rw-r-- 1 root root 59978 Jan 23 18:58 Makefile > drwxrwxr-x 3 root root 4096 Jan 23 18:58 mm > drwxrwxr-x 69 root root 4096 Jan 23 18:58 net > -rw-rw-r-- 1 root root722 Jan 23 18:58 README > drwxrwxr-x 28 root root 4096 Jan 23 18:58 samples > drwxrwxr-x 14 root root 4096 Jan 23 18:58 scripts > drwxrwxr-x 10 root root 4096 Jan 23 18:58 security > drwxrwxr-x 24 root root 4096 Jan 23 18:58 sound > drwxrwxr-x 30 root root 4096 Jan 23 18:58 tools > drwxrwxr-x 2 root root 4096 Jan 23 18:58 usr > drwxrwxr-x 4 root root 4096 Jan 23 18:58 virt > root@mikef-PC:/usr/src/linux-4.14.15# > > Where would the default location of such a file be if were created using > the make-kpkg command? > > Cheers > > MF > > PS since I can't seem to find the linux-image file for the new kernel to run dpkg -i on should I have run the *fakeroot make-kpkg --initrd --revision=1.0.custom kernel_image ie fakeroot make-kpkg --initrd --revision=4.14.15.krankenhaus kernel_image * command instead of just make-kpkg to create it? Cheers
Re: kernel 4.14.15 compilation using GCC 8 in unstable.......
On 27 January 2018 at 11:59, Michael Lange wrote: > Hi, > > On Sat, 27 Jan 2018 11:26:25 + > Michael Fothergill wrote: > > > > > Where would the default location of such a file be if were created using > > the make-kpkg command? > > the package should be in the source's parent directory, in your case I > guess in /usr/src . > Many thanks for the help again here. I can't see it in /usr/src: root@mikef-PC:/usr/src# ls -l total 907316 drwxrwxr-x 26 root root 4096 Jan 27 11:01 linux-4.14.15 -rw-r--r-- 1 mikef mikef 825139200 Jan 25 16:43 linux-4.14.15.tar drwxr-xr-x 2 root root 4096 Jan 25 18:02 linux-config-4.14 drwxr-xr-x 4 root root 4096 Jan 25 00:01 linux-headers-4.14.0-3-amd64 drwxr-xr-x 4 root root 4096 Jan 25 00:01 linux-headers-4.14.0-3-common drwxr-xr-x 4 root root 4096 Jan 24 16:32 linux-headers-4.9.0-4-amd64 drwxr-xr-x 4 root root 4096 Jan 24 16:33 linux-headers-4.9.0-4-common lrwxrwxrwx 1 root root 24 Jan 14 19:45 linux-kbuild-4.14 -> ../lib/linux-kbuild-4.14 lrwxrwxrwx 1 root root 24 Jan 15 04:43 linux-kbuild-4.15 -> ../lib/linux-kbuild-4.15 lrwxrwxrwx 1 root root 23 Aug 6 05:24 linux-kbuild-4.9 -> ../lib/linux-kbuild-4.9 -rw-r--r-- 1 root root 216052 Jan 14 19:45 linux-patch-4.14-rt.patch.xz -rw-r--r-- 1 root root 103701828 Jan 14 19:45 linux-source-4.14.tar.xz drwxr-xr-x 8 root root 4096 Nov 18 09:15 open-vm-tools-10.1.5 root@mikef-PC:/usr/src# Should the filename be something like linux-image-4.14.14.deb etc? Maybe Greg could think some find command that would search everywhere in the install I have here and then find it in some funny directory (even /tmp?) no one has ever heard of. I would be grateful for suggestions here. Could there be a bug in gcc 8 that made it forget to actually output the file? Thanks MF > > Regards > > Michael > > > .-.. .. ...- . .-.. --- -. --. .- -. -.. .--. .-. --- ... .--. . .-. > > Vulcans never bluff. > -- Spock, "The Doomsday Machine", stardate 4202.1 > >
Re: kernel 4.14.15 compilation using GCC 8 in unstable.......
On 27 January 2018 at 12:12, Michael Fothergill < michael.fotherg...@gmail.com> wrote: > > > On 27 January 2018 at 11:59, Michael Lange wrote: > >> Hi, >> >> On Sat, 27 Jan 2018 11:26:25 + >> Michael Fothergill wrote: >> >> > >> > Where would the default location of such a file be if were created using >> > the make-kpkg command? >> >> the package should be in the source's parent directory, in your case I >> guess in /usr/src . >> > > Many thanks for the help again here. I can't see it in /usr/src: > > > root@mikef-PC:/usr/src# ls -l > total 907316 > drwxrwxr-x 26 root root 4096 Jan 27 11:01 linux-4.14.15 > -rw-r--r-- 1 mikef mikef 825139200 Jan 25 16:43 linux-4.14.15.tar > drwxr-xr-x 2 root root 4096 Jan 25 18:02 linux-config-4.14 > drwxr-xr-x 4 root root 4096 Jan 25 00:01 > linux-headers-4.14.0-3-amd64 > drwxr-xr-x 4 root root 4096 Jan 25 00:01 > linux-headers-4.14.0-3-common > drwxr-xr-x 4 root root 4096 Jan 24 16:32 > linux-headers-4.9.0-4-amd64 > drwxr-xr-x 4 root root 4096 Jan 24 16:33 > linux-headers-4.9.0-4-common > lrwxrwxrwx 1 root root 24 Jan 14 19:45 linux-kbuild-4.14 -> > ../lib/linux-kbuild-4.14 > lrwxrwxrwx 1 root root 24 Jan 15 04:43 linux-kbuild-4.15 -> > ../lib/linux-kbuild-4.15 > lrwxrwxrwx 1 root root 23 Aug 6 05:24 linux-kbuild-4.9 -> > ../lib/linux-kbuild-4.9 > -rw-r--r-- 1 root root 216052 Jan 14 19:45 > linux-patch-4.14-rt.patch.xz > -rw-r--r-- 1 root root 103701828 Jan 14 19:45 linux-source-4.14.tar.xz > drwxr-xr-x 8 root root 4096 Nov 18 09:15 open-vm-tools-10.1.5 > root@mikef-PC:/usr/src# > > > Should the filename be something like linux-image-4.14.14.deb etc? > > Maybe Greg could think some find command that would search everywhere in > the install I have here and then find it in some funny directory (even > /tmp?) no one has ever heard of. > > I would be grateful for suggestions here. > > Could there be a bug in gcc 8 that made it forget to actually output the > file? > > Thanks > > MF > Available space for the file creation does not seem to be a problem: root@mikef-PC:/usr/src# df Filesystem 1K-blocks Used Available Use% Mounted on udev 35157160 3515716 0% /dev tmpfs 71418017564696616 3% /run /dev/sda9 352522356 17476768 317115400 6% / tmpfs357088488304 3482580 3% /dev/shm tmpfs 51204 5116 1% /run/lock tmpfs35708840 3570884 0% /sys/fs/cgroup tmpfs 714176 12714164 1% /run/user/1000 root@mikef-PC:/usr/src# MF > > > >> >> Regards >> >> Michael >> >> >> .-.. .. ...- . .-.. --- -. --. .- -. -.. .--. .-. --- ... .--. . .-. >> >> Vulcans never bluff. >> -- Spock, "The Doomsday Machine", stardate 4202.1 >> >> >
Re: kernel 4.14.15 compilation using GCC 8 in unstable.......
Hi, On Sat, 27 Jan 2018 12:12:57 + Michael Fothergill wrote: > > Should the filename be something like linux-image-4.14.14.deb etc? With default settings for make-kpkg the filename is probably a little longer, here it looks like linux-image-4.15.0-rc9-klappnase270118_4.15.0-rc9-klappnase270118-10.00.Custom_amd64.deb > > Maybe Greg could think some find command that would search everywhere in > the install I have here and then find it in some funny directory (even > /tmp?) no one has ever heard of. > > I would be grateful for suggestions here. > > Could there be a bug in gcc 8 that made it forget to actually output the > file? I don't think that gcc is to blame. Did you look at the final messages make-kpkg printed? If run successfully it should say something like "building package linux-image-..." . Regards Michael .-.. .. ...- . .-.. --- -. --. .- -. -.. .--. .-. --- ... .--. . .-. Power is danger. -- The Centurion, "Balance of Terror", stardate 1709.2
Re: kernel 4.14.15 compilation using GCC 8 in unstable.......
On 27 January 2018 at 11:59, Michael Lange wrote: > Hi, > > On Sat, 27 Jan 2018 11:26:25 + > Michael Fothergill wrote: > > > > > Where would the default location of such a file be if were created using > > the make-kpkg command? > > the package should be in the source's parent directory, in your case I > guess in /usr/src . > I think something is not right here. The compilation was very quick. Normally in gentoo the kernel compilation takes a little while. Maybe something got left out. Maybe I should have run mrproper after make clean before running make-kpkg. Cheers MF > > Regards > > Michael > > > .-.. .. ...- . .-.. --- -. --. .- -. -.. .--. .-. --- ... .--. . .-. > > Vulcans never bluff. > -- Spock, "The Doomsday Machine", stardate 4202.1 > >
Re: kernel 4.14.15 compilation using GCC 8 in unstable.......
On 27 January 2018 at 12:43, Michael Lange wrote: > Hi, > > On Sat, 27 Jan 2018 12:12:57 + > Michael Fothergill wrote: > > > > > Should the filename be something like linux-image-4.14.14.deb etc? > > With default settings for make-kpkg the filename is probably a little > longer, here it looks like > > linux-image-4.15.0-rc9-klappnase270118_4.15.0-rc9- > klappnase270118-10.00.Custom_amd64.deb > > > > > > Maybe Greg could think some find command that would search everywhere in > > the install I have here and then find it in some funny directory (even > > /tmp?) no one has ever heard of. > > > > I would be grateful for suggestions here. > > > > Could there be a bug in gcc 8 that made it forget to actually output the > > file? > > I don't think that gcc is to blame. Did you look at the final messages > make-kpkg printed? If run successfully it should say something like > "building package linux-image-..." . > It never did it. It did this at the end: chmod 0644 debian/control debian/changelog make -f debian/rules debian/stamp/conf/kernel-conf make[2]: Entering directory '/usr/src/linux-4.14.15' make[2]: 'debian/stamp/conf/kernel-conf' is up to date. make[2]: Leaving directory '/usr/src/linux-4.14.15' make[1]: Leaving directory '/usr/src/linux-4.14.15' echo done > debian/stamp/conf/minimal_debian exec debian/rules nothing to be done. and stopped. if you look through the rest of the output I posted above its not there AFAICT. Cheers MF > Regards > > Michael > > > .-.. .. ...- . .-.. --- -. --. .- -. -.. .--. .-. --- ... .--. . .-. > > Power is danger. > -- The Centurion, "Balance of Terror", stardate 1709.2 > >
Re: kernel 4.14.15 compilation using GCC 8 in unstable.......
It does seem as if make-kpkg has gone awol here. MF
Re: kernel 4.14.15 compilation using GCC 8 in unstable.......
On Sat, 27 Jan 2018 12:32:24 + Michael Fothergill wrote: > On 27 January 2018 at 11:59, Michael Lange wrote: > > > Hi, > > > > On Sat, 27 Jan 2018 11:26:25 + > > Michael Fothergill wrote: > > > > > > > > Where would the default location of such a file be if were created > > > using the make-kpkg command? > > > > the package should be in the source's parent directory, in your case I > > guess in /usr/src . > > > > I think something is not right here. The compilation was very quick. > Normally in gentoo the kernel compilation takes a little while. > Maybe something got left out. > > Maybe I should have run mrproper after make clean before running > make-kpkg. Yes, I naturally cannot tell from here, but it sounds like for some reason the procedure was terminated prematurely. Regards Michael .-.. .. ...- . .-.. --- -. --. .- -. -.. .--. .-. --- ... .--. . .-. It is necessary to have purpose. -- Alice #1, "I, Mudd", stardate 4513.3
Re: kernel 4.14.15 compilation using GCC 8 in unstable.......
On 27 January 2018 at 12:43, Michael Lange wrote: > Hi, > > On Sat, 27 Jan 2018 12:12:57 + > Michael Fothergill wrote: > > > > > Should the filename be something like linux-image-4.14.14.deb etc? > > With default settings for make-kpkg the filename is probably a little > longer, here it looks like > > linux-image-4.15.0-rc9-klappnase270118_4.15.0-rc9- > klappnase270118-10.00.Custom_amd64.deb > > > > > > Maybe Greg could think some find command that would search everywhere in > > the install I have here and then find it in some funny directory (even > > /tmp?) no one has ever heard of. > > > > I would be grateful for suggestions here. > > > > Could there be a bug in gcc 8 that made it forget to actually output the > > file? > > I don't think that gcc is to blame. I think I will sign up on the gcc gnu help page and ask people if they have a test case file I can run to 100% confirm the GCC 8 compiler is running properly. Once I am convinced it is then the next stage is to try to talk to the developers who maintain the make-kpkg program. Cheers MF > Did you look at the final messages > make-kpkg printed? If run successfully it should say something like > "building package linux-image-..." . > > Regards > > Michael > > > > .-.. .. ...- . .-.. --- -. --. .- -. -.. .--. .-. --- ... .--. . .-. > > Power is danger. > -- The Centurion, "Balance of Terror", stardate 1709.2 > >
Re: kernel 4.14.15 compilation using GCC 8 in unstable.......
Hi, On Sat, 27 Jan 2018 13:12:13 + Michael Fothergill wrote: > I think I will sign up on the gcc gnu help page and ask people if they > have a test case file I can run to 100% confirm the GCC 8 compiler is > running properly. > Once I am convinced it is then the next stage is to try to talk to the > developers who maintain the make-kpkg program. are you still using gcc-8? Here this one didn't work at all for me, compiling always aborted early with compiler errors. It worked immediately though after I removed ggc-8 and upgraded gcc-7 to v. 7.3 from sid. Regards Michael .-.. .. ...- . .-.. --- -. --. .- -. -.. .--. .-. --- ... .--. . .-. "It's hard to believe that something which is neither seen nor felt can do so much harm." "That's true. But an idea can't be seen or felt. And that's what kept the Troglytes in the mines all these centuries. A mistaken idea." -- Vanna and Kirk, "The Cloud Minders", stardate 5819.0
Re: kernel 4.14.15 compilation using GCC 8 in unstable.......
On 27 January 2018 at 13:17, Michael Lange wrote: > On Sat, 27 Jan 2018 12:32:24 + > Michael Fothergill wrote: > > > On 27 January 2018 at 11:59, Michael Lange wrote: > > > > > Hi, > > > > > > On Sat, 27 Jan 2018 11:26:25 + > > > Michael Fothergill wrote: > > > > > > > > > > > Where would the default location of such a file be if were created > > > > using the make-kpkg command? > > > > > > the package should be in the source's parent directory, in your case I > > > guess in /usr/src . > > > > > > > I think something is not right here. The compilation was very quick. > > Normally in gentoo the kernel compilation takes a little while. > > Maybe something got left out. > > > > Maybe I should have run mrproper after make clean before running > > make-kpkg. > > Yes, I naturally cannot tell from here, but it sounds like for some > reason the procedure was terminated prematurely. > But, you would argue that what terminated was the make-kpkg efforts to make use of the result of the successful compilation not a malfunction of the compiler itself At least I think that is what you are saying/suggesting here. It did occur to me that maybe I still need some extra package to be installed either for the compiler or make-kpkg here. Cheers MF > > Regards > > Michael > > > .-.. .. ...- . .-.. --- -. --. .- -. -.. .--. .-. --- ... .--. . .-. > > It is necessary to have purpose. > -- Alice #1, "I, Mudd", stardate 4513.3 > >
Re: kernel 4.14.15 compilation using GCC 8 in unstable.......
On 27 January 2018 at 13:38, Michael Lange wrote: > Hi, > > On Sat, 27 Jan 2018 13:12:13 + > Michael Fothergill wrote: > > > I think I will sign up on the gcc gnu help page and ask people if they > > have a test case file I can run to 100% confirm the GCC 8 compiler is > > running properly. > > Once I am convinced it is then the next stage is to try to talk to the > > developers who maintain the make-kpkg program. > > are you still using gcc-8? Here this one didn't work at all for me, > compiling always aborted early with compiler errors. It worked > immediately though after I removed ggc-8 and upgraded gcc-7 to v. 7.3 > from sid. > In my case after I took you helpful advice and installed libelf-dev in GCC 8 (which I am still using) the crash I had went away. I think now GCC 8 is close to working OK. Perhaps it needs another little nudge or some other package we don't know about. I have sent the gnu gcc help people the following email: ** Dear All, I am running debian unstable on an amd64 kaveri box. I recently installed GCC 8 from the Debian experimental site: https://packages.debian.org/experimental/devel/gcc-8 I also installed libelf-dev. It did run correctly without it. I have been using it to try to compile and install linux kernel 4.14.15 using the debian package make-kpkg. The output from doing this is here: https://pastebin.com/sgrhdCKW I copied over the config file from/boot and ran make-clean and the command: yes "" | make oldconfig before running make-kpkg. Kernel compilations I do in gentoo usually take a while. This ran too quickly I think. Something is not quite right here. Perhaps some more depedent packages needed to be installed to make GCC8 run happily. Do you have a test file I can compile that will check whether GCC 8 is really running correctly? The discussions on these two threads are relevant: https://lists.debian.org/debian-user/2018/01/msg01159.html https://lists.debian.org/debian-user/2018/01/msg01002.html We are all trying to compile kernels that defeat the meltdown and spectre vulnerabilities. Comments appreciated. Regards MF Maybe they can help here. Cheers MF > > Regards > > Michael > > .-.. .. ...- . .-.. --- -. --. .- -. -.. .--. .-. --- ... .--. . .-. > > "It's hard to believe that something which is neither seen nor > felt can do so much harm." > "That's true. But an idea can't be seen or felt. And that's > what kept the Troglytes in the mines all these centuries. A mistaken > idea." > -- Vanna and Kirk, "The Cloud Minders", stardate 5819.0 > >
Re: kernel 4.14.15 compilation using GCC 8 in unstable.......
On 27 January 2018 at 13:38, Michael Lange wrote: > Hi, > > On Sat, 27 Jan 2018 13:12:13 + > Michael Fothergill wrote: > > > I think I will sign up on the gcc gnu help page and ask people if they > > have a test case file I can run to 100% confirm the GCC 8 compiler is > > running properly. > > Once I am convinced it is then the next stage is to try to talk to the > > developers who maintain the make-kpkg program. > > are you still using gcc-8? Here this one didn't work at all for me, > compiling always aborted early with compiler errors. It worked > immediately though after I removed ggc-8 and upgraded gcc-7 to v. 7.3 > from sid. > > Regards > > > Michael > PS The maintainer of kernel-package (https://tracker.debian.org/pkg/kernel-package) that contains make-kpkg is: Manoj Srivastava . Cheers MF > .-.. .. ...- . .-.. --- -. --. .- -. -.. .--. .-. --- ... .--. . .-. > > "It's hard to believe that something which is neither seen nor > felt can do so much harm." > "That's true. But an idea can't be seen or felt. And that's > what kept the Troglytes in the mines all these centuries. A mistaken > idea." > -- Vanna and Kirk, "The Cloud Minders", stardate 5819.0 > >
Playing or Ripping UDF CD's Under jessie
I started to play an audio CD which is part of a book and ran in to an interesting problem. The CD is recorded using the UDF file system and it does play perfectly on a DVD player. When trying to mount the CD with mount -t udf /dev/sr1 /media/cdrom I got a spew of errors relating to low-level disk issues such as sector numbers, etc and it finally gave up and never mounted. The disks aren't bad and all the tested disks gave the same spew be for giving up. The fstab file has lines like: /dev/sr0/media/cdrom0 udf,iso9660 user,noauto 0 0 so it should mount either udf or iso9660 and it does mount iso9660 with no problem. I am thinking that this might be some sort of copy protection scheme which dedicated disk players can handle but computer CDROM drives can't. Is this the case or am I not mounting it right? One CDRW drive simply reports no media when you insert the disk and a Sony drive does try to mount it with the error spew. Another slightly newer P.C. running jessie also spews and dies. Thanks for any ideas. Martin mcCormick
Re: kernel 4.14.15 compilation using GCC 8 in unstable.......
On 27 January 2018 at 13:38, Michael Lange wrote: > Hi, > > On Sat, 27 Jan 2018 13:12:13 + > Michael Fothergill wrote: > > > I think I will sign up on the gcc gnu help page and ask people if they > > have a test case file I can run to 100% confirm the GCC 8 compiler is > > running properly. > > Once I am convinced it is then the next stage is to try to talk to the > > developers who maintain the make-kpkg program. > > are you still using gcc-8? Here this one didn't work at all for me, > compiling always aborted early with compiler errors. It worked > immediately though after I removed ggc-8 and upgraded gcc-7 to v. 7.3 > from sid. > > Regards > > Michael > I have sent the kernel-source package maintainer the following email: ** Dear Sir, I understand that you are the package maintainer for kernel-source ie make-kpkg etc. within debian. I am running debian unstable (Sid)on an amd64 kaveri box. I installed GCC 8 from the experimental repository. I am trying to use it to compile the kernel 4.14.15 using make-kpkg to use the fixes for the meltdown and spectre vulnerabilities. The output from doing this is here: https://pastebin.com/sgrhdCKW Make-kpkg did not create any linux-image file ..?! I copied over the config file from/boot and ran make-clean and the command: yes "" | make oldconfig before running make-kpkg. Kernel compilations I do in gentoo (I am a gentoo user as well as a debian user) usually take a while. This ran too quickly I think. Something is not quite right here I think. It might be that more dependent packages needed to be installed to make GCC8 run happily. As a result I have sent an email to the gnu gcc help site ( gcc-h...@gcc.gnu.org) asking them for a test file to check that GCC8 is running correctly. But, maybe you might say that make-kpkg needs to be upgraded in some way to work correctly here and GCC 8 ran OK... The discussions on these two threads are relevant to this case: https://lists.debian.org/debian-user/2018/01/msg01159.html https://lists.debian.org/debian-user/2018/01/msg01002.html We are all trying to compile kernels that defeat the meltdown and spectre vulnerabilities. Comments appreciated. Regards etc * Maybe will end up having to quit with GCC8 but it I am giving it one last attempt here. Cheers MF > > .-.. .. ...- . .-.. --- -. --. .- -. -.. .--. .-. --- ... .--. . .-. > > "It's hard to believe that something which is neither seen nor > felt can do so much harm." > "That's true. But an idea can't be seen or felt. And that's > what kept the Troglytes in the mines all these centuries. A mistaken > idea." > -- Vanna and Kirk, "The Cloud Minders", stardate 5819.0 > >
Re: Playing or Ripping UDF CDs Under jessie
Hi, Martin McCormick wrote: > I started to play an audio CD which is part of a book and ran in > to an interesting problem. The CD is recorded using the UDF file > system and it does play perfectly on a DVD player. First issue will be to clarify the true nature of this CD medium. Audio CDs (CD-DA) are recorded without any filesystem. There are "tracks" which usually each contain one piece of music. Tracks may be grouped by sessions. But that's rare with commercially mastered CDs. There are hybrid formats somewhere between CD-DA and CD-ROM which usually has ISO 9660 and/or UDF filesystems. The first track might contain the filesystem and further tracks contain audio or video streams. Please run one of wodim -v dev=/dev/sr0 -toc cdrskin -v dev=/dev/sr0 -toc A commercial audio CD-DA will show some tracks like: first: 1 last 10 track: 1 lba: 0 (0) 00:02:00 adr: 1 control: 0 mode: 0 track: 2 lba: 23260 (93040) 05:12:10 adr: 1 control: 0 mode: 0 track: 3 lba: 45067 ( 180268) 10:02:67 adr: 1 control: 0 mode: 0 track: 4 lba: 61932 ( 247728) 13:47:57 adr: 1 control: 0 mode: 0 track: 5 lba: 81697 ( 326788) 18:11:22 adr: 1 control: 0 mode: 0 track: 6 lba:101667 ( 406668) 22:37:42 adr: 1 control: 0 mode: 0 track: 7 lba:125462 ( 501848) 27:54:62 adr: 1 control: 0 mode: 0 track: 8 lba:143957 ( 575828) 32:01:32 adr: 1 control: 0 mode: 0 track: 9 lba:164232 ( 656928) 36:31:57 adr: 1 control: 0 mode: 0 track: 10 lba:185992 ( 743968) 41:21:67 adr: 1 control: 0 mode: 0 track:lout lba:202362 ( 809448) 45:00:12 adr: 1 control: 0 mode: -1 A CD-ROM with several data tracks and sessions: first: 1 last 4 track: 1 lba: 0 (0) 00:02:00 adr: 1 control: 4 mode: 1 track: 2 lba: 75614 ( 302456) 16:50:14 adr: 1 control: 4 mode: 1 track: 3 lba:102249 ( 408996) 22:45:24 adr: 1 control: 4 mode: 1 track:lout lba:121984 ( 487936) 27:08:34 adr: 1 control: 4 mode: -1 track: 4 lba:128884 ( 515536) 28:40:34 adr: 1 control: 4 mode: 1 track:lout lba:132116 ( 528464) 29:23:41 adr: 1 control: 4 mode: -1 Whether a track is in CD-DA or CD-ROM format does not depend on the CD medium type CD-R, CD-RW, readily pressed CD. > I got a spew of errors relating to low-level disk issues such as > sector numbers, etc and it finally gave up and never mounted. Mind to share a few examples of such messages ? > One CDRW drive simply reports no media when you insert > the disk and a Sony drive does try to mount it with the error > spew. Another slightly newer P.C. running jessie also spews and > dies. I hope it's only the mount attempt which dies. Well, you see the reactions of operating system drivers and other software. The drives' statements can be watched by the SCSI logging modes of above burn programs. Those modes are quite verbous. So one would catch their output in files in the /tmp directory: wodim -v -V dev=/dev/sr0 -toc 2>&1 | tee -i /tmp/wodim.log cdrskin -v -V dev=/dev/sr0 -toc 2>&1 | tee -i /tmp/cdrskin.log This might become interesting if the normal Table-Of-Content runs above yield surprising results. But for now, let's just see what the drive tells when properly asked. Have a nice day :) Thomas
testing running lxde cannot diplay desktop icon images
Setup Testing running as guest in vbox vm on a Solaris (openindiana) host. This OS has been in operation since before the release of stretch ... It sees little use and has exibited very few problems. I run the lxde desktop. The problem I am seeing is that the desktop starts but only diplays a small white box with a red X in it, where-ever there should be an item in the bottom panel. Like the main menu item or the iceweasel item. those and several other `normal' lxde items that reside in the bottom panel all show a small white box with red x. Something one sees when an icons image file is missing or not viewable for some reason. A right click on the Main Menu icon shows where the image file should be: /usr/share/lxde/images/xde-icon.png So to dispaly the permissions we'll show just directory and then the file: ls -ld /usr/share/lxde/images I've attached a small screen shot showing what I'm describing. I cut it down to just the bottom of the screen, but in full width.
testing running lxde cannot diplay desktop icon images
Setup Testing running as guest in vbox vm on a Solaris (openindiana) host. This OS has been in operation since before the release of stretch ... It sees little use and has exibited very few problems. I run the lxde desktop. The problem I am seeing is that the desktop starts but only diplays a small white box with a red X in it, where-ever there should be an item in the bottom panel. Like the main menu item or the iceweasel item. those and several other `normal' lxde items that reside in the bottom panel all show a small white box with red x. Something one sees when an icons image file is missing or not viewable for some reason. A right click on the Main Menu icon shows where the image file should be: /usr/share/lxde/images/xde-icon.png So to dispaly the permissions we'll show just directory and then the file: ls -ld /usr/share/lxde/images I've attached a small screen shot showing what I'm describing. I cut it down to just the bottom of the screen, but in full width.
Re: kernel 4.14.15 compilation using GCC 8 in unstable.......
On 27/01/2018 20:30, Michael Fothergill wrote: On 27 January 2018 at 13:38, Michael Lange wrote: Hi, On Sat, 27 Jan 2018 13:12:13 + Michael Fothergill wrote: I think I will sign up on the gcc gnu help page and ask people if they have a test case file I can run to 100% confirm the GCC 8 compiler is running properly. Once I am convinced it is then the next stage is to try to talk to the developers who maintain the make-kpkg program. are you still using gcc-8? Here this one didn't work at all for me, compiling always aborted early with compiler errors. It worked immediately though after I removed ggc-8 and upgraded gcc-7 to v. 7.3 from sid. Regards Michael I have sent the kernel-source package maintainer the following email: ** Dear Sir, I understand that you are the package maintainer for kernel-source ie make-kpkg etc. within debian. I am running debian unstable (Sid)on an amd64 kaveri box. I installed GCC 8 from the experimental repository. I am trying to use it to compile the kernel 4.14.15 using make-kpkg to use the fixes for the meltdown and spectre vulnerabilities. The output from doing this is here: https://pastebin.com/sgrhdCKW Make-kpkg did not create any linux-image file ..?! I copied over the config file from/boot and ran make-clean and the command: yes "" | make oldconfig before running make-kpkg. Kernel compilations I do in gentoo (I am a gentoo user as well as a debian user) usually take a while. This ran too quickly I think. Something is not quite right here I think. It might be that more dependent packages needed to be installed to make GCC8 run happily. As a result I have sent an email to the gnu gcc help site ( gcc-h...@gcc.gnu.org) asking them for a test file to check that GCC8 is running correctly. But, maybe you might say that make-kpkg needs to be upgraded in some way to work correctly here and GCC 8 ran OK... The discussions on these two threads are relevant to this case: https://lists.debian.org/debian-user/2018/01/msg01159.html https://lists.debian.org/debian-user/2018/01/msg01002.html We are all trying to compile kernels that defeat the meltdown and spectre vulnerabilities. Comments appreciated. Regards etc * Maybe will end up having to quit with GCC8 but it I am giving it one last attempt here. Cheers MF .-.. .. ...- . .-.. --- -. --. .- -. -.. .--. .-. --- ... .--. . .-. "It's hard to believe that something which is neither seen nor felt can do so much harm." "That's true. But an idea can't be seen or felt. And that's what kept the Troglytes in the mines all these centuries. A mistaken idea." -- Vanna and Kirk, "The Cloud Minders", stardate 5819.0 Hi, you need to read the kernel-package doc, it requires configuration. Read at the minimum /usr/share/doc/kernel-package/README.gz It contains all the info you need, and even gives you hints as to how to configure your system, like: " Or, alternately, you could do: --8<---cut here---start->8--- cp /usr/share/kernel-package/examples/etc/kernel/postinst.d/initramfs \ /etc/kernel/postinst.d/ cp /usr/share/kernel-package/examples/etc/kernel/postrm.d/initramfs \ /etc/kernel/postrm.d/ --8<---cut here---end--->8--- " to get a working initrd. Once it is configured you need a command that will look like: make-kpkg -j 4 --revision 1 --append_to_version -mykernel --initrd kernel_image kernel_headers to build both kernel and headers packages, and get and initrd to boot on. The default is to create the packages one level above the current directory (../). I don't think it is the maintainer to walk you through the procedure, he already wrote the docs. Building on a custom kernel is not very difficult, but it isn't as trivial as an "apt-get install", some extra work and care are required. And you may void your Debian warranty (you have none anyway) ;-) .
Re: Playing or Ripping UDF CD's Under jessie
Martin McCormick wrote: > When trying to mount the CD with > > mount -t udf /dev/sr1 /media/cdrom > > I got a spew of errors relating to low-level disk issues such as > sector numbers, etc and it finally gave up and never mounted. > I'm not sure, but isn't there a certain package / library that's needed for udf-support? Bernd
Re: kernel 4.14.15 compilation using GCC 8 in unstable.......
Hi, On Sat, 27 Jan 2018 22:30:06 +0530 "tv.deb...@googlemail.com" wrote: > Hi, you need to read the kernel-package doc, it requires configuration. > Read at the minimum /usr/share/doc/kernel-package/README.gz > It contains all the info you need, and even gives you hints as to how > to configure your system, like: > > " > Or, alternately, you could do: > --8<---cut here---start->8--- > cp /usr/share/kernel-package/examples/etc/kernel/postinst.d/initramfs > \ /etc/kernel/postinst.d/ > cp /usr/share/kernel-package/examples/etc/kernel/postrm.d/initramfs \ > /etc/kernel/postrm.d/ > --8<---cut here---end--->8--- > " > > to get a working initrd. it is certainly a good advice to read the docs before starting. But then, I admit that I never did and never configured anything for make-kpkg (besides installing required software of course) and the resulting kernel packages including the initrd's "just worked". So I guess that the OP's problem do not result from a misconfigured kernel-package (unless the OP changed some defaults for the worse) but from something else. Just a guess of course. My guess is, that the "make clean" command issued before the last build attempt failed to clean the source tree properly and the try before was not succesful either. .-.. .. ...- . .-.. --- -. --. .- -. -.. .--. .-. --- ... .--. . .-. ... bacteriological warfare ... hard to believe we were once foolish enough to play around with that. -- McCoy, "The Omega Glory", stardate unknown
Re: kernel 4.14.15 compilation using GCC 8 in unstable.......
On 27/01/2018 22:47, Michael Lange wrote: Hi, On Sat, 27 Jan 2018 22:30:06 +0530 "tv.deb...@googlemail.com" wrote: Hi, you need to read the kernel-package doc, it requires configuration. Read at the minimum /usr/share/doc/kernel-package/README.gz It contains all the info you need, and even gives you hints as to how to configure your system, like: " Or, alternately, you could do: --8<---cut here---start->8--- cp /usr/share/kernel-package/examples/etc/kernel/postinst.d/initramfs \ /etc/kernel/postinst.d/ cp /usr/share/kernel-package/examples/etc/kernel/postrm.d/initramfs \ /etc/kernel/postrm.d/ --8<---cut here---end--->8--- " to get a working initrd. it is certainly a good advice to read the docs before starting. But then, I admit that I never did and never configured anything for make-kpkg (besides installing required software of course) and the resulting kernel packages including the initrd's "just worked". So I guess that the OP's problem do not result from a misconfigured kernel-package (unless the OP changed some defaults for the worse) but from something else. Just a guess of course. My guess is, that the "make clean" command issued before the last build attempt failed to clean the source tree properly and the try before was not succesful either. Then "make-kpkg clean" may be the answer ?
Re: Playing or Ripping UDF CDs Under jessie
Hi, Bernd Gruber wrote: > I'm not sure, but isn't there a certain package / library that's needed for > udf-support? Jessie's kernel 3.16 should have full UDF support by the code in: https://github.com/torvalds/linux/tree/64aa90f26c06e1cb2aacfb98a7d0eccfbd6c1a91/fs/udf fs/udf/Kconfig points to Documentation/filesystems/udf.txt which says "Write support requires a block driver which supports writing. Currently dvd+rw drives and media support true random sector writes, and so a udf filesystem on such devices can be directly mounted read/write." man 8 mount mentions some "Mount options for udf". A few weeks ago i was able to mount a Nero-made pure UDF image. Have a nice day :) Thomas
getting the right and complete firmware
upon installing Debian stretch I got a notice about missing firmware (Atheros). I managed to find a package that, apperently, contained some of the missing firmware, since the list of missing firmware was diminished. I am still missing some firmware, I will find it eventually, but my question is: Can I be sure I have the correct and required firmware if I am not getting any errors from dmesg ? or upon boot? Is there any tool that will help me address these issues? thanks,
preferences > openbox configuration manager no start
setup: OS = Debian Testing (running as guest in a Vbox vm on an openindiana (solaris-11 offshoot [illumos powered])) Virtualbox-5.6.2 desktop=lxde I've reported a problem about the desktop icons unable to display their *.png images in another thread... the problem described below is probably part of the same root cause What I'm seeing is at the lxde main menu > preferences > openbox configuration manager When clicked nothing happens I just see the mouse cursor show the `busy' icon. Nothing ever starts After doing a few dpkg -L pkgname looking for something that might be the binary of that manager... I'm not able to find it. Even chking on a `stable' version (stretch) I can't really tell what runs when you click the openbox config manager. I guess it is reading '.config/openbox/lxde-rc.xml' Anyway, I'm not able to tell what is supposed to happen when that menu item is clicked. I can see whatever it is ... is not starting ... the `busy' mouse icon eventually stops and I get the regular mouse cursor back... takes about 10-15 seconds but configurator never appears. One thing that may be of note is that the .config/openbox/lxde-rc.xml Is getting read at login... If I make changes in that file they do show up if I relogin. But for some reason the configurator that edits that file is not starting.
Re: OT: Help with a search and replace script in Perl for a big file with no line breaks
> On Jan 27, 2018, at 12:58 AM, tomas wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Fri, Jan 26, 2018 at 03:31:37PM -0800, David Christensen wrote: > > [...] > >> I've "cleaned up" more files than I care to remember. (Perl s/// is the >> road to madness for anything but the most trivial cases.) I wanted to give >> the OP an idea of what needs to be done and the level of effort involved. > > Pretty arrogant, if you don't even know OP's problem, much > less the OP himself? Perhaps the language he is dealing with > is a regular language, in which case regex is... just what > the doctor ordered? Perhaps the OP has a proof for that? > What do you know? I have seen the OP on this list, but don't recall interacting with him/her recently. So, I had to go by the information provided in his/her post. My options included: 1. Make a guess and respond immediately. 2. Ask for more information and delay. 3. Do nothing. I chose #1. I have found that most posters ignore #2 if they receive any #1. Perhaps you had additional information you used for your reply? > Regex is a sharp tool. Much more Perl's variant, which is > a tad beyond regex. You gotta learn what it's good for and > what ain't. Like a good cook's knife. You might cut off your > toe with it, but if you want to dig a trench in your back > yard, you better use something else. > > BTW, you can build fine parsers with Perl regex. It just makes > for the first stage (lexer) (and a bit, see above), but it > works a charm. I don't disagree that Perl can be used to build lexers and parsers (and a whole lot more); but I would not limit myself to just regular expression operators. The thesis of my lexer/ parser/ data structure response can be summed up as follows: given Perl is the most sublime programming language ever invented and tends to impart laziness, impatience, and hubris upon its programmers, it is all too easy for Perl programmers to create programs quickly and easily that give correct output for trivial input, only to then expend great effort and fail miserably when attempting to enlarge those programs to deal with non-trivial and/or incorrect input (e.g. the "real world"). Therefore, Perl programmers must resist laziness, impatience, and hubris, and instead apply computer science to develop systems programming products that can be used and re-used to solve real-world problems. This has been my unending struggle with Perl (and every other programming language, for that matter). David p.s. I recently switched from a Debian laptop and Thunderbird to a MacBook Pro and Apple Mail. I don't know if Mail is doing the response indentation levels correctly, and I am unable to adjust them to my satisfaction. (Mail did include tomas' full e-mail address in the quoted text, which I consider an error; I removed the domain part.) Perhaps Mail was the root cause of the mis-attribution issues we noticed in a prior thread (?).
Re: Playing or Ripping UDF CDs Under jessie
"Thomas Schmitt" writes: > First issue will be to clarify the true nature of this CD medium. > Audio CDs (CD-DA) are recorded without any filesystem. There are "tracks" > which usually each contain one piece of music. Tracks may be grouped > by sessions. But that's rare with commercially mastered CDs. > > There are hybrid formats somewhere between CD-DA and CD-ROM which usually > has ISO 9660 and/or UDF filesystems. The first track might contain the > filesystem and further tracks contain audio or video streams. > > Please run one of > > wodim -v dev=/dev/sr0 -toc > > cdrskin -v dev=/dev/sr0 -toc > > A commercial audio CD-DA will show some tracks like: > > first: 1 last 10 > track: 1 lba: 0 (0) 00:02:00 adr: 1 control: 0 mode: 0 > track: 2 lba: 23260 (93040) 05:12:10 adr: 1 control: 0 mode: 0 > track: 3 lba: 45067 ( 180268) 10:02:67 adr: 1 control: 0 mode: 0 > track: 4 lba: 61932 ( 247728) 13:47:57 adr: 1 control: 0 mode: 0 > track: 5 lba: 81697 ( 326788) 18:11:22 adr: 1 control: 0 mode: 0 > track: 6 lba:101667 ( 406668) 22:37:42 adr: 1 control: 0 mode: 0 > track: 7 lba:125462 ( 501848) 27:54:62 adr: 1 control: 0 mode: 0 > track: 8 lba:143957 ( 575828) 32:01:32 adr: 1 control: 0 mode: 0 > track: 9 lba:164232 ( 656928) 36:31:57 adr: 1 control: 0 mode: 0 > track: 10 lba:185992 ( 743968) 41:21:67 adr: 1 control: 0 mode: 0 > track:lout lba:202362 ( 809448) 45:00:12 adr: 1 control: 0 mode: > -1 > > A CD-ROM with several data tracks and sessions: > > first: 1 last 4 > track: 1 lba: 0 (0) 00:02:00 adr: 1 control: 4 mode: 1 > track: 2 lba: 75614 ( 302456) 16:50:14 adr: 1 control: 4 mode: 1 > track: 3 lba:102249 ( 408996) 22:45:24 adr: 1 control: 4 mode: 1 > track:lout lba:121984 ( 487936) 27:08:34 adr: 1 control: 4 mode: > -1 > track: 4 lba:128884 ( 515536) 28:40:34 adr: 1 control: 4 mode: 1 > track:lout lba:132116 ( 528464) 29:23:41 adr: 1 control: 4 mode: > -1 > > Whether a track is in CD-DA or CD-ROM format does not depend on the CD > medium > type CD-R, CD-RW, readily pressed CD. Okay. What we got was surprisingly similar between a normal iso9660 audio cd that will play on any functioning CD player since 1983 and the mystery format CD . Here is the output from a normal music CD. scsidev: '/dev/sr1' devname: '/dev/sr1' scsibus: -2 target: -2 lun: -2 Linux sg driver version: 3.5.27 Wodim version: 1.1.11 SCSI buffer size: 64512 Beginning DMA speed test. Set CDR_NODMATEST environment variable if device communication breaks or freezes immediately after that. TOC Type: 1 = CD-ROM Device type: Removable CD-ROM Version: 5 Response Format: 2 Capabilities : Vendor_info: 'SONY' Identification : 'CD-RW CRX140E ' Revision : '1.0n' Device seems to be: Generic mmc CD-RW. Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-2 SWABAUDIO Supported modes: TAO PACKET SAO SAO/R96R RAW/R96R Drive buf size : 4183808 = 4085 KB Drive DMA Speed: 21942 kB/s 124x CD 15x DVD Current Secsize: 2048 first: 1 last 17 track: 1 lba: 0 (0) 00:02:00 adr: 1 control: 0 mode: 0 track: 2 lba: 19142 (76568) 04:17:17 adr: 1 control: 0 mode: 0 all the way up to track: 17 lba:351017 ( 1404068) 78:02:17 adr: 1 control: 4 mode: 1 track:lout lba:351785 ( 1407140) 78:12:35 adr: 1 control: 4 mode: -1 This is the output on the same drive from the mystery CD. scsidev: '/dev/sr1' devname: '/dev/sr1' scsibus: -2 target: -2 lun: -2 Linux sg driver version: 3.5.27 Wodim version: 1.1.11 SCSI buffer size: 64512 Beginning DMA speed test. Set CDR_NODMATEST environment variable if device communication breaks or freezes immediately after that. TOC Type: 1 = CD-ROM Device type: Removable CD-ROM Version: 5 Response Format: 2 Capabilities : Vendor_info: 'SONY' Identification : 'CD-RW CRX140E ' Revision : '1.0n' Device seems to be: Generic mmc CD-RW. Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-2 SWABAUDIO Supported modes: TAO PACKET SAO SAO/R96R RAW/R96R Drive buf size : 4183808 = 4085 KB Drive DMA Speed: 21504 kB/s 122x CD 15x DVD Current Secsize: 2048 ATIP info from disk: Indicated writing power: 5 Is not unrestricted Is not erasable Disk sub type: Medium Type A, high Beta category (A+) (3) ATIP start of lead in: -11634 (97:26/66) ATIP start of lead out: 359846 (79:59/71) Disk type:Short strategy type (Phthalocyanine or similar) Manuf. index: 3 Manufacturer: CMC Magnetics Corporation first: 1 last 20 track: 1 lba: 0 (0) 00:02:00 adr: 1 control: 0 mode: 0 track: 2 lba: 17271 (69084) 03:52:21 adr: 1 control: 0 mode: 0 all the way up to track: 19 lba:280452 ( 1121808) 62:21:27 adr: 1 control: 0 mode: 0 track: 20 lba:293350 ( 1173400) 65:1
Re: Playing or Ripping UDF CDs Under jessie
Martin McCormick wrote: > sr 1:0:1:0: [sr1] <> ASC=0xc6 ASCQ=0x2ASC=0xc6 ASCQ=0x2 > sr 1:0:1:0: [sr1] CDB: Read(10): 28 00 00 05 06 a2 00 00 02 00 > end_request: I/O error, dev sr1, sector 1317512 > Buffer I/O error on device sr1, logical block 164689 > > It looks like it probably can read normally if one skips some of the > control sectors. > > Thanks. This is interesting. IMO read error means CD is bad, dirty scratched whatever regards
Re: Playing or Ripping UDF CDs Under jessie
deloptes writes: > IMO read error means CD is bad, dirty scratched whatever > > regards Thank you but I think it is confused as the disk is brand new, part of a set and all of them spew errors when placed in a drive. They also play flawlessly in a DVD player which is one of those multimedia types that will play anything from ISO9660 CD's to DVD's. I think there is a deliberate protocol violation in the control data that is there to discourage copying as there are just too many brand new disks (6 all together) for them all to be duds. I do agree that damaged disks do normally throw these errors but it also looks like one is not supposed to mount them as file systems. In that way, they are exactly like iso9660 disks. Martin
Re: Playing or Ripping UDF CDs Under jessie
Hi, Martin McCormick wrote: > Here is the output from a normal music CD. > track: 1 lba: 0 (0) 00:02:00 adr: 1 control: 0 mode: 0 > track: 2 lba: 19142 (76568) 04:17:17 adr: 1 control: 0 mode: 0 These are audio tracks. No filesystem. Neither ISO 9660 nor UDF. > track: 17 lba:351017 ( 1404068) 78:02:17 adr: 1 control: 4 mode: 1 > track:lout lba:351785 ( 1407140) 78:12:35 adr: 1 control: 4 mode: -1 Number 17 is a data track. Not overly normal for music CDs but not uncommon either. If it contains an ISO 9660 filesystem it should be mountable by mount -t iso9660 -o sbsector=351017 /dev/sr1 /your/mount/directory It is just 1.5 MB large. So there cannot be much file content in it. > This is the output on the same drive from the mystery CD. > first: 1 last 20 > track: 1 lba: 0 (0) 00:02:00 adr: 1 control: 0 mode: 0 > track: 2 lba: 17271 (69084) 03:52:21 adr: 1 control: 0 mode: 0 > all the way up to > track: 19 lba:280452 ( 1121808) 62:21:27 adr: 1 control: 0 mode: 0 > track: 20 lba:293350 ( 1173400) 65:13:25 adr: 1 control: 0 mode: 0 These are all non-data tracks. Probably audio. They are not mountable as filesystems. Google finds me for "Linux play audio CD" this Mplayer page: https://www.cyberciti.biz/faq/linux-unix-mplayer-playing-audio-dvd-cd-using-bash-shell/ Its advise is to do with not mounted /dev/sr1 : mplayer -cdrom-device /dev/sr1 cdda:// -cache 5000 > all the way up to It would be interesting to see whether there are other track types. I see that wodim does not display session end marks, as cdrskin does. With cdrskin there is an option with better readable output cdrskin -v dev=/dev/sr1 -minfo (Not to be confused with option -msinfo.) It will display session numbers and track numbers like: Track Sess Type Start Addr End Addr Size == 1 1 Audio 0 23259 23260 2 1 Audio 23260 45066 21807 3 1 Audio 45067 61931 16865 4 1 Audio 61932 81696 19765 5 1 Audio 81697 101666 19970 6 1 Audio 101667 125461 23795 7 1 Audio 125462 143956 18495 8 1 Audio 143957 164231 20275 9 1 Audio 164232 185991 21760 10 1 Audio 185992 202361 16370 or Track Sess Type Start Addr End Addr Size == 1 1 Data 0 64211 64212 2 2 Data 75614 95346 19733 3 3 Data 102249 121981 19733 4 4 Data 128884 132113 3230 Please post full lists without "all the way up". > sr 1:0:1:0: [sr1] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE > sr 1:0:1:0: [sr1] Sense Key : Illegal Request [current] Info fld=0x506a2 > sr 1:0:1:0: [sr1] <> ASC=0xc6 ASCQ=0x2ASC=0xc6 ASCQ=0x2 > sr 1:0:1:0: [sr1] CDB: Read(10): 28 00 00 05 06 a2 00 00 02 00 end_request: > I/O error, dev sr1, sector 1317512 > Buffer I/O error on device sr1, logical block 164689 The failed SCSI command tried to read two blocks starting at block 0x506a2 = 329378. The error message formatters multiply this number by 4 to get 1317512, and divide it by 2 to get 164689. (We laugh, so we don't have to cry.) The error code indicates that the drive refused to perform this command. Righteously, because the address 329378 is far behind the last track end at block 306750. It is not clear to me which part of Linux or systemd came to the idea of reading that block. It was futile and not very smart. Unless there is a data track among the skipped ones in your track list, none of the blocks of the mystery CD would be readable by SCSI command READ(10). Only commands READ CD or READ CD MSF will do. > It looks like it probably can read normally if one skips some of the > control sectors. The words "control" and "mode" stem from SCSI specs. They apply to the whole track. MMC-5, table 17 says: "CONTROL The Control Field has 4 bits that define the type of information in the frame: 00x0b = 2 audio channels without pre-emphasis 00x1b = 2 audio channels with pre-emphasis of 50/15 μs 10x0b = 4 audio channels without pre-emphasis 10x1b = 4 audio channels with pre-emphasis of 50/15 μs 01x0b = Data track, recorded uninterrupted 01x1b = Data track, recorded increment 11xxb = reserved xx0xb = digital copy prohibited xx1xb = digital copy permitted The bits of the control field (except for the copy bit) may change during a pause (X=00) of at least 2 seconds and during the Lead-in area only." You showed tracks with these control values: 0 = b = 2 audio channels without pre-emphasis and without copy permission (which nobody cares about) 4 = 0100b = Data track, recorded uninter
Re: Playing or Ripping UDF CDs Under jessie
Martin McCormick wrote: > I think there is a deliberate protocol violation in the > control data that is there to discourage copying as there are > just too many brand new disks (6 all together) for them all to be > duds. I do agree that damaged disks do normally throw these > errors but it also looks like one is not supposed to mount them > as file systems. In that way, they are exactly like iso9660 > disks. if disks are new and drive is also ok, could be indeed some nasty magic put in place to prevent copying, or something new that is not implemented in the software you have (on jessie) in any case no one can take the power of dd away :D regards
Re: Playing or Ripping UDF CDs Under jessie
"Thomas Schmitt" writes: > Hi, > > Martin McCormick wrote: > > Here is the output from a normal music CD. > > track: 1 lba: 0 (0) 00:02:00 adr: 1 control: 0 mode: 0 > > track: 2 lba: 19142 (76568) 04:17:17 adr: 1 control: 0 mode: 0 > > These are audio tracks. No filesystem. Neither ISO 9660 nor UDF. > > > track: 17 lba:351017 ( 1404068) 78:02:17 adr: 1 control: 4 mode: 1 > > track:lout lba:351785 ( 1407140) 78:12:35 adr: 1 control: 4 mode: > -1 > > Number 17 is a data track. Not overly normal for music CDs but not > uncommon > either. > > If it contains an ISO 9660 filesystem it should be mountable by > > mount -t iso9660 -o sbsector=351017 /dev/sr1 /your/mount/directory > > It is just 1.5 MB large. So there cannot be much file content in it. > > > > This is the output on the same drive from the mystery CD. > > first: 1 last 20 > > track: 1 lba: 0 (0) 00:02:00 adr: 1 control: 0 mode: 0 > > track: 2 lba: 17271 (69084) 03:52:21 adr: 1 control: 0 mode: 0 > > all the way up to > > track: 19 lba:280452 ( 1121808) 62:21:27 adr: 1 control: 0 mode: 0 > > track: 20 lba:293350 ( 1173400) 65:13:25 adr: 1 control: 0 mode: 0 > > These are all non-data tracks. Probably audio. They are not mountable > as filesystems. > > Google finds me for "Linux play audio CD" this Mplayer page: > > https://www.cyberciti.biz/faq/linux-unix-mplayer-playing-audio-dvd-cd-using-bash-shell/ > Its advise is to do with not mounted /dev/sr1 : > > mplayer -cdrom-device /dev/sr1 cdda:// -cache 5000 > > > > all the way up to > > It would be interesting to see whether there are other track types. > I see that wodim does not display session end marks, as cdrskin does. > With cdrskin there is an option with better readable output > > cdrskin -v dev=/dev/sr1 -minfo > > (Not to be confused with option -msinfo.) > It will display session numbers and track numbers like: > > Track Sess Type Start Addr End Addr Size > == > 1 1 Audio 0 23259 23260 > 2 1 Audio 23260 45066 21807 > 3 1 Audio 45067 61931 16865 > 4 1 Audio 61932 81696 19765 > 5 1 Audio 81697 101666 19970 > 6 1 Audio 101667 125461 23795 > 7 1 Audio 125462 143956 18495 > 8 1 Audio 143957 164231 20275 > 9 1 Audio 164232 185991 21760 > 10 1 Audio 185992 202361 16370 > > or > > Track Sess Type Start Addr End Addr Size > == > 1 1 Data 0 64211 64212 > 2 2 Data 75614 95346 19733 > 3 3 Data 102249 121981 19733 > 4 4 Data 128884 132113 3230 > > Please post full lists without "all the way up". I am sorry. I will play with wodim and cdrskin to see what these tools can tell me and post when there is something new to report. I want to be able to play the audio files through mplayer which can allow one to speed up the playback tempo without changing the pitch of the voice which was why I started this project in the first place. I looked at a CD containing a file system made with mkisofs which is mountable and it is drastically different in that there is 1 disk-sized data track and no LBA tracks at all. > > sr 1:0:1:0: [sr1] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE > > sr 1:0:1:0: [sr1] Sense Key : Illegal Request [current] Info > fld=0x506a2 > > sr 1:0:1:0: [sr1] <> ASC=0xc6 ASCQ=0x2ASC=0xc6 ASCQ=0x2 > > sr 1:0:1:0: [sr1] CDB: Read(10): 28 00 00 05 06 a2 00 00 02 00 > end_request: I/O error, dev sr1, sector 1317512 > > Buffer I/O error on device sr1, logical block 164689 > > The failed SCSI command tried to read two blocks starting at block > 0x506a2 = 329378. > The error message formatters multiply this number by 4 to get 1317512, > and divide it by 2 to get 164689. (We laugh, so we don't have to cry.) > > The error code indicates that the drive refused to perform this command. > Righteously, because the address 329378 is far behind the last track end > at block 306750. > It is not clear to me which part of Linux or systemd came to the idea > of reading that block. It was futile and not very smart. > > Unless there is a data track among the skipped ones in your track list, > none of the blocks of the mystery CD would be readable by SCSI command > READ(10). Only commands READ CD or READ CD MSF will do. > > > > It looks like it probably can read normally if one skips some of the > > control sectors. > > The words "control" and "mode" stem from SCSI specs. They apply to the > whole track. MMC-5, table 17 says: > "CONTROL >The Control Field has 4 bits that define the type of information in >the frame: > 00x0b = 2 audio channels without pre-emphasis > 0
Re: Playing or Ripping UDF CDs Under jessie
"Thomas Schmitt" writes: > I see that wodim does not display session end marks, as cdrskin does. cdrskin to the rescue. > With cdrskin there is an option with better readable output > > cdrskin -v dev=/dev/sr1 -minfo > > (Not to be confused with option -msinfo.) > It will display session numbers and track numbers like: > > Track Sess Type Start Addr End Addr Size > == > 1 1 Audio 0 23259 23260 > 2 1 Audio 23260 45066 21807 > 3 1 Audio 45067 61931 16865 > 4 1 Audio 61932 81696 19765 > 5 1 Audio 81697 101666 19970 > 6 1 Audio 101667 125461 23795 > 7 1 Audio 125462 143956 18495 > 8 1 Audio 143957 164231 20275 > 9 1 Audio 164232 185991 21760 > 10 1 Audio 185992 202361 16370 > > or > > Track Sess Type Start Addr End Addr Size > == > 1 1 Data 0 64211 64212 > 2 2 Data 75614 95346 19733 > 3 3 Data 102249 121981 19733 > 4 4 Data 128884 132113 3230 > > Please post full lists without "all the way up". Here is what I did so far and it works. I ran cdrskin on one of the disks from /dev/sr1 ATIP start of lead in: -11634 (97:26/66) ATIP start of lead out: 359846 (79:59/71) 1T speed low: 8 1T speed high: 8 Producer: CMC Magnetics Corporation Manufacturer: CMC Magnetics Corporation Mounted media class: CD Mounted media type: CD-ROM Disk Is not erasable disk status: complete session status: complete first track: 1 number of sessions: 1 first track in last sess: 1 last track in last sess: 20 Disk Is not unrestricted Disk type: CD-DA or CD-ROM Track Sess Type Start Addr End Addr Size == 1 1 Audio 0 17270 17271 2 1 Audio 17271 33862 16592 3 1 Audio 33863 49554 15692 4 1 Audio 49555 64594 15040 5 1 Audio 64595 81015 16421 6 1 Audio 81016 94659 13644 7 1 Audio 94660 108516 13857 8 1 Audio 108517 123667 15151 9 1 Audio 123668 136320 12653 10 1 Audio 136321 148048 11728 11 1 Audio 148049 163696 15648 12 1 Audio 163697 182745 19049 13 1 Audio 182746 200379 17634 14 1 Audio 200380 217756 17377 15 1 Audio 217757 234016 16260 16 1 Audio 234017 249782 15766 17 1 Audio 249783 266826 17044 18 1 Audio 266827 280451 13625 19 1 Audio 280452 293349 12898 20 1 Audio 293350 306750 13401 Last session start address: 0 Last session leadout start address: 306751 Read capacity: 306751 The very first track 1 1 Audio 0 17270 17271 is what drives computers mad. It would correspond to track0.cdda.wav and appears to contain information that looks like a bad disk or otherwise pours sugar in to the fuel tank of a normal ripping process. So, what would happen if I ripped from track 1 instead of 0 using cdparanoia? #!/bin/sh drivespec=/dev/cdrom3 cdparanoia -d $drivespec "1-" -rw-r--r-- 1 martin martin 721478396 Jan 27 21:52 cdda.wav It plays but you lose the individual track boundaries as you see in the listing above. I noticed that it occasionally repeated what amounts to one revolution of the disk so a word or 2 might stutter but after track0, it's red-blooded orange book. How about that as a meta fore? Or is it the red book for audio CD's? I thought it was udf because one of the two systems I tried it on spewed out a reference to udffs in one of the myriad error messages it flung when I tried to mount it originally. I might be able to restore the individual tracks by feeding the output of cdrskin in to a perl program if cdparanoia can't be persuaded to extract them any other way. This is fun isn't it? By the way, mplayer, set to do tempo compression worked fine speeding up the audio. Thanks to all who helped. Martin
Re: Playing or Ripping UDF CDs Under jessie
May I suggest cdparanoia? I'm calling it with Python, and it's a lovely piece of software. Makes wavs of everything I've thrown at it, with good info on the screen and all the tracks are on my HDD, with no silliness. -- Glenn English
