Re: Read sysctl from file
> As I see it everybody has agreed upon that and some are now just making > suggestions on how to solve the OP's problem, that do not involve adding -p to > OpenBSD's sysctl. So I thik that was uncalled for. Not everybody! Man, you talk like a black suit manager here. > I just do not get that. Yes, you obviously don't. It has been explained that the CONCEPT of -p is WRONG in OpenBSD area and maybe other areas, too. IF you can grasp that, then think why the hell would someone try to implement this and find a solution for the OP? I think one of the reasons that OpenBSD avoided to become useless swiss army knife of OSes is exactly that resitance to implement crap "just because ...".
Re: Openbsd 6.1 and Current Console Freezes and lockup Proxmox PVE5.0
On 17-07-24 20:56:46, Tom Smyth wrote: > Hi Viq, > > Regarding your email > >And removing VGA and switching to serial console only didn't help in my > >case, as I did that around the time I sent my previous mail, and I'm > >writing this one just after doing a hard reboot of a hanged VM. > > Can you confirm that you set the serial console, and then > set the display in Proxmox libvirt, not proxmox. No proxmox anywhere in my case. > to serial 0 ? Yes, I removed video devices from machine whatsoever, and did 'set tty com0' in /etc/boot.conf inside the VM > it seemed to work for me ... > I also found that if I changed to the serial console and > I set a custom disk setup, such as > > / offset 2048 with a size of 2G > swap with a size of 4G > and any partition after that (eg / var ) the installer > would hang when copying to disk, > but if I just set defaults autopartion / or just 2 > partitions the installer would not hang... > > once the install was complete I set the display to serial 0 > exclusively then.. > ie use vga to set the boot parameters to use serial 0 as the console > then continue with the installer > shutdown,and modify proxmox guest Display to serial 0 > after that I saw improved stability > > > I hope this helps > Tom Smyth The machines have IIRC automatic partition layout. And even with the changes above, I do get occasional hangs.
Re: Openbsd 6.1 and Current Console Freezes and lockup Proxmox PVE5.0
Hello Jorge, > Tom, > > I guess this problem is related to pve 5.0 kernel, try to install pve 4.4 > kernel. > > JP I can confirm that Proxmox 4.4 works fine with Ivy Bridge Processors with host CPU exposed to the guest... -- Kindest regards, Tom Smyth Mobile: +353 87 6193172 The information contained in this E-mail is intended only for the confidential use of the named recipient. If the reader of this message is not the intended recipient or the person responsible for delivering it to the recipient, you are hereby notified that you have received this communication in error and that any review, dissemination or copying of this communication is strictly prohibited. If you have received this in error, please notify the sender immediately by telephone at the number above and erase the message You are requested to carry out your own virus check before opening any attachment.
Re: Openbsd 6.1 and Current Console Freezes and lockup Proxmox PVE5.0
Hi Viq, Regarding your email >And removing VGA and switching to serial console only didn't help in my >case, as I did that around the time I sent my previous mail, and I'm >writing this one just after doing a hard reboot of a hanged VM. Can you confirm that you set the serial console, and then set the display in Proxmox to serial 0 ? it seemed to work for me ... I also found that if I changed to the serial console and I set a custom disk setup, such as / offset 2048 with a size of 2G swap with a size of 4G and any partition after that (eg / var ) the installer would hang when copying to disk, but if I just set defaults autopartion / or just 2 partitions the installer would not hang... once the install was complete I set the display to serial 0 exclusively then.. ie use vga to set the boot parameters to use serial 0 as the console then continue with the installer shutdown,and modify proxmox guest Display to serial 0 after that I saw improved stability I hope this helps Tom Smyth
Re: octeon port, ubiquity edgerouter
I have and spare ERPRO-8 (almost the same dual-core MIPS, 1GHz vs 800MHz, two SFP ports) that could be included on this tests. Regards, 2017-07-24 19:21 GMT+02:00 Peter J. Philipp : > On Mon, Jul 24, 2017 at 07:11:32PM +0200, Doggie wrote: > > W dniu 2017-07-24 o 14:18, Sean Murphy pisze: > > > Whoops, you're right. I did mention that it was an ERL in my original > > > email, but I didn't follow the original link. Sorry for the noise. > > > > All I can say is that I share the same good experience with ERL :) > > > > Now it would be very interesting to see dmesg coming from 8-port ER. > > > > -- > > Cheers, > > Pawel Waga > > Hi, > > According to DHL the ER-8 will be delivered here tomorrow. I'm going to > try > to get a dmesg on list if it's requested. Thanks to all that made this > hardware possible. The guy that sent this to me has not included a console > cable so I have only 1 Lanner FW rollover cable here, hoping it will work > for > this task. The Lanner rollover cable is cisco compatible it said on their > support website, so it should work. Otherwise we'll have to wait about a > day > until I get the rollover cable that I purchased on Amazon yesterday. > > Cheers, > -peter > >
Re: octeon port, ubiquity edgerouter
On Mon, Jul 24, 2017 at 07:11:32PM +0200, Doggie wrote: > W dniu 2017-07-24 o 14:18, Sean Murphy pisze: > > Whoops, you're right. I did mention that it was an ERL in my original > > email, but I didn't follow the original link. Sorry for the noise. > > All I can say is that I share the same good experience with ERL :) > > Now it would be very interesting to see dmesg coming from 8-port ER. > > -- > Cheers, > Pawel Waga Hi, According to DHL the ER-8 will be delivered here tomorrow. I'm going to try to get a dmesg on list if it's requested. Thanks to all that made this hardware possible. The guy that sent this to me has not included a console cable so I have only 1 Lanner FW rollover cable here, hoping it will work for this task. The Lanner rollover cable is cisco compatible it said on their support website, so it should work. Otherwise we'll have to wait about a day until I get the rollover cable that I purchased on Amazon yesterday. Cheers, -peter
Re: octeon port, ubiquity edgerouter
W dniu 2017-07-24 o 14:18, Sean Murphy pisze: Whoops, you're right. I did mention that it was an ERL in my original email, but I didn't follow the original link. Sorry for the noise. All I can say is that I share the same good experience with ERL :) Now it would be very interesting to see dmesg coming from 8-port ER. -- Cheers, Pawel Waga
Re: Lumina enable Shut Down
On Mon, 2017-07-24 at 07:34 -0600, Theo de Raadt wrote: > Whatever anyone wants to do to de-secure their own machine, but this > type of thing should NEVER be default configuration applied by a > package. > > I think the entire approach is dumb. > > It's like adding a "shutdown" built-in to ksh. Obviously when I'm in > ksh, I want to be able to Shutdown my machine. Why has this feature > been withheld from me for so long?? > > Darned good point. If the project leadership thinks it's a bad idea, I'm totally fine with not baking it into upstream. I have been using Lumina as my daily driver since 1.1 and haven't really found it difficult to type "shutdown -hp now" into the xterm I always have open. ☺
Re: Lumina enable Shut Down
As one who uses Lumina on a daily-driver OpenBSD laptop, I just fire up a terminal and "doas halt -p" (or reboot, etc) when I'm ready to shut the system down. You could likely add a nopassd rule to doas.conf so your user account can run shutdown, and make a launcher or script for Lumina. On Mon, Jul 24, 2017 at 8:34 AM, Theo de Raadt wrote: > > I'm our maintainer of the Lumina port. Let me chat with my friends > > upstream and see if we can't come up with a better solution for this. > > As a quick thought, allowing users in a particular group (perhaps > > :wheel?) to run shutdown(8) without a password prompt using doas seems > > like a starting point. Thoughts on that if I push that direction? > > Whatever anyone wants to do to de-secure their own machine, but this > type of thing should NEVER be default configuration applied by a > package. > > I think the entire approach is dumb. > > It's like adding a "shutdown" built-in to ksh. Obviously when I'm in > ksh, I want to be able to Shutdown my machine. Why has this feature > been withheld from me for so long?? > > >
Re: Lumina enable Shut Down
> I'm our maintainer of the Lumina port. Let me chat with my friends > upstream and see if we can't come up with a better solution for this. > As a quick thought, allowing users in a particular group (perhaps > :wheel?) to run shutdown(8) without a password prompt using doas seems > like a starting point. Thoughts on that if I push that direction? Whatever anyone wants to do to de-secure their own machine, but this type of thing should NEVER be default configuration applied by a package. I think the entire approach is dumb. It's like adding a "shutdown" built-in to ksh. Obviously when I'm in ksh, I want to be able to Shutdown my machine. Why has this feature been withheld from me for so long??
Re: Lumina enable Shut Down
On Mon, 2017-07-24 at 09:51 +0200, Martijn Rijkeboer wrote: > I totally agree with you, but if you want to use the shutdown > button from within Lumina you currently need to be member of the > 'operator' group [0]. > > [0] > https://github.com/trueos/lumina/blob/master/src-qt5/core/libLumina/LuminaOS-OpenBSD.cpp#L157 > > > Kind regards, > > > Martijn Rijkeboer > I'm our maintainer of the Lumina port. Let me chat with my friends upstream and see if we can't come up with a better solution for this. As a quick thought, allowing users in a particular group (perhaps :wheel?) to run shutdown(8) without a password prompt using doas seems like a starting point. Thoughts on that if I push that direction?
Re: octeon port, ubiquity edgerouter
On Sat, Jul 22, 2017 at 12:26 PM, Doggie wrote: > Judging by your dmesg, Sean, you are describing EdgeRouter Lite > (https://www.ubnt.com/edgemax/edgerouter-lite/), while Peter was asking > about EdgeRouter (https://www.ubnt.com/edgemax/edgerouter/). > > BTW, it's really great to see now we have not 2, but 4 models of Ubiquiti > routers supported! (https://www.openbsd.org/octeon.html) > > -- > Cheers, > Pawel Waga Whoops, you're right. I did mention that it was an ERL in my original email, but I didn't follow the original link. Sorry for the noise.
Re: Read sysctl from file
On Fri, Jul 21, 2017 at 05:30:32PM -0600, Theo de Raadt wrote: > > > On Jul 21, 2017, at 3:42 PM, li...@wrant.com wrote: > > >=20 > > > Fri, 21 Jul 2017 12:33:31 -0700 Peter Faiman > > >> # ./sysctl -p example.conf > > >> Peter > > >=20 > > > Hi Peter, ansibles, > > >=20 > > > No guarantee systems controls stay affixed, wrapper tools comply got = > > it? > > > > The point of sysctl -p is reloading from a file. So that you put controls in > > the file and load that file, exactly as happens in system startup. The whole > > point is to ensure consistency with system startup. True, securelevel throws > > a bit of a wrench in that, but this works for all other settings. > > We don't have -p. > > It is an addition made by a foreign system which barely uses sysctl, > and has been acting for years like they will be removing support. > > THERE IS NO SUPPORT FOR -p. > > It is unlikely to happen. As I see it everybody has agreed upon that and some are now just making suggestions on how to solve the OP's problem, that do not involve adding -p to OpenBSD's sysctl. So I thik that was uncalled for. > > Let's just stop this. You just aren't capable of listening to what > is being said. Also, you are ridiculously rude. I just do not get that. I think Peter has listened to what was said and that others are rude to him for no (very little) reason. Best regards -- / Raimo Niskanen, Erlang/OTP, Ericsson AB
Re: Read sysctl from file
On Fri, Jul 21, 2017 at 05:40:04PM -0600, Theo de Raadt wrote: > Peter, please leave. People around here don't need to read your > insults. > Peter, you do not have to leave. Theo says that all the time. I did not read your posts as particulary insulting to anyone and understand why you feel you ought to defend yourself for getting maybe deliberately misunderstood. Best regards -- / Raimo Niskanen, Erlang/OTP, Ericsson AB
Re: Lumina enable Shut Down
On 23-07-17 23:12, Stefan Sperling wrote: On Sun, Jul 23, 2017 at 09:10:07PM +0200, Martijn Rijkeboer wrote: On 22-07-17 02:02, Sha'ul wrote: In Lumina desktop how do I enable shutdown from GUI menu for point and click poweroff and reboot? Try adding yourself to the 'operator' group. The operator group has read access to raw disk device nodes, bypassing file system permissions: ls -l /dev/r[ws]d[0-9]* Allowing shutdown/reboot via doas(1) is a safer option. I totally agree with you, but if you want to use the shutdown button from within Lumina you currently need to be member of the 'operator' group [0]. [0] https://github.com/trueos/lumina/blob/master/src-qt5/core/libLumina/LuminaOS-OpenBSD.cpp#L157 Kind regards, Martijn Rijkeboer
