Re: [arch-general] Is ATI more... compatible?
Dimitris, You may find this news interesting: http://www.phoronix.com/scan.php?page=news_itempx=MTY4MTc -- Kind regards, Damian Nowak StratusHost www.AtlasHost.eu
Re: [arch-general] Is ATI more... compatible?
On May 5, 2014 3:11 PM, Nowaker enwuk...@gmail.com wrote: Dimitris, You may find this news interesting: http://www.phoronix.com/scan.php?page=news_itempx=MTY4MTc -- Kind regards, Damian Nowak StratusHost www.AtlasHost.eu Will I need a new mobo for this? Or it's just sofware?
Re: [arch-general] Comment on: Use systemd timers instead of /etc/cron.{hourly, daily, weekly, monthly}?
I have been testing the issue for a week. Daily timers are fired between 0:00 and 0:01 without exception - all timers at the same time, all machines at the same time, every day at the same time. The largest variation I have seen was 30 seconds. So yes, there is definitely an issue with AccuracySec=12h not being honored. However, whether timer accuracy is 30 seconds or 12 hours, this makes little difference to me, as both are unacceptable without the possibility to customize timer elapse time. I have reverted all my Arch machines to previous cron-based config and intend to keep it this way. Perhaps it is not cool, but at least it works. Which brings me to what I consider the most important problem here. Having read the original thread on arch-dev-public I was left with an impression that perceived coolness of the new setup took precedence over consideration of its impact. As a result, modification has been released without sufficient testing, as we can clearly see now. It did not help that discussion was carried on a mailing list that does not allow user comments. Perhaps a larger audience would have allowed a consideration of alternative solutions. An example of such a solution would be hourly/daily/monthly/weekly timers that execute scripts from relevant /etc/cron.* directories. That would allow for removal of cronie while sidestepping timer elapse problems that we are discussing here. It would also have a benefit of handling all cron tasks in addition to logrotate/updatedb/man-db/shadow. Thanks Maciej Puzio
Re: [arch-general] Installing Archlinux alongside Ubuntu on aWindows8 UEFI laptop
Following up, I have taken more steps, with partial success. The following two steps were taken: 1. Installed Kubuntu the same way I originally insalled Ubuntu. This time I noticed that the system booted in a BIOS and not UEFI state. The result was that now two Ubuntu entries are found in Grub. Grub is still only available after booting Windows 8.1, and rebooting through the Advanced Boot Settings facility. 2. Installed Manjaro, and this time I walked through the System Settings (BIOS, so to speak) and set the system into EFI mode. As best I recall. The system installed, and when I rebooted, a GRUB menu is presented with these three GNU/Linux boot options, but Windows 8.1 is no longer seen as available. I don't care for now about Windows 8.1. I hope it shows up later if necessary, by switching the BIOS back to BIOS mode. I had to identify the EFI partition. Manjaro's installation tool was very helpful in directing me to specify an EFI partition, which I was able to idenify with gdisk. Can I safely treat this Manjaro as an Arch installation? I did this with Antergos a couple of years ao, and it worked out fine. Will I run into a roadblock down the road? Thank you for the many hellpful comments. Alan Davis On Sun, May 4, 2014 at 9:52 AM, Daniel Meer meerd...@gmail.com wrote: On 05/03/2014 04:55 PM, Delcypher wrote: On 3 May 2014 05:53, Alan E. Davis lngn...@gmail.com wrote: I have installed Archlinux on a partition, with a home partition. I just cannot boot into it. I was able to boot into the USB flash drive. I never saw any messages about UEFI or legacy. The USB image supports legacy and UEFI boot. I'm not 100% sure if this is a reliable method but when I boot up via legacy the /sys/firmware/efi folder does not exist but when I boot via UEFI the folder does exist. There is probably a way on your machine to disable legacy boot and also select to boot from USB when legacy boot is disabled. When I installed Arch alongside Windows 8, I had the same problem that it didn't offer me a UEFI boot option. I think I had to disable CSM (Compatibility Support Module) in my BIOS settings. After that, it worked perfectly. It will probably not be the same for you, since I have an Asus BIOS. But the option was about some non-UEFI driver add-on devices. Hope that helps.
Re: [arch-general] Comment on: Use systemd timers instead of /etc/cron.{hourly, daily, weekly, monthly}?
On 05-05-14 15:05, Maciej Puzio wrote: Perhaps a larger audience would have allowed a consideration of alternative solutions. An example of such a solution would be hourly/daily/monthly/weekly timers that execute scripts from relevant /etc/cron.* directories. That would allow for removal of cronie while sidestepping timer elapse problems that we are discussing here. It would also have a benefit of handling all cron tasks in addition to logrotate/updatedb/man-db/shadow. Thanks Maciej Puzio That sounds like a good idea. Instead of removing the entire cron system, this would allow systemd-timers to function as an alternative to cron. it would also reduce the increasing dependency archlinux has on systemd as init system. Lone_Wolf
[arch-general] Fwd: Installing Archlinux alongside Ubuntu on aWindows8 UEFI laptop
I tried several times, without any change to the boot menu. The SDD device (perhaps a specific part) and also a windows boot manager are items in a menu when rebooting with Advanced Startup from Windows. The steps I used were: - Ran grub-mkconfig -o /boot/grub/grub.cfg - changed the permissions of that file to +w - re-ran grub-mkconfig Why are you doing this? You generally shouldn't need to set the +w on /boot/grub/grub.cfg. It should be set correctly for from the beginning. Remember you should be root or using sudo when running grub-mkconfig to write to /boot/grub/grub.cfg $ ls -l /boot/grub/grub.cfg -rw--- 1 root root 6209 Apr 22 18:29 /boot/grub/grub.cfg Each time I ran this, it saw the Arch partition. And each time I booted, this was not found in the grub menu at boot time. It was shown as 1. You should check the contents /boot/grub/grub.cfg actually contains the menu entries for Arch Linux 2. If you do see Arch Linux the menu entries in /boot/grub/grub.cfg but then don't see them at boot then that mostly likely means /boot/grub does not contain the grub files you are actually using at boot time (i.e. your /boot is mounting the wrong thing!). Either that or the menu you're looking at when booting isn't even GRUB!
Re: [arch-general] Installing Archlinux alongside Ubuntu on aWindows8 UEFI laptop
Can I safely treat this Manjaro as an Arch installation? I did this with Antergos a couple of years ao, and it worked out fine. Will I run into a roadblock down the road? Antergos is Arch Linux, Manjaro isn't. signature.asc Description: OpenPGP digital signature
Re: [arch-general] Comment on: Use systemd timers instead of /etc/cron.{hourly, daily, weekly, monthly}?
Am 05.05.2014 15:05, schrieb Maciej Puzio: I have been testing the issue for a week. Daily timers are fired between 0:00 and 0:01 without exception - all timers at the same time, all machines at the same time, every day at the same time. The largest variation I have seen was 30 seconds. So yes, there is definitely an issue with AccuracySec=12h not being honored. However, whether timer accuracy is 30 seconds or 12 hours, this makes little difference to me, as both are unacceptable without the possibility to customize timer elapse time. Of course you can configure the elapse time, by adjusting the associated .timer unit. With anacron, there was no way to adjust the time, so this is a step forward. signature.asc Description: OpenPGP digital signature
Re: [arch-general] Comment on: Use systemd timers instead of /etc/cron.{hourly, daily, weekly, monthly}?
Hi, On Mon, 5 May 2014 08:05:08 -0500 Maciej Puzio mx34...@gmail.com wrote: I have been testing the issue for a week. Daily timers are fired between 0:00 and 0:01 without exception - all timers at the same time, all machines at the same time, every day at the same time. The largest variation I have seen was 30 seconds. So yes, there is definitely an issue with AccuracySec=12h not being honored. AFAIU systemd is supposed to start timers randomly in the time interval [1d, 1d + 12h]; different timers are started in parallel. Are you arguing that the starting time is not random enough? However, whether timer accuracy is 30 seconds or 12 hours, this makes little difference to me, as both are unacceptable without the possibility to customize timer elapse time. I have reverted all my Arch machines to previous cron-based config and intend to keep it this way. Perhaps it is not cool, but at least it works. You misunderstood the point here. Systemd timers (at least in the current form) are _not_ cron replacement. However, they are adequate for daily maintainance jobs that are shipped with packages. If you had custom, carefully scheduled cron jobs, you should continue using cronie. What I don't understand is why do you care when man-db/updatedb runs? An example of such a solution would be hourly/daily/monthly/weekly timers that execute scripts from relevant /etc/cron.* directories. That would allow for removal of cronie while sidestepping timer elapse problems that we are discussing here. It would also have a benefit of handling all cron tasks in addition to logrotate/updatedb/man-db/shadow. The scripts mainly set up the environment which is now done by systemd. You issue is with scheduling, and it will _not_ go away because scripts are still executed by systemd (as opposed to cronie). Cheers, -- Leonid Isaev GPG fingerprints: DA92 034D B4A8 EC51 7EA6 20DF 9291 EE8A 043C B8C4 C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D signature.asc Description: PGP signature
Re: [arch-general] Comment on: Use systemd timers instead of /etc/cron.{hourly, daily, weekly, monthly}?
On 05/05/14 09:05 AM, Maciej Puzio wrote: I have been testing the issue for a week. Daily timers are fired between 0:00 and 0:01 without exception - all timers at the same time, all machines at the same time, every day at the same time. The largest variation I have seen was 30 seconds. So yes, there is definitely an issue with AccuracySec=12h not being honored. However, whether timer accuracy is 30 seconds or 12 hours, this makes little difference to me, as both are unacceptable without the possibility to customize timer elapse time. I have reverted all my Arch machines to previous cron-based config and intend to keep it this way. Perhaps it is not cool, but at least it works. Which brings me to what I consider the most important problem here. Having read the original thread on arch-dev-public I was left with an impression that perceived coolness of the new setup took precedence over consideration of its impact. As a result, modification has been released without sufficient testing, as we can clearly see now. It did not help that discussion was carried on a mailing list that does not allow user comments. Perhaps a larger audience would have allowed a consideration of alternative solutions. An example of such a solution would be hourly/daily/monthly/weekly timers that execute scripts from relevant /etc/cron.* directories. That would allow for removal of cronie while sidestepping timer elapse problems that we are discussing here. It would also have a benefit of handling all cron tasks in addition to logrotate/updatedb/man-db/shadow. Thanks Maciej Puzio cronie was not enabled by default before and these systemd timers are, so there has been an improvement in the default configuration. The issue of systemd not spreading out the timers enough can be fixed, because if true it's a bug. signature.asc Description: OpenPGP digital signature
Re: [arch-general] Installing Archlinux alongside Ubuntu on aWindows8 UEFI laptop
Well, the new wrinkle is that I can no longer find Windows. I turned back to Both as the boot mode. All I see is the two Ubuntu options, and Manjaro, the default. Now I am in an unbeleivable situation where I am applying for a teaching certificate in a state where the system actually will not work with Firefox. The site says that IE is required. I can get most things to work wtih Chrome. However, I have run into a wrinkle where nothing is working, so i need Windoze, much to my consternation. Otherwise I would not worry about this issue. I would proceed from here with these GNU/Linux installs. Thank you for all the advice. Had I understood, I would have followed more of it, and possibly with full awareness of consequences. Alan Davis On Mon, May 5, 2014 at 10:18 AM, Daniel Micay danielmi...@gmail.com wrote: Can I safely treat this Manjaro as an Arch installation? I did this with Antergos a couple of years ao, and it worked out fine. Will I run into a roadblock down the road? Antergos is Arch Linux, Manjaro isn't.
