Re: [arch-general] After upgrade

2016-12-02 Thread piequiex
-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.9565

Re: [arch-general] After upgrade

2016-12-02 Thread piequiex
-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 dhrfgvb

Re: [arch-general] After upgrade

2016-12-02 Thread Martin Kühne via arch-general
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 s

Re: [arch-general] abs & sourceforge.net

2016-12-02 Thread Martin Kühne via arch-general
asynchronous inode failure. cheers! mar77i

Re: [arch-general] After upgrade

2016-12-02 Thread Martin Kühne via arch-general
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] After upgrade

2016-12-02 Thread Bennett Piater
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

Re: [arch-general] Installation: How to get HDD > LUKS > GPT working in a clean way

2016-12-02 Thread Merlin Büge
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

Re: [arch-general] After upgrade

2016-12-02 Thread Doug Newgard
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] After upgrade

2016-12-02 Thread piequiex
-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

Re: [arch-general] After upgrade

2016-12-02 Thread Martin Kühne via arch-general
Your mail is being routed through Germany ... and they're censoring us. cheers! mar77i

Re: [arch-general] After upgrade

2016-12-02 Thread Doug Newgard
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.

[arch-general] Stronger Hashes for PKGBUILDs

2016-12-02 Thread fnodeuser
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