Re: Can I use OpenBSD as a desktop system?
On Mon, Jun 12, 2017 at 1:16 AM, Davor Balderwrote: > xfce is available and you should be able to use mac-like shortcuts there. I > think this relates to your chaoice of window manager/desktop environment. We have choices! Using xfce already, but Apple-like shortcuts did not work so far. > I've been using seamonkey and qutebrowser with good results. Will try them. I have a privacy and security protocol that I could implement on firefox only, across different OSs, with extensions, configurations and changes to the code. The result is better than torbrowser. I installed chromium on openbsd, but was greeted by chrome instead. I tried hard to to secure chrome, but each step I took resulted in greater leaks. I expected the openbsd version of both ff and chrome to be safer by default. There is s lot of work to be done. Will share more next weekend. R
Re: Boot issue 6.1
Hello Martin, It may be worth upgrading from USB just in case... Cheers D On 06/12/17 14:43, Martin Oppegaard wrote: Hello, After updating to 6.1 my computer will no longer boot; it stops on "Loading.". Redoing installboot from the installation CD did not help. Do you have any suggestions? Here is an old dmesg of mine: https://marc.info/?l=openbsd-misc=146436543130287=2 Regards, Martin Oppegaard
Re: re0 and re1 watchdog timeouts, and system freeze
On Fri, Jun 09, 2017 at 07:19:34PM +0200, Bj??rn Ketelaars wrote: > On Fri 09/06/2017 12:07, Martin Pieuchot wrote: > > On 08/06/17(Thu) 20:38, Bj??rn Ketelaars wrote: > > > On Thu 08/06/2017 16:55, Martin Pieuchot wrote: > > > > On 07/06/17(Wed) 09:43, Bj??rn Ketelaars wrote: > > > > > On Sat 03/06/2017 08:44, Bj??rn Ketelaars wrote: > > > > > > > > > > > > Reverting back to the previous kernel fixed the issue above. > > > > > > Question: can > > > > > > someone give a hint on how to track this issue? > > > > > > > > > > After a bit of experimenting I'm able to reproduce the problem. > > > > > Summary is > > > > > that queueing in pf and use of a current (after May 30), multi > > > > > processor > > > > > kernel (bsd.mp from snapshots) causes these specific watchdog timeouts > > > > > followed by a system freeze. > > > > > > > > > > Issue is 'gone' when: > > > > > 1.) using an older kernel (before May 30); > > > > > 2.) removal of queueing statements from pf.conf. Included below the > > > > > specific > > > > > snippet; > > > > > 3.) switch from MP kernel to SP kernel. > > > > > > > > > > New observation is that while queueing, using a MP kernel, the > > > > > download > > > > > bandwidth is only a fraction of what is expected. Exchanging the MP > > > > > kernel > > > > > with a SP kernel restores the download bandwidth to expected level. > > > > > > > > > > I'm guessing that this issue is related to recent work on PF? > > > > > > > > It's certainly a problem in, or exposed by, re(4) with the recent MP > > > > work > > > > in the network stack. > > > > > > > > It would help if you could build a kernel with MP_LOCKDEBUG defined and > > > > see if the resulting kernel enters ddb(4) instead of freezing. > > > > > > > > Thanks, > > > > Martin > > > > > > Thanks for the hint! It helped in entering ddb. I collected a bit of > > > output, > > > which you can find below. If I read the trace correctly the crash is > > > related > > > to line 1750 of sys/dev/ic/re.c: > > > > > > d->rl_cmdstat |= htole32(RL_TDESC_CMD_EOF); > > > > Could you test the diff below, always with a MP_LOCKDEBUG kernel and > > tell us if you can reproduce the freeze or if the kernel enters ddb(4)? > > > > Another question, how often do you see "watchdog timeout" messages? > > > > Index: re.c > > === > > RCS file: /cvs/src/sys/dev/ic/re.c,v > > retrieving revision 1.201 > > diff -u -p -r1.201 re.c > > --- re.c24 Jan 2017 03:57:34 - 1.201 > > +++ re.c9 Jun 2017 10:04:43 - > > @@ -2074,9 +2074,6 @@ re_watchdog(struct ifnet *ifp) > > s = splnet(); > > printf("%s: watchdog timeout\n", sc->sc_dev.dv_xname); > > > > - re_txeof(sc); > > - re_rxeof(sc); > > - > > re_init(ifp); > > > > splx(s); > > The diff (with a MP_LOCKDEBUG kernel) resulted in similar traces as before. > ddb Output is included below. > > With your diff the number of timeout messages decreased from 9 to 2 before > entering ddb. can you try the diff below please? Index: hfsc.c === RCS file: /cvs/src/sys/net/hfsc.c,v retrieving revision 1.39 diff -u -p -r1.39 hfsc.c --- hfsc.c 8 May 2017 11:30:53 - 1.39 +++ hfsc.c 12 Jun 2017 05:08:01 - @@ -817,7 +817,7 @@ hfsc_deferred(void *arg) KASSERT(HFSC_ENABLED(ifq)); if (!ifq_empty(ifq)) - (*ifp->if_qstart)(ifq); + ifq_start(ifq); hif = ifq->ifq_q;
Boot issue 6.1
Hello, After updating to 6.1 my computer will no longer boot; it stops on "Loading.". Redoing installboot from the installation CD did not help. Do you have any suggestions? Here is an old dmesg of mine: https://marc.info/?l=openbsd-misc=146436543130287=2 Regards, Martin Oppegaard
Re: Can I use OpenBSD as a desktop system?
On 06/12/17 10:54, Donald Allen wrote: On 11 June 2017 at 19:16, Davor Balderwrote: On 06/12/17 06:06, Rupert Gallagher wrote: I spent yesterday and today installing 6.1 from scratch on a Dell Optiplex gx620. The machine has a pentium 4 @3.0GHz with 4GB non ECC RAM, returning a passmark of 354*. The aim is to replace the accountant's windows 10 pro tomorrow morning, moving the disk into his more recent Dell. In summary, I have everything he needs, including a gui that looks like windows 7, except for the following, so far: a toolbar icon for the printer and a gui for cups, configuring and testing the printer (cups), the scanner (sane), and the remote desktop to a windows server (vnc). The only thing that refrains me from using it myself is the lack of Apple-like keyboard shortcuts on everything. They are a real time saver; forget about mouse and menu bars, you do everything everywhere with the same command-s, command-c, command-z, etc. By comparison, copying and pasting across windows and vim on other OSs is a royal pain. Opening tabs on terminal, firefox, file manager, vim, you name it: just command-t. They are not everyone's cup of tea, but I use a tiling window manager with OpenBSD (I like xmonad, but there are other choices: dwm, i3, awesome; there's also spectrwm, written originally, I believe, by someone formerly associated with OpenBSD; I've tried it multiple times over the years and always had problems with it). The point of these things is, at least in part, exactly what you are talking about -- avoiding having to move between keyboard and mouse by providing keyboard commands for just about everything (everything you describe above is just as easy with my setup as on a Mac; I've used both and prefer the OpenBSD/xmonad setup). Tilers also eliminate the need to spend time rearranging windows. I do not use a desktop system; just the window manager, the Rox filer and dmenu. I used xmobar for battery and date-time info displayed on the bar at the top of the screen. You are right. For example on my setup, I've been playing with cwm and fvwm of late. I also have xfce and gnome installed that I use less frequently. A word of warning: I found I have issues with libreoffice running in cwm (it crashes). However, if I load thunar then crashes are not as frequent. Loading nautilus in cwm and then libreoffice completely kills X and puts me in command line. Fvwm (interestingly enough) does not give me any of those issues so I have been running fvwm if I have to edit a document in libreoffice (my work requires me to do this). I am happy and comfortable with this minimalist setup. Command line is my friend! I will be happier when abiword is updated to the recent version (there is a black screen bug with the current port/version). Abiword is lighter than libreoffice writer. Cheers D
Re: Can I use OpenBSD as a desktop system?
On 11 June 2017 at 19:16, Davor Balderwrote: > > > On 06/12/17 06:06, Rupert Gallagher wrote: >> >> I spent yesterday and today installing 6.1 from scratch on a Dell Optiplex >> gx620. The machine has a pentium 4 @3.0GHz with 4GB non ECC RAM, returning a >> passmark of 354*. The aim is to replace the accountant's windows 10 pro >> tomorrow morning, moving the disk into his more recent Dell. In summary, I >> have everything he needs, including a gui that looks like windows 7, except >> for the following, so far: >> >> a toolbar icon for the printer and a gui for cups, configuring and testing >> the printer (cups), the scanner (sane), and the remote desktop to a windows >> server (vnc). >> >> The only thing that refrains me from using it myself is the lack of >> Apple-like keyboard shortcuts on everything. They are a real time saver; >> forget about mouse and menu bars, you do everything everywhere with the same >> command-s, command-c, command-z, etc. By comparison, copying and pasting >> across windows and vim on other OSs is a royal pain. Opening tabs on >> terminal, firefox, file manager, vim, you name it: just command-t. They are not everyone's cup of tea, but I use a tiling window manager with OpenBSD (I like xmonad, but there are other choices: dwm, i3, awesome; there's also spectrwm, written originally, I believe, by someone formerly associated with OpenBSD; I've tried it multiple times over the years and always had problems with it). The point of these things is, at least in part, exactly what you are talking about -- avoiding having to move between keyboard and mouse by providing keyboard commands for just about everything (everything you describe above is just as easy with my setup as on a Mac; I've used both and prefer the OpenBSD/xmonad setup). Tilers also eliminate the need to spend time rearranging windows. I do not use a desktop system; just the window manager, the Rox filer and dmenu. I used xmobar for battery and date-time info displayed on the bar at the top of the screen.
ocsp response not current
Hi All, I'm attempting to fetch the latest bsd.rd snapshot, but it's failing because of the ocsp response. $ ftp https://ftp.openbsd.org/pub/OpenBSD/snapshots/amd64/bsd.rd Trying 129.128.5.191... Requesting https://ftp.openbsd.org/pub/OpenBSD/snapshots/amd64/bsd.rd ftp: SSL write error: ocsp verify failed: ocsp response not current Currently on OpenBSD 6.1-current (GENERIC.MP) #116: Sat Jun 10 22:34:37 MDT 2017 Any clues as to what's happening with the ocsp response? Thanks, j.b.
Re: Can I use OpenBSD as a desktop system?
On 06/12/17 06:06, Rupert Gallagher wrote: I spent yesterday and today installing 6.1 from scratch on a Dell Optiplex gx620. The machine has a pentium 4 @3.0GHz with 4GB non ECC RAM, returning a passmark of 354*. The aim is to replace the accountant's windows 10 pro tomorrow morning, moving the disk into his more recent Dell. In summary, I have everything he needs, including a gui that looks like windows 7, except for the following, so far: a toolbar icon for the printer and a gui for cups, configuring and testing the printer (cups), the scanner (sane), and the remote desktop to a windows server (vnc). The only thing that refrains me from using it myself is the lack of Apple-like keyboard shortcuts on everything. They are a real time saver; forget about mouse and menu bars, you do everything everywhere with the same command-s, command-c, command-z, etc. By comparison, copying and pasting across windows and vim on other OSs is a royal pain. Opening tabs on terminal, firefox, file manager, vim, you name it: just command-t. xfce is available and you should be able to use mac-like shortcuts there. I think this relates to your chaoice of window manager/desktop environment. We have choices! Anyway, it works, it is rock solid, and it is fucking fast, excuse my French. The only app that heats up the CPU is fucking firefox, excuse my French again. So, pending the above, the resulting desktop OS would be good enough for everyday office use, PXE bootable and ansible/remotely configurable. I've been using seamonkey and qutebrowser with good results. *By comparison, the NUC6I5SYK has a passmark of 4300, 12x faster than this Dell.
Re: EBNH's Artwork
> Just to share artworks of my alter-ego EsteBaN Hache: The Madagascar end of the movie penguin's quote: "It sucks!".
Re: Can I use OpenBSD as a desktop system?
I spent yesterday and today installing 6.1 from scratch on a Dell Optiplex gx620. The machine has a pentium 4 @3.0GHz with 4GB non ECC RAM, returning a passmark of 354*. The aim is to replace the accountant's windows 10 pro tomorrow morning, moving the disk into his more recent Dell. In summary, I have everything he needs, including a gui that looks like windows 7, except for the following, so far: a toolbar icon for the printer and a gui for cups, configuring and testing the printer (cups), the scanner (sane), and the remote desktop to a windows server (vnc). The only thing that refrains me from using it myself is the lack of Apple-like keyboard shortcuts on everything. They are a real time saver; forget about mouse and menu bars, you do everything everywhere with the same command-s, command-c, command-z, etc. By comparison, copying and pasting across windows and vim on other OSs is a royal pain. Opening tabs on terminal, firefox, file manager, vim, you name it: just command-t. Anyway, it works, it is rock solid, and it is fucking fast, excuse my French. The only app that heats up the CPU is fucking firefox, excuse my French again. So, pending the above, the resulting desktop OS would be good enough for everyday office use, PXE bootable and ansible/remotely configurable. *By comparison, the NUC6I5SYK has a passmark of 4300, 12x faster than this Dell.
Re: dokuwiki - /dev/urandom issue
> The port should be fixed, so that it internally use arc4random. That is what for i came here. think i need to write some mail to package developer... 2017-06-11 21:37 GMT+03:00 Theo de Raadt: > > Asbel Kiprop wrote on Sun, Jun 11, 2017 at 09:24:23PM +0300: > > > > > cat: /var/www/dev/urandom: Device not configured > > > > By default, /var is mounted nodev. See mount(8), fstab(5). > > Providing a workaround that reduces security is a poor answer. > Perhaps the drive to make-it-work inevitably overrides the > desire to do right. > > Also, you could "cp /etc/passwd urandom" and it will work fine > also! Safety, good lord who cares. > > The port should be fixed, so that it internally use arc4random. > > The "nodev" option is used for some good reasons. > >
OpenBSD 6.1 is now supported on Microsoft Azure
Maybe I missed the email here, but in case it actually doesn't exist: OpenBSD 6.1 is now supported on Microsoft Azure courtesy of reyk@ and the team over at Esdenera® Networks, with assistance from Microsoft. At least that's what I got out of the BSDCan announcement. I'll let Reyk blow his own horn on the products & marketing. But I think it's great that MS sanctions running OpenBSD in Azure now. For me, this is a significant milestone. Thanks, Reyk (et al.) https://azuremarketplace.microsoft.com/en-us/marketplace/apps/esdenera.esdenera-firewall-3 The link to the Sponsor BOF doesn't have any info so I'm not going providing it here. https://azure.microsoft.com/en-au/blog/running-openbsd-on-azure/ (apparently this page is about to get updated Real Soon Now) -Adam
Re: blank screen
On 06/11/17 11:53, lvdd wrote: > On Sun, 11 Jun 2017 09:42:15 -0600 > "Theo de Raadt"wrote: > >>> is somebody messing with the graphics stack by any chance? >> >> It is probably rude to call steps-being-taken-toward-progress "messing" >> >> > > I am sorry - this wasn't meant to be as insult to anyone. I took "messing" here to be a term of familiar endearment. Undoubtedly it was written with as much affection as respect for the very step-being-taken-towards-progress mentioned. The use of English was, IMHO, sound... but perhaps familiarity has bred contempt. Chill-pill-time. Long live the messing!
Re: dokuwiki - /dev/urandom issue
> Asbel Kiprop wrote on Sun, Jun 11, 2017 at 09:24:23PM +0300: > > > cat: /var/www/dev/urandom: Device not configured > > By default, /var is mounted nodev. See mount(8), fstab(5). Providing a workaround that reduces security is a poor answer. Perhaps the drive to make-it-work inevitably overrides the desire to do right. Also, you could "cp /etc/passwd urandom" and it will work fine also! Safety, good lord who cares. The port should be fixed, so that it internally use arc4random. The "nodev" option is used for some good reasons.
Re: dokuwiki - /dev/urandom issue
Ooops, really, thanks So for now it really the only solution, create dev in chroot and remove nodev flag from mounting options of /var/ directory? Hmmm 2017-06-11 21:33 GMT+03:00 Ingo Schwarze: > Hi Asbel, > > Asbel Kiprop wrote on Sun, Jun 11, 2017 at 09:24:23PM +0300: > > > cat: /var/www/dev/urandom: Device not configured > > By default, /var is mounted nodev. See mount(8), fstab(5). > > Yours, > Ingo >
Re: dokuwiki - /dev/urandom issue
Hi Asbel, Asbel Kiprop wrote on Sun, Jun 11, 2017 at 09:24:23PM +0300: > cat: /var/www/dev/urandom: Device not configured By default, /var is mounted nodev. See mount(8), fstab(5). Yours, Ingo
Re: dokuwiki - /dev/urandom issue
On Sun, 11 Jun 2017 21:24:23 +0300, Asbel Kipropwrote: > Created /dev/urandom in chroot. btw > root :: /var/www : ls -la /var/www/dev/ > > > > total 16 > drwxr-xr-x 2 root wheel512 Jun 11 21:01 ./ > drwxr-xr-x 16 root daemon 512 Jun 11 21:01 ../ > crw-r--r-- 1 root wheel45, 3 Jun 11 21:01 arandom > crw-r--r-- 1 root wheel45, 0 Jun 11 21:01 random > crw-r--r-- 1 root wheel45, 1 Jun 11 21:01 srandom > crw-r--r-- 1 root wheel45, 2 Jun 11 21:01 urandom > > but > root :: /var/www : cat /var/www/dev/urandom > > > > cat: /var/www/dev/urandom: Device not configured Your partition is probably mounted with the nodev flag.
Re: dokuwiki - /dev/urandom issue
Created /dev/urandom in chroot. btw root :: /var/www : ls -la /var/www/dev/ total 16 drwxr-xr-x 2 root wheel512 Jun 11 21:01 ./ drwxr-xr-x 16 root daemon 512 Jun 11 21:01 ../ crw-r--r-- 1 root wheel45, 3 Jun 11 21:01 arandom crw-r--r-- 1 root wheel45, 0 Jun 11 21:01 random crw-r--r-- 1 root wheel45, 1 Jun 11 21:01 srandom crw-r--r-- 1 root wheel45, 2 Jun 11 21:01 urandom but root :: /var/www : cat /var/www/dev/urandom cat: /var/www/dev/urandom: Device not configured
Re: dokuwiki - /dev/urandom issue
I'll try it, but as far as i remember years ago in misc was the discussion about urandom use in OpenBSD applications and advice was to correct the applications so it wasnt depended on urandom. And as i use Doku package from openbsd it looks kinda contradictory - chroot by default and urandom dependency in package... 2017-06-11 20:54 GMT+03:00 Daniel Gillen: > On 11.06.2017 19:43, Asbel Kiprop wrote: > > Hello > > After todays update my Dokuwiki just throw 500 error "There is no > suitable > > CSPRNG installed on your system". Googled a bit and found out it because > i > > have no /dev/urandom in my basedir, > > And this kinda obvious cuz i have httpd chrooted by default > > > > Doku version dokuwiki-2017.02.19b installed from the OpenBSD pacjages, So > > only way is to disable chroot? > > > > Have u tried creating urandom in the httpd chroot? > > In case your chroot is /var/www: mkdir /var/www/dev && cd /var/www/dev > && /dev/MAKEDEV random > > I just have no idea whether this might have any security implications. > Probably not, but maybe someone else can enlighten us on this. > > -- > Unix _IS_ user friendly - it's just > selective about who its friends are! >
Re: dokuwiki - /dev/urandom issue
On 11.06.2017 19:43, Asbel Kiprop wrote: > Hello > After todays update my Dokuwiki just throw 500 error "There is no suitable > CSPRNG installed on your system". Googled a bit and found out it because i > have no /dev/urandom in my basedir, > And this kinda obvious cuz i have httpd chrooted by default > > Doku version dokuwiki-2017.02.19b installed from the OpenBSD pacjages, So > only way is to disable chroot? > Have u tried creating urandom in the httpd chroot? In case your chroot is /var/www: mkdir /var/www/dev && cd /var/www/dev && /dev/MAKEDEV random I just have no idea whether this might have any security implications. Probably not, but maybe someone else can enlighten us on this. -- Unix _IS_ user friendly - it's just selective about who its friends are!
Re: dokuwiki - /dev/urandom issue
Oh, forgot, OpenBSD -current, php56 + php56-fpm. 2017-06-11 20:43 GMT+03:00 Asbel Kiprop: > Hello > After todays update my Dokuwiki just throw 500 error "There is no suitable > CSPRNG installed on your system". Googled a bit and found out it because i > have no /dev/urandom in my basedir, > And this kinda obvious cuz i have httpd chrooted by default > > Doku version dokuwiki-2017.02.19b installed from the OpenBSD pacjages, So > only way is to disable chroot? >
dokuwiki - /dev/urandom issue
Hello After todays update my Dokuwiki just throw 500 error "There is no suitable CSPRNG installed on your system". Googled a bit and found out it because i have no /dev/urandom in my basedir, And this kinda obvious cuz i have httpd chrooted by default Doku version dokuwiki-2017.02.19b installed from the OpenBSD pacjages, So only way is to disable chroot?
Re: Can I use OpenBSD as a desktop system?
> FWIW, that's not the name he's been using Is that '55' from 'SOUL_OF_ROOT 55' a 'SS' in fact?
Re: blank screen
On Sun, Jun 11, 2017 at 06:48:07PM +0200, Sebastien Marie wrote: > > Please at least post a dmesg sorry, I just saw you posted it in your first message. -- Sebastien Marie
Re: blank screen
On Sun, Jun 11, 2017 at 06:08:11PM +0200, lvdd wrote: > On Sun, 11 Jun 2017 09:56:07 -0600 > "Theo de Raadt"wrote: > > > > > For about a week, snapshots have contained a prototype of the new > > inteldrm codebase. Thereby allowing people to report issues. > > Thank you. That was the answer to my question. And it was exactly that > - just a question. > > > > > But saying "messing" really isn't helping. A detailed bug report > > helps. 1 line of whining doesn't. > > > > Noone said snapshots would always work for everyone all the time. > > > > I won't answer to that. See above. > Hi Lars, I think you miss the point of using snapshots: helping the project and permit progress for everybody. Please at least post a dmesg: developers will at least know on which hardware there is a problem. A detailed bug report would be welcome too. Thanks. -- Sebastien Marie
Re: blank screen
On 11 Jun 2017, Theo de Raadt wrote: > > On Sun, 11 Jun 2017 09:42:15 -0600 > > "Theo de Raadt"wrote: > > > > > > is somebody messing with the graphics stack by any chance? > > > > > > It is probably rude to call steps-being-taken-toward-progress "messing" > > > > > > > > > > I am sorry - this wasn't meant to be as insult to anyone. As far as I > > know 'messing' is used in english as well for a more colloquial speech > > of saying 'somebody is changing things' - But what do I know - it is > > not my primary language. > > > > So please let me rephrase it. > > > > Is somebody currently doing changes to the graphics stack? I would like > > to report a problem because those possible changes might have a > > negative impact on my system. > > For about a week, snapshots have contained a prototype of the new > inteldrm codebase. Thereby allowing people to report issues. > > But saying "messing" really isn't helping. A detailed bug report > helps. 1 line of whining doesn't. > > Noone said snapshots would always work for everyone all the time. Thanks, usefl - probably explains the firefox lockups I reported earlier. -- Anthony Campbellhttp://www.acampbell.uk
Re: blank screen
On Sun, 11 Jun 2017 09:56:07 -0600 "Theo de Raadt"wrote: > > For about a week, snapshots have contained a prototype of the new > inteldrm codebase. Thereby allowing people to report issues. Thank you. That was the answer to my question. And it was exactly that - just a question. > > But saying "messing" really isn't helping. A detailed bug report > helps. 1 line of whining doesn't. > > Noone said snapshots would always work for everyone all the time. > I won't answer to that. See above. Thanks Lars
Re: blank screen
> On Sun, 11 Jun 2017 09:42:15 -0600 > "Theo de Raadt"wrote: > > > > is somebody messing with the graphics stack by any chance? > > > > It is probably rude to call steps-being-taken-toward-progress "messing" > > > > > > I am sorry - this wasn't meant to be as insult to anyone. As far as I > know 'messing' is used in english as well for a more colloquial speech > of saying 'somebody is changing things' - But what do I know - it is > not my primary language. > > So please let me rephrase it. > > Is somebody currently doing changes to the graphics stack? I would like > to report a problem because those possible changes might have a > negative impact on my system. For about a week, snapshots have contained a prototype of the new inteldrm codebase. Thereby allowing people to report issues. But saying "messing" really isn't helping. A detailed bug report helps. 1 line of whining doesn't. Noone said snapshots would always work for everyone all the time.
Re: blank screen
On Sun, 11 Jun 2017 09:42:15 -0600 "Theo de Raadt"wrote: > > is somebody messing with the graphics stack by any chance? > > It is probably rude to call steps-being-taken-toward-progress "messing" > > I am sorry - this wasn't meant to be as insult to anyone. As far as I know 'messing' is used in english as well for a more colloquial speech of saying 'somebody is changing things' - But what do I know - it is not my primary language. So please let me rephrase it. Is somebody currently doing changes to the graphics stack? I would like to report a problem because those possible changes might have a negative impact on my system. Better? :-) Thanks Lars
Re: Can I use OpenBSD as a desktop system?
>With a name like SOUL_OF_ROOT_CANAL I wonder what he is trying to FWIW, that's not the name he's been using. So far he hasn't proven to be anything but an ass though. Cheers, Alexander
Re: blank screen
> is somebody messing with the graphics stack by any chance? It is probably rude to call steps-being-taken-toward-progress "messing"
blank screen
Hi, is somebody messing with the graphics stack by any chance? I installed today's snapshot (#116) and my system refuses to show me a picture as soon as "inteldrm0" is initialized. Up to that point I can see all messages on the console but after that the screen stays blank because the monitor goes to sleep. I have no console and no X and restarting xenodm or typing startx blindly after login has no effect. Right now I can only connect remotely. I had an older snapshot lying around (#111) and tried that one with the same effect. I was working with OpenBSD 6.1-current (GENERIC.MP) #91 until today and had no issues. What is happening? Thanks Lars here is my current dmesg: OpenBSD 6.1-current (GENERIC.MP) #116: Sat Jun 10 22:34:37 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8440090624 (8049MB) avail mem = 8178507776 (7799MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xec2f0 (67 entries) bios0: vendor American Megatrends Inc. version "0806" date 12/14/2015 bios0: ASUS All Series acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT LPIT SSDT SSDT MCFG HPET SSDT SSDT BGRT acpi0: wakeup devices UAR1(S4) PXSX(S4) RP01(S4) PXSX(S4) PXSX(S4) RP03(S4) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) GLAN(S4) EHC1(S4) EHC2(S4) XHC_(S4) HDEF(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i3-4360 CPU @ 3.70GHz, 3691.93 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: TSC frequency 3691929440 Hz cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i3-4360 CPU @ 3.70GHz, 3691.46 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM) i3-4360 CPU @ 3.70GHz, 3691.46 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 1, core 0, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i3-4360 CPU @ 3.70GHz, 3691.46 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (RP01) acpiprt2 at acpi0: bus 3 (RP03) acpiprt3 at acpi0: bus 1 (PEG0) acpiprt4 at acpi0: bus -1 (PEG1) acpiprt5 at acpi0: bus -1 (PEG2) acpiec0 at acpi0: not present acpicpu0 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpipwrres0 at acpi0: FN00, resource for FAN0 acpipwrres1 at acpi0: FN01, resource for FAN1 acpipwrres2 at acpi0: FN02, resource for FAN2 acpipwrres3 at acpi0: FN03, resource for FAN3 acpipwrres4 at acpi0: FN04, resource for FAN4 acpitz0 at acpi0: critical temperature is 105 degC acpitz1 at acpi0: critical temperature is 105 degC "INT3F0D" at acpi0 not configured "PNP0501" at acpi0 not configured acpibtn0 at acpi0: PWRB "PNP0C0B" at acpi0 not configured "PNP0C0B" at acpi0 not configured "PNP0C0B" at acpi0 not
inet6 packet filter question: link local address vs antispoof
Hi folks, pf.conf on my gateway (6.1) says bash-4.4# pfctl -sr | egrep -i icmp\|block block return log all : : pass quick inet proto icmp all keep state (if-bound) pass quick inet6 proto ipv6-icmp all keep state (if-bound) Problem is, a ping6 to the gateway's link local address is not answered. The pflog file reveals 15:11:35.491878 rule 0/(match) [uid 0, pid 14639] block out on re1: [uid 4294967295, pid 10] ::1 > fe80::f66d:4ff:fe73:ab4e: icmp6: echo reply (id:7445 seq:1) (len 64, hlim 64) 15:11:36.520792 rule 0/(match) [uid 0, pid 14639] block out on re1: [uid 4294967295, pid 10] ::1 > fe80::f66d:4ff:fe73:ab4e: icmp6: echo reply (id:7445 seq:2) (len 64, hlim 64) 15:11:37.544670 rule 0/(match) [uid 0, pid 14639] block out on re1: [uid 4294967295, pid 10] ::1 > fe80::f66d:4ff:fe73:ab4e: icmp6: echo reply (id:7445 seq:3) (len 64, hlim 64) Please note the "::1". This address is not bound to re1. If I disable the firewall(!), or if I use pass quick inet6 proto ipv6-icmp all no state then the icmp6 echo reply can pass: bash-4.4# tcpdump -i re1 -env icmp6 tcpdump: listening on re1, link-type EN10MB 15:13:36.328563 f4:6d:04:73:ab:4e 80:ee:73:95:c1:0d 86dd 118: fe80::f66d:4ff:fe73:ab4e > fe80::82ee:73ff:fe95:c10d: icmp6: echo request (id:74c1 seq:30) [flowlabel 0x47412] (len 64, hlim 255) 15:13:36.328689 80:ee:73:95:c1:0d f4:6d:04:73:ab:4e 86dd 118: ::1 > fe80::f66d:4ff:fe73:ab4e: icmp6: echo reply (id:74c1 seq:30) (len 64, hlim 64) 15:13:37.352729 f4:6d:04:73:ab:4e 80:ee:73:95:c1:0d 86dd 118: fe80::f66d:4ff:fe73:ab4e > fe80::82ee:73ff:fe95:c10d: icmp6: echo request (id:74c1 seq:31) [flowlabel 0x47412] (len 64, hlim 255) 15:13:37.352845 80:ee:73:95:c1:0d f4:6d:04:73:ab:4e 86dd 118: ::1 > fe80::f66d:4ff:fe73:ab4e: icmp6: echo reply (id:74c1 seq:31) (len 64, hlim 64) 15:13:38.376557 f4:6d:04:73:ab:4e 80:ee:73:95:c1:0d 86dd 118: fe80::f66d:4ff:fe73:ab4e > fe80::82ee:73ff:fe95:c10d: icmp6: echo request (id:74c1 seq:32) [flowlabel 0x47412] (len 64, hlim 255) 15:13:38.376672 80:ee:73:95:c1:0d f4:6d:04:73:ab:4e 86dd 118: ::1 > fe80::f66d:4ff:fe73:ab4e: icmp6: echo reply (id:74c1 seq:32) (len 64, hlim 64) 15:13:39.400577 f4:6d:04:73:ab:4e 80:ee:73:95:c1:0d 86dd 118: fe80::f66d:4ff:fe73:ab4e > fe80::82ee:73ff:fe95:c10d: icmp6: echo request (id:74c1 seq:33) [flowlabel 0x47412] (len 64, hlim 255) 15:13:39.400693 80:ee:73:95:c1:0d f4:6d:04:73:ab:4e 86dd 118: ::1 > fe80::f66d:4ff:fe73:ab4e: icmp6: echo reply (id:74c1 seq:33) (len 64, hlim 64) But this doesn't help. The sender address of the echo reply is still bad. It is blocked by some antispoof rule on the receiver, afaict. Is there some secret sysctl I missed to adjust? Every helpful comment is highly appreciated. Harri
Re: inet6 packet filter question: link local address vs antispoof
PS #1: Outgoing traffic to a link-local address initiated by the gateway is not corrupted. PS #2: It seems that OpenBSD 6.0 doesn't show this problem. Regards Harri
Re: Can I use OpenBSD as a desktop system?
Yes just download the desktop manager u want with pkg_add On June 9, 2017 9:39:30 PM GMT+02:00, SOUL_OF_ROOT 55wrote: >Can I use OpenBSD as a desktop system? -- Take Care Sincerely flipchan layerprox dev
Re: Current FreeBSD looking to switch to OpenBSD
On Sat, 10 Jun 2017 21:07:59 -0700 Kurt H Maierwrote: > I don't know. Some people just like talking about their computers to > strangers, I guess. > 4-way native uefi boot of Windows, FreeBSD, OpenBSD and Linux, with shared FAT32 partition: pacija@efreet-freebsd:~ % sudo gpart show ada0 => 34 468862061 ada0 GPT (224G) 34 2014- free - (1.0M) 2048 921600 1 ms-recovery (450M) 923648 204800 2 efi (100M) 1128448 32768 3 ms-reserved (16M) 1161216 125829120 4 ms-basic-data (60G) 126990336 33554432 5 freebsd-ufs (16G) 1605447688388608 6 freebsd-swap (4.0G) 168933376 41943040 7 openbsd-data (20G) 210876416 33554432 8 linux-data (16G) 2444308488388608 9 linux-swap (4.0G) 252819456 21604263910 ms-basic-data (103G) Works for me :) -- Before enlightenment - chop wood, draw water. After enlightenment - chop wood, draw water. Marko Cupać https://www.mimar.rs/
Re: Can I use OpenBSD as a desktop system?
On Sun, 11 Jun 2017 02:32:10 +0300 li...@wrant.com wrote: ... > Hi Nicolas, > > Soul of root canal is a half retarded troll, totally lacking any > character. I can not believe you're still falling for their simply > elemental tactics.. > > There is one absolutely zero diff between my init reply and Nick > Holland's. Continued further this thread is funny, amusing, and a > complete time waste. > > For the time being I can say you're all right and correct, but about > amiss. It is not any question "can they", it is those questions why > "won't they".. > > OpenBSD has always been and will continue to be, most developer use > system. Many if not most of us use the system on all machines > completely dedicated. > > You, Nicolas, can not defend any troll position here. They can not > use it. > > Kind regards, > Anton Lazarov > With a name like SOUL_OF_ROOT_CANAL I wonder what he is trying to achieve. He's not likely to hurt anyone, but he'll get a lot of mischievous or sarcastic responses. As for using OpenBSD as a desktop system: yes it is possible with a bit of work. Over the years I have created a decent configuration of a basic desktop using the FVWM in the base. The good thing is that once you have done the hard work, it seems to survive major updates if you back up the right config files, sure beats Windows and the registry. As newer versions of OpenBSD are released, I may tweak the setup if the new release comes with an interesting feature, or removes a feature, or allows my configuration to be simpler. I hope to put Windows to rest by 2020, just as Windows 7 reaches the end of extended support.
Re: Current FreeBSD looking to switch to OpenBSD
On dual-booting: I have set up Windows/OpenBSD dual-boot quite a few times. Windows 7 and Windows 10 instructions are all about the same, and the information in the FAQ on multi-booting has enough info to get you started. https://www.openbsd.org/faq/faq4.html#Multibooting First, always have good backups, but especially make sure anything important is backed up and tested before you embark on dual-booting with Windows. It works best with a fresh install of everything, though. Use the Windows installer to partition the drive. I like to have three partitions: 1 for Windows, 1 for OpenBSD and one for sharing files between the two. Install Windows on the first partition. Carefully install OpenBSD on the second partition. If memory serves correctly, I had to shell out of the installer, use fdisk to change the partition type of the OpenBSD partition, then go back into the installer and tell it to use that partition. BE REALLY CAREFUL using fdisk and setting up your partitions. after install, follow the FAQ guidance on using dd to copy the PBR. I mounted a USB stick from the install environment and copied the PBR to that, then to Windows. Back in Windows, if you didn't f*** it up with the OpenBSD installer, follow the FAQ guidance on using BCDEdit, or perhaps, use the free (for non-commercial use) BCDEdit to add OpenBSD to the Windows bootloader. Reboot. Get into OpenBSD, if you followed the instructions correctly. Install exfat-fuse from packages, and use the mkfs.exfat tool to format the third partition for shared files. For whatever reason, Windows doesn't like to format hard disk partitions as Exfat, but you can do it from OpenBSD easily enough. Did I mention you should back up your data? Even I have messed up a few times. Fortunately, it was just a fresh Windows install that got clobbered last time I botched it. Good luck. I hope you come to enjoy OpenBSD as much as I do. On Sat, Jun 10, 2017 at 12:30 PM, Baho Utotwrote: > I am currently using FreeBSD 11.0 and win7. I have looked over OpenBSD > and I like what I am seeing. I have several machine to install it on an old > laptop Dell Inspirion 1501 and newer AMD64 machines with 8 cores and 16GB > ram. I would also like to install into Raspberry pi versions 2 and 3. > > I have the following questions: > > 1. Where can I get a list of graphics card that are supported? > > 2. Where can I find information on dual booting OpenBSD > and Windows? > > 3. Does OpenBSD need to be on the primary disk drive or can > it be installed on the second drive with windos on the > first drive. > > 4. Is the manul that is online, can it be obtained on a pdf? > > 5. Where can I find information on wifi support? > > These are the important question I have for now. > > Thanks > >