[arch-general] Stronger Hashes for PKGBUILDs
https://lists.archlinux.org/pipermail/arch-dev-public/2016-November/028492.html i have a few things to add to this. the message digests at the download page for the .iso file, must change to sha256 and sha512 ones, or to a sha512 one. if an upstream does not sign the files, does not have https enabled, and/or refuses to take security and privacy seriously, sha512 must be used in the PKGBUILD files. in the cases of upstreams that use md5 and/or sha1 message digests, those will be added in a second ALGOsums= line under the sha512sums= line. if they use md5 and sha1, then sha1sums must be used for the second ALGOsums= line.
Re: [arch-general] After upgrade
On Sat, 3 Dec 2016 00:30:43 + (GMT) piequiex wrote: > > Whatever you expected to happen. I'm going to go through a few things > The logical conclusion. Logical conclusion: It crashed. What more do you want us to say? We're not kernel devs.
Re: [arch-general] After upgrade
Your mail is being routed through Germany ... and they're censoring us. cheers! mar77i
Re: [arch-general] After upgrade
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > On Fri, Dec 2, 2016 at 6:25 PM, piequiex wrote: > >> [ 66.078059] RIP [] __memmove+0x24/0x1a0 > >> [ 66.080161] RSP > >> [ 66.082193] CR2: 81e0 > >> [ 66.084178] ---[ end trace 7fe3870b4855ddc6 ]--- > >> - -- > >> Have a nice day! > >> > >> > >> You too! > > Useless message. > > P.S. Adjust MUA setings. > > > > Whatever you expected to happen. I'm going to go through a few things The logical conclusion. > give some context and some information about what you upgraded, what > you were doing when it happened and what software was running. Looking Read original message. On boot. > You may not post a stacktrace to the mailing list though, ESPECIALLY "Not enough details" someone may say in this case. - -- Have a nice day! ~~~ This PGP signature only certifies the sender and date of the message. It implies no approval from the administrators of nym.mixmin.net. Date: Sat Dec 3 00:30:43 2016 GMT From: piequ...@nym.mixmin.net -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlhCEjMACgkQViYZwngkfDt5wACcDJE95jRYeqEmHIvEze489npj I88AoI43xVkmNbaVMk0dhtqBYU6e8OXg =eDLV -END PGP SIGNATURE-
Re: [arch-general] After upgrade
On Fri, 2 Dec 2016 17:25:57 + (GMT) piequiex wrote: > > Have a nice day! > > > > > > You too! > Useless message. > P.S. Adjust MUA setings. Just as useless as you original message. pgpX_4Ngnv0my.pgp Description: OpenPGP digital signature
Re: [arch-general] Installation: How to get HDD > LUKS > GPT working in a clean way
Hi, > > Hm. I can see your points. But I don't need the flexibility LVM provides, > > I have enough flexibility through Btrfs. > > And yeah, it's readily automated, and that's indeed practical for many > > people. Personally, I'd rather modify the start-up process a tiny bit > > so that GPT inside LUKS gets parsed. I just try to strip off unnecessary > > 'overhead' / layers of my system. > Okay, then. > > Here's my opinion on this approach. > > If you have 8 GiB or more and not hibernating, don't bother with swap, > it'd be a waste of disk space. In that case you could just put a btrfs > volume straight on the LUKS container without the GPT. Problem solved as > you don't need any more volume management than opening LUKS containers. > > Otherwise WITH swap: Unfortunately btrfs (still) doesn't support swap > files properly, otherwise I'd suggest using them. You can write a custom > hook. Unless you plan to share it, I'd make it a dead simple shell > script that simply reruns the command to scan for added GPT partitions > for your specific setup. Make sure you have a setup hook that gets the > dependencies in there. > > Personally, I still think you should just use LVM, for the simple reason > you're having trouble with GPT, which is not meant for being used like > this, since it can work as a more flexible "partition table" inside the > LUKS container and is better supported all around. btrfs really doesn't > act as a good replacement for logical volumes, in my experience. Having > something with more features than you need is better than trying to > coerce something into working ways it's not really intended. Thanks for your input! I've reconsidered LVM twice now but still feel better without it. Cheers, Merlin -- Merlin Büge
Re: [arch-general] After upgrade
I prever ancient greek, so here you go: τῇ καλλίστῃ :) I knew it would pay of to learn that :D Cheers, Bennett On 12/02/2016 06:53 PM, Martin Kühne via arch-general wrote: > Wait a minute, wait a minute. > I just realized some crucial aspect of your fnord. > You stripped the context yourself, ad on purpose. > That's some seriously τη καλλίστη stuff you got there. > > cheers! > mar77i > -- GPG fingerprint: 871F 1047 7DB3 DDED 5FC4 47B2 26C7 E577 EF96 7808 signature.asc Description: OpenPGP digital signature
Re: [arch-general] After upgrade
Wait a minute, wait a minute. I just realized some crucial aspect of your fnord. You stripped the context yourself, ad on purpose. That's some seriously τη καλλίστη stuff you got there. cheers! mar77i
Re: [arch-general] abs & sourceforge.net
asynchronous inode failure. cheers! mar77i
Re: [arch-general] After upgrade
On Fri, Dec 2, 2016 at 6:25 PM, piequiex wrote: >> [ 66.078059] RIP [] __memmove+0x24/0x1a0 >> [ 66.080161] RSP >> [ 66.082193] CR2: 81e0 >> [ 66.084178] ---[ end trace 7fe3870b4855ddc6 ]--- >> - -- >> Have a nice day! >> >> >> You too! > Useless message. > P.S. Adjust MUA setings. > Whatever you expected to happen. I'm going to go through a few things now, because how people reacted to what you sent was neither unexpected nor unjustified. You basically did the same thing to this mailing list that the kernel did to you. We do not deserve this. But you're not a machine. You can give some context and some information about what you upgraded, what you were doing when it happened and what software was running. Looking at some of the details, it seems like you were running a shell in the linux console - probably with nvidia kms running. Was X11 running? You may not post a stacktrace to the mailing list though, ESPECIALLY one with NO CONTEXT WHATSOEVER automatically OR IN YOUR OWN WORDS attached, because literally nobody can help you now. The stacktrace doesn't contain any information about what part of the system broke, but you coulld have told yourself if you had actually looked at it. The literally best thing I can do for you is respond with BOFH excuse: Our POP server was kidnapped by a weasel. cheers! mar77i
Re: [arch-general] After upgrade
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > Hi, > > http://bfy.tw/8wi1 #YZTGSL Ybtb pbybe fznyy GUVF vf gur vagrearg. GURFR yrg lbh frnepu vg. freivpr.cerfragngvba freivpr.cerfragngvba (gurer'f zber, gurfr ner whfg gur zbfg cbchyne) Arkg gvzr lbh unir n dhrfgvba V erpbzzraq hfvat: freivpr.cerfragngvba Vg jbexf yvxr GUVF... NobhgCevinplPbagnpg@YZTGSL Ohl FgvpxrefYvir Fgernz © YZTGSL, 2009-2016 | Tbbtyr(E) vf n ertvfgrerq genqrznex bs Tbbtyr Vap. YZTGSL vf abg raqbefrq ol, fcbafberq ol, be nssvyvngrq jvgu Tbbtyr Vap. > Regards, > Ralf > > PS: > https://lists.archlinux.org/pipermail/arch-general/2016-November/042594.html > > https://lists.archlinux.org/pipermail/arch-general/2016-November/042594.html - -- Have a nice day! ~~~ This PGP signature only certifies the sender and date of the message. It implies no approval from the administrators of nym.mixmin.net. Date: Fri Dec 2 17:36:01 2016 GMT From: piequ...@nym.mixmin.net -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlhBsQEACgkQViYZwngkfDvZnwCcDGcvEk1XgxqQrUsUyLdE1Pea ejcAn2y+W93OQkkLgERJzDw4vscpXZVt =F0OO -END PGP SIGNATURE-
Re: [arch-general] After upgrade
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > On 2 Dec 2016 6:47 am, "piequiex" wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > upgraded linux (4.8.10-1 -> 4.8.11-1) > 4.8.11-1-ARCH > [ 65.955101] BUG: unable to handle kernel paging request at > 81e0 > [ 65.956510] IP: [] __memmove+0x24/0x1a0 > [ 65.957874] PGD 1a09067 PUD 1a0a063 PMD 0 > [ 65.959198] Oops: [#17] PREEMPT SMP > [ 65.960489] Modules linked in: nf_log_ipv4 nf_log_common xt_LOG > ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_pkttype nf_conntrack_ipv4 > nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_filter bnep > sha256_mb mcryptd sha256_ssse3 sha256_generic dm_crypt joydev dm_mod > hid_rmi dell_wmi sparse_keymap mxm_wmi btusb mousedev btrtl uvcvideo btbcm > btintel bluetooth videobuf2_vmalloc rtsx_usb_ms videobuf2_memops > videobuf2_v4l2 videobuf2_core videodev media memstick intel_rapl dell_led > iTCO_wdt iTCO_vendor_support x86_pkg_temp_thermal coretemp dell_laptop > dell_smbios dcdbas snd_soc_rt5640 elan_i2c snd_hda_codec_hdmi > snd_hda_codec_realtek snd_hda_codec_generic snd_soc_rl6231 snd_soc_core > snd_compress kvm irqbypass crct10dif_pclmul crc32_pclmul crc32c_intel > ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul > [ 65.972470] glue_helper ablk_helper cryptd r8169 intel_cstate > intel_rapl_perf pcspkr input_leds snd_pcm_dmaengine mac_hid i2c_hid > snd_hda_intel i2c_i801 i2c_smbus ac97_bus snd_hda_codec > i2c_designware_platform i2c_designware_core mei_me snd_soc_sst_acpi mii > thermal battery ac spi_pxa2xx_platform snd_soc_sst_match 8250_dw i915 wmi > snd_hda_core video drm_kms_helper snd_hwdep intel_gtt syscopyarea > sysfillrect dell_rbtn tpm_tis sysimgblt button fb_sys_fops tpm_tis_core > i2c_algo_bit tpm mei shpchp lpc_ich fjes sch_fq_codel sg ip_tables x_tables > ext4 crc16 jbd2 fscrypto mbcache rtsx_usb_sdmmc rtsx_usb hid_generic usbhid > hid sr_mod cdrom sd_mod serio_raw atkbd libps2 dell_smm_hwmon ahci libahci > libata scsi_mod xhci_pci ehci_pci ehci_hcd xhci_hcd usbcore usb_common > i8042 serio sdhci_acpi sdhci led_class > [ 65.988729] mmc_core evdev speedstep_lib snd_pcm_oss snd_mixer_oss > snd_pcm snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_timer snd > soundcore wl(PO) cfg80211 rfkill nvidia(PO) drm > [ 65.993921] CPU: 2 PID: 892 Comm: loadkeys Tainted: P DO > 4.8.11-1-ARCH #1 > [ 65.999240] task: 8801144a0e40 task.stack: 88011451 > [ 66.001963] RIP: 0010:[] [] > __memmove+0x24/0x1a0 > [ 66.004774] RSP: 0018:880114513cf0 EFLAGS: 00010246 > [ 66.007584] RAX: 81aa2742 RBX: 0017 RCX: > 8801a5516e9f > [ 66.010453] RDX: 8801a587475d RSI: 81e0 RDI: > 81e0 > [ 66.013328] RBP: 880114513d48 R08: 8801198fec00 R09: > 813f8fda > [ 66.016231] R10: R11: 0246 R12: > > [ 66.019184] R13: 880127316e7d R14: 81aa2742 R15: > 8801198fec00 > [ 66.022165] FS: 7f900658e480() GS:88012fb0() > knlGS: > [ 66.025209] CS: 0010 DS: ES: CR0: 80050033 > [ 66.028204] CR2: 81e0 CR3: 00011444d000 CR4: > 001406e0 > [ 66.031219] Stack: > [ 66.034191] 813f92dc 8801009f 8801198fec01 > 0016 > [ 66.037305] 1f326800 880127316e9f 88011f326800 > 88011f326800 > [ 66.040367] 4b49 88012b010800 > 880114513dc8 > [ 66.043353] Call Trace: > [ 66.046208] [] ? vt_do_kdgkb_ioctl+0x34c/0x450 > [ 66.049051] [] vt_ioctl+0x8df/0x12a0 > [ 66.051806] [] ? touch_atime+0x33/0xd0 > [ 66.054481] [] ? generic_file_read_iter+0x65b/0x840 > [ 66.057111] [] tty_ioctl+0x365/0xc70 > [ 66.059639] [] ? lru_cache_add_active_or_ > unevictable+0x36/0xb0 > [ 66.062150] [] ? __vfs_read+0xe1/0x130 > [ 66.064583] [] do_vfs_ioctl+0xa3/0x5f0 > [ 66.066914] [] ? vfs_read+0x96/0x130 > [ 66.069176] [] SyS_ioctl+0x79/0x90 > [ 66.071345] [] entry_SYSCALL_64_fastpath+0x1a/0xa4 > [ 66.073473] Code: 90 90 90 90 90 90 90 48 89 f8 48 83 fa 20 0f 82 03 01 > 00 00 48 39 fe 7d 0f 49 89 f0 49 01 d0 49 39 f8 0f 8f 9f 00 00 00 48 89 d1 > a4 c3 48 81 fa a8 02 00 00 72 05 40 38 fe 74 3b 48 83 ea 20 > [ 66.078059] RIP [] __memmove+0x24/0x1a0 > [ 66.080161] RSP > [ 66.082193] CR2: 81e0 > [ 66.084178] ---[ end trace 7fe3870b4855ddc6 ]--- > - -- > Have a nice day! > > > You too! Useless message. P.S. Adjust MUA setings. - -- Have a nice day! ~~~ This PGP signature only certifies the sender and date of the message. It implies no approval from the administrators of nym.mixmin.net. Date: Fri Dec 2 17:25:57 2016 GMT From: piequ...@nym.mixmin.net -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlhBrqUACgkQViYZwngkfDt/pACeK72wX0lbMY03QnIbJt4uRXQz WXMAnAiiaSEdIa8+LLGqZwj2p9gv0kyd =VMvK -END PGP SIGNATURE-
