Re: httpd and Wordpress
+1
Wordpress must be installed on the desired path, if you are moving from
previous scheme like site/wordpress to wordpress, you have a problem. Refer
to wordpress manual and you find how to fix. The best bet is like Todd
said: Deploy again.
2017-06-10 20:56 GMT-03:00 Todd :
> What is in your httpd error log?
> My guess is that WP is trying to pull some content from /wordpress which no
> longer exists since you moved the docroot.
>
> My suggestion for having your WP site available without going to the
> /wordpress URL is to redeploy the WordPress files to /var/www/html instead
> of /var/www/html/wordpress.
> Or add a 301 redirect from / to /wordpress
>
> On Sat, Jun 10, 2017 at 2:32 PM, Jan Betlach wrote:
>
> > Hi guys,
> >
> > I have a small problem with httpd and Wordpress.
> > When I go to https://myipaddress I get "Access denied". If I go to
> > https://myipaddress/wordpress, everything works as expected.
> > I have tried to change the appropriate line in the httpd.conf to:
> > root "/htdocs/wordpress". In that case the webpage is loaded, but in the
> > "broken" form.
> >
> > My current httpd.conf:
> >
> > # $OpenBSD: httpd.conf,v 1.16 2016/09/17 20:05:59 tj Exp $
> > # Macros
> > ext_addr="*"
> > # Global Options
> > # prefork 3
> > # Servers
> > # A minimal default server
> > server "default" {
> > listen on $ext_addr port 80
> > listen on $ext_addr tls port 443 block return 301 "https://
> > $SERVER_NAME$REQUEST_URI"
> > tls {
> > key "/etc/ssl/private/server.key"
> > certificate "/etc/ssl/server.crt"
> > }
> > directory {
> > no auto index, index "index.php"
> > }
> > location "*.php" {
> > fastcgi socket "/run/php-fpm.sock"
> > }
> > root "/htdocs"
> > }
> > # Include MIME types instead of the built-in ones
> > types {
> > include "/usr/share/misc/mime.types"
> > }
> >
> >
> > Any ideas where I am making a mistake?
> >
> > Thank you
> >
> > Jan
> >
>
Re: Current FreeBSD looking to switch to OpenBSD
On Sat, Jun 10, 2017 at 09:20:49PM -0400, Baho Utot wrote: > > I dual boot now between Win7 and FreeBSD > > on I lapdog I have 5 os on it and use grub2 to boot them > > How is this helpful? I don't know. Some people just like talking about their computers to strangers, I guess. khm
Re: Current FreeBSD looking to switch to OpenBSD
On 06/10/17 16:20, Mihai Popescu wrote: I dual boot now between Win7 and FreeBSD on I lapdog I have 5 os on it and use grub2 to boot them Prepare in the upcoming messages for something like "OpenBSD destroyed my harddisk" subject line message! Just a warning. How is this helpful?
Re: httpd and Wordpress
Hi,
# Set a correct root path
root "/htdocs/wordpress"
# You can set max upload size to 513 M ( in bytes )
connection max request body 537919488
# You can protect files and dir
location "/.*" { block }
location "/ upload /*. php " { block }
location "/ files /*. php " { block }
# For any other PHP file
location "/*. php *" {
fastcgi socket "/ run / php - fpm . sock "}
Ilyes Aiouaz
Le 11/06/2017 à 00:56, Todd a écrit :
> What is in your httpd error log?
> My guess is that WP is trying to pull some content from /wordpress which no
> longer exists since you moved the docroot.
>
> My suggestion for having your WP site available without going to the
> /wordpress URL is to redeploy the WordPress files to /var/www/html instead
> of /var/www/html/wordpress.
> Or add a 301 redirect from / to /wordpress
>
> On Sat, Jun 10, 2017 at 2:32 PM, Jan Betlach wrote:
>
>> Hi guys,
>>
>> I have a small problem with httpd and Wordpress.
>> When I go to https://myipaddress I get "Access denied". If I go to
>> https://myipaddress/wordpress, everything works as expected.
>> I have tried to change the appropriate line in the httpd.conf to:
>> root "/htdocs/wordpress". In that case the webpage is loaded, but in the
>> "broken" form.
>>
>> My current httpd.conf:
>>
>> # $OpenBSD: httpd.conf,v 1.16 2016/09/17 20:05:59 tj Exp $
>> # Macros
>> ext_addr="*"
>> # Global Options
>> # prefork 3
>> # Servers
>> # A minimal default server
>> server "default" {
>> listen on $ext_addr port 80
>> listen on $ext_addr tls port 443 block return 301 "https://
>> $SERVER_NAME$REQUEST_URI"
>> tls {
>> key "/etc/ssl/private/server.key"
>> certificate "/etc/ssl/server.crt"
>> }
>> directory {
>> no auto index, index "index.php"
>> }
>> location "*.php" {
>> fastcgi socket "/run/php-fpm.sock"
>> }
>> root "/htdocs"
>> }
>> # Include MIME types instead of the built-in ones
>> types {
>> include "/usr/share/misc/mime.types"
>> }
>>
>>
>> Any ideas where I am making a mistake?
>>
>> Thank you
>>
>> Jan
>>
signature.asc
Description: OpenPGP digital signature
Re: httpd and Wordpress
What is in your httpd error log?
My guess is that WP is trying to pull some content from /wordpress which no
longer exists since you moved the docroot.
My suggestion for having your WP site available without going to the
/wordpress URL is to redeploy the WordPress files to /var/www/html instead
of /var/www/html/wordpress.
Or add a 301 redirect from / to /wordpress
On Sat, Jun 10, 2017 at 2:32 PM, Jan Betlach wrote:
> Hi guys,
>
> I have a small problem with httpd and Wordpress.
> When I go to https://myipaddress I get "Access denied". If I go to
> https://myipaddress/wordpress, everything works as expected.
> I have tried to change the appropriate line in the httpd.conf to:
> root "/htdocs/wordpress". In that case the webpage is loaded, but in the
> "broken" form.
>
> My current httpd.conf:
>
> # $OpenBSD: httpd.conf,v 1.16 2016/09/17 20:05:59 tj Exp $
> # Macros
> ext_addr="*"
> # Global Options
> # prefork 3
> # Servers
> # A minimal default server
> server "default" {
> listen on $ext_addr port 80
> listen on $ext_addr tls port 443 block return 301 "https://
> $SERVER_NAME$REQUEST_URI"
> tls {
> key "/etc/ssl/private/server.key"
> certificate "/etc/ssl/server.crt"
> }
> directory {
> no auto index, index "index.php"
> }
> location "*.php" {
> fastcgi socket "/run/php-fpm.sock"
> }
> root "/htdocs"
> }
> # Include MIME types instead of the built-in ones
> types {
> include "/usr/share/misc/mime.types"
> }
>
>
> Any ideas where I am making a mistake?
>
> Thank you
>
> Jan
>
Re: Can I use OpenBSD as a desktop system?
Sun, 11 Jun 2017 00:43:19 +0200 Marc Espie > On Sat, Jun 10, 2017 at 12:55:04PM +0200, Nicolas Schmidt wrote: > > > > >> On 06/09/17 15:39, SOUL_OF_ROOT 55 wrote: > > >> Can I use OpenBSD as a desktop system? > > > > > > You? No, I doubt it. > > ... > > > But, you are welcome, and invited > > ... > > > Nick. > > > > Nick, I don't think you were being either welcoming or inviting there. > > Oh, come on this list isn't politically correct, and Nick's answer was > very funny. If the original poster doesn't see the humor, well, he's > probably not right for OpenBSD in any case. > > And yeah, you must be this tall to run OpenBSD pretty much says it all > actually. 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
Re: Current FreeBSD looking to switch to OpenBSD
Hi Erling,
Erling Westenvik wrote on Sat, Jun 10, 2017 at 10:08:57PM +0200:
> Probably a stupid question but:
> Why isn't the -T switch documented in man(1)?
Not a stupid question at all.
First answer:
It is, look at man(1) and you will find this sentence:
The options -IKOTW are also supported and are documented in mandoc(1).
Second answer:
The reason why it isn't in the SYNOPSIS, in the usage(), and in the
main options list is that jmc@ insisted that the man(1) manual page
better be short and simple, and advanced stuff that is more fully
documented in mandoc(1), and more often needed in mandoc(1), not
be duplicated there. He kind of has a point. The man(1) manual
is most important for beginners and should better not overwhelm
them. Advanced users are likely to also find their way if finding
the advanced features requires carefully studying the *whole* text.
I designed the user interface of the OpenBSD versions of man(1),
apropos(1), whatis(1), and mandoc(1) such that all four support
exactly the same options, such that you only need to learn one set
of options, which is not true on other operating systems. If you
like a bit of confusion now and then, take a look at:
http://mdocml.bsd.lv/man/man.options.1.html
Yes, -AxY are the only three option letters not yet taken, and all
except -BGJjNOUXyZz have conflicting meanings; the record holders
are -c with nine different meanings, -p and -s with eight, -f and
-w with seven, and several with six different meanings. Talk about
history -- as if nobody ever looked at what anybody else did...
On OpenBSD, if you like, you can access all functionality of the
four utilities with man(1):
apropos == man -k
whatis == man -f
mandoc == man -cl
Also, our options are designed to naturally form four groups
and are firmly grounded in BSD history, with one exception
adopted from Colin Watson's Debian Linux man-db package:
1. Search options decide which directories are used for searches:
-M override MANPATH ("manpath", 4.3BSD man, 1986)
-m augment MANPATH ("manpath", 4.3BSD-Reno man, 1990)
-S restrict architecture ("subsection", OpenBSD 2.3 man, 1998)
-s restrict manual section ("section", OpenBSD 2.3 man, 1998)
2. Input options decide how command line arguments are interpreted:
-k use full search query syntax ("keywords", 4BSD man, 1980)
(default for -k) search substrings in title lines only
-f complete words to be matched in names only ("find", 4BSD man, 1980)
(default for man(1)) exact match of complete names
-l accept file names, ignore search options ("local", man-db 2.2a7, 1994)
3. Parse options influence interpretation of the input files:
-I set default value for .Os macro ("input", OpenBSD 5.2 mandoc, 2012)
-K force an input character encoding ("enKoding", groff-1.20, 2005)
-m force an input macro language ("macro language", v7 troff, 1979)
4. Output options decide how output is presented:
-a show all matching pages, formatted ("all", 4.3BSD-Tahoe man, 1988)
(default for man(1)) show the first matching page, formatted
-T select an output format for formatting ("terminal", v7 nroff, 1979)
-O set output format specific options ("output", OpenBSD 4.8 mandoc, 2009)
-c do no use a pager ("copy to stdout", 4.3BSD-Reno man, 1990)
-h show the SYNOPSIS sections only ("head", 4.3BSD-Net/2 man, 1991)
(default for -k and -h) show title lines only
-w show file names only ("where", v7 man, 1979)
-W select a message level ("warn", OpenBSD 4.8 mandoc, 2009)
5. One special option can influence search, parse, and output options:
-C select alternate config file ("config", 4.4BSD-Lite1 apropos, 1994)
Unfortunately, this structure cannot easily be represented in
the manual pages without bloating them and making them less readable.
Several of the option letters could be more mnemonic. But they
come from six different programs (troff, nroff, groff, man, apropos,
mandoc) and five different operating systems (Version 7 AT&T Unix,
4.xBSD, groff, Debian man-db, OpenBSD) and the oldest (-mTw) have
been established since 1979, so people have become so used to them
for several decades that it's much too late to change any of them.
Yours,
Ingo
Re: Current FreeBSD looking to switch to OpenBSD
On Sat, Jun 10, 2017 at 9:20 PM, Mihai Popescu wrote: > > I dual boot now between Win7 and FreeBSD > > on I lapdog I have 5 os on it and use grub2 to boot them > > Prepare in the upcoming messages for something like "OpenBSD destroyed > my harddisk" subject line message! Just a warning. > > OpenBSD 6.1 release has a bug with nvme drives. The disk partitioning program in the installer read my gpt partition incorrectly. Once I noticed this I immediately rebooted my machine but it was too late. The partition table was completely hosed. I suspect that after the incorrect read maybe it thought my disk was corrupted or had no table and wrote a fresh one for me automatically. It actually sounds like a bug that the installer would write to your disk if you bail out before taking any action. Even if thinks (correctly or incorrectly) that your disk may have a corrupted partition table it should do no writes until you actually commit to repartitioning the disk. The nvme bug appears to be fixed in the latest OpenBSD development snapshots. Dual booting OpenBSD is rather easy on UEFI systems. I've got Windows 10, FreeBSD 11, OpenBSD Current, and Arch Linux all on my laptop. I would suggest partitioning the disk manually first using a gparted livecd or similar. Create the partitions and set all of the correct partition types for your OSes before hand. I did this and then OpenBSD correctly identified my OpenBSD partition and installed the OS on it. Has no problem booting with UEFI/GPT with all of my other OSes present. Backing up your disk (including your partition table) first would be prudent of course.
Re: Can I use OpenBSD as a desktop system?
On Sat, Jun 10, 2017 at 12:55:04PM +0200, Nicolas Schmidt wrote: > > >> On 06/09/17 15:39, SOUL_OF_ROOT 55 wrote: > >> Can I use OpenBSD as a desktop system? > > > > You? No, I doubt it. > ... > > But, you are welcome, and invited > ... > > Nick. > > Nick, I don't think you were being either welcoming or inviting there. Oh, come on this list isn't politically correct, and Nick's answer was very funny. If the original poster doesn't see the humor, well, he's probably not right for OpenBSD in any case. And yeah, you must be this tall to run OpenBSD pretty much says it all actually.
Re: SCSI Enclosure Service
Hello David, Thanks for your explanation. On the occation of the next service among other things I will test the replacement of mpii by mfii hardware as well as all brands of (more or less sensitive) MiniSAS cablings I have at hand ... With best regards, Jens On 06/09/17 03:57, David Gwynne wrote: hey jens, from what i can tell, you talk to the ami mg9071 chips on that enclosure using sgpio, not in band using smp (sas mgmt protocol) or ses as a scsi device. i get the impression that mpii hardware does have some understanding of enclosures connected via sgpio, but i'm not sure what benefit it would provide. it may affect addressing on the bus, but im not sure you'd get temperatures or fan speeds or anything off it. cheers, dlg On 9 Jun 2017, at 02:05, Jens A. Griepentrog wrote: Dear Listeners, Let me know, please, if enclosure monitoring is supported for disks attached to Supermicro M28SAB drive cages (with two AMI MG9071 chips) or similar backplanes. Drives work fine when attached to some LSI 2008 controller but there appear no "ses* at scsibus?" boot messages (see below, disks attached to the drive cage are sd4 ... sd11), jumper settings on the cage: JP61 2-3: Fan disabled (there is no fan) JP62 1-2: Enclosure monitor enabled With best regards, Jens OpenBSD 6.1 (GENERIC.MP) #6: Mon May 22 20:34:30 CEST 2017 rob...@syspatch-61-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17154113536 (16359MB) avail mem = 16629547008 (15859MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xf06f0 (62 entries) bios0: vendor American Megatrends Inc. version "0705" date 06/29/2010 bios0: ASUSTeK Computer INC. P7F-M WS acpi0 at bios0: rev 2 acpi0: sleep states S0 S1 S3 S4 S5 acpi0: tables DSDT FACP APIC MCFG OEMB HPET SSDT acpi0: wakeup devices BR1E(S4) UAR1(S4) PS2K(S4) EUSB(S4) USB0(S4) USB1(S4) USB2(S4) USB3(S4) USBE(S4) USB4(S4) USB5(S4) USB6(S4) BR21(S4) BR22(S4) BR23(S4) P0P1(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) Xeon(R) CPU L3426 @ 1.87GHz, 1867.00 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,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR cpu0: 256KB 64b/line 8-way L2 cache cpu0: TSC frequency 1867000680 Hz cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 133MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Xeon(R) CPU L3426 @ 1.87GHz, 1866.73 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,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Xeon(R) CPU L3426 @ 1.87GHz, 1866.73 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,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Xeon(R) CPU L3426 @ 1.87GHz, 1866.73 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,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 3, package 0 ioapic0 at mainbus0: apid 7 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 7 (BR1E) acpiprt2 at acpi0: bus -1 (BR21) acpiprt3 at acpi0: bus -1 (BR22) acpiprt4 at acpi0: bus -1 (BR23) acpiprt5 at acpi0: bus -1 (P0P1) acpiprt6 at acpi0: bus 1 (P0P3) acpiprt7 at acpi0: bus -1 (P0P4) acpiprt8 at acpi0: bus -1 (P0P5) acpiprt9 at acpi0: bus -1 (P0P6) acpiprt10 at acpi0: bus 2 (BR20) acpiprt11 at acpi0: bus 5 (BR26) acpiprt12 at acpi0: bus 6 (BR27) acpicpu0 at acpi0: !C3(350@17 mwait.1@0x20), !C3(500@17 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: !C3(350@17 mwait.1@0x20), !C3(500@17 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: !C3(350@17 mwait.1@0x20), !C3(500@17 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: !C3(350@17 mwait.1@0x20), !C3(500@17 mwait.1@0x10), C1(1000@1 mwait.1), PSS "PNP0501" at acpi0 not configured "PNP0303" at acpi0 not configured acpibtn0 at acpi0: PWRB ipmi
Re: LACP problem
On 10/06/2017 19:15, Lyndon Nerenberg wrote: > Not really, other than running tcpdump on the two interfaces and > examining the LACP protocol packets to try to discover why the > negotiation is acting the way it is. OK, that sounds like an even deeper rabbit-hole. > Also, if you don't have the enable password, how did you configure > LACP on the switch to begin with? Fair question: via the web UI. That would imply it's not just a front-end for the CLI, which implies another set of potential security issues. Not an issue for this network, but certainly something to consider in future.
Re: Current FreeBSD looking to switch to OpenBSD
> I dual boot now between Win7 and FreeBSD > on I lapdog I have 5 os on it and use grub2 to boot them Prepare in the upcoming messages for something like "OpenBSD destroyed my harddisk" subject line message! Just a warning.
httpd and Wordpress
Hi guys,
I have a small problem with httpd and Wordpress.
When I go to https://myipaddress I get "Access denied". If I go to
https://myipaddress/wordpress, everything works as expected.
I have tried to change the appropriate line in the httpd.conf to:
root "/htdocs/wordpress". In that case the webpage is loaded, but in the
"broken" form.
My current httpd.conf:
# $OpenBSD: httpd.conf,v 1.16 2016/09/17 20:05:59 tj Exp $
# Macros
ext_addr="*"
# Global Options
# prefork 3
# Servers
# A minimal default server
server "default" {
listen on $ext_addr port 80
listen on $ext_addr tls port 443 block return 301 "https://
$SERVER_NAME$REQUEST_URI"
tls {
key "/etc/ssl/private/server.key"
certificate "/etc/ssl/server.crt"
}
directory {
no auto index, index "index.php"
}
location "*.php" {
fastcgi socket "/run/php-fpm.sock"
}
root "/htdocs"
}
# Include MIME types instead of the built-in ones
types {
include "/usr/share/misc/mime.types"
}
Any ideas where I am making a mistake?
Thank you
Jan
Re: Current FreeBSD looking to switch to OpenBSD
On 06/10/17 14:12, Ingo Schwarze wrote: Hi, Baho Utot wrote on Sat, Jun 10, 2017 at 01:30:46PM -0400: 1. Where can I get a list of graphics card that are supported? $ man -s 4 -k graphic drm radeon On modern amd64, it is mostly intel(4) and radeon(4). Stay away from NVidia unless you want to use vga(4). 2. Where can I find information on dual booting OpenBSD and Windows? Don't do it. Use separate hardware. Dual booting is only asking for trouble. It's not impossible if you know what you are doing, but even then, it's not worth it. If you have to ask how it works, just don't do it. I dual boot now between Win7 and FreeBSD on I lapdog I have 5 os on it and use grub2 to boot them 4. Is the manul that is online, can it be obtained on a pdf? $ time man -M/usr/share/man -Tpdf -ak Nd~. > all.pdf 1m03.33s real 0m52.16s user 0m03.22s system $ wc all.pdf 165640334 587327767 3457322371 all.pdf That's only the base system manual (without X11 = Xenocara). Even though building it with mandoc(1) only takes a minute on my notebook, i'm not sure it's a great idea to put all that information into a single file. It's a 15458 page, 3.5 Gigabyte PDF. If you want to read specific sections, you can use more specific commands, see apropos(1). Or you can view individual typeset pages like this: $ doas pkg_add gv $ man -Tps pledge | gv - 5. Where can I find information on wifi support? $ man -k wireless https://www.openbsd.org/faq/faq6.html#Wireless Yours, Ingo Thanks
Re: Current FreeBSD looking to switch to OpenBSD
On Sat, Jun 10, 2017 at 08:12:31PM +0200, Ingo Schwarze wrote: > Hi, > > Baho Utot wrote on Sat, Jun 10, 2017 at 01:30:46PM -0400: > > > 5. Where can I find information on wifi support? > > $ man -k wireless > > https://www.openbsd.org/faq/faq6.html#Wireless Also, http://man.openbsd.org/ is very useful - go there, type your keyword in the search field, click apropos and you get all the man pages matching that keyword. -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
Re: LACP problem
> On Jun 10, 2017, at 10:44 AM, Charles Lecklider > wrote: > > Is there no other diagnostic information I can get from the OpenBSD side? Not really, other than running tcpdump on the two interfaces and examining the LACP protocol packets to try to discover why the negotiation is acting the way it is. Also, if you don't have the enable password, how did you configure LACP on the switch to begin with?
Re: Current FreeBSD looking to switch to OpenBSD
Hi, Baho Utot wrote on Sat, Jun 10, 2017 at 01:30:46PM -0400: > 1.Where can I get a list of graphics card that are supported? $ man -s 4 -k graphic drm radeon On modern amd64, it is mostly intel(4) and radeon(4). Stay away from NVidia unless you want to use vga(4). > 2.Where can I find information on dual booting OpenBSD > and Windows? Don't do it. Use separate hardware. Dual booting is only asking for trouble. It's not impossible if you know what you are doing, but even then, it's not worth it. If you have to ask how it works, just don't do it. > 4.Is the manul that is online, can it be obtained on a pdf? $ time man -M/usr/share/man -Tpdf -ak Nd~. > all.pdf 1m03.33s real 0m52.16s user 0m03.22s system $ wc all.pdf 165640334 587327767 3457322371 all.pdf That's only the base system manual (without X11 = Xenocara). Even though building it with mandoc(1) only takes a minute on my notebook, i'm not sure it's a great idea to put all that information into a single file. It's a 15458 page, 3.5 Gigabyte PDF. If you want to read specific sections, you can use more specific commands, see apropos(1). Or you can view individual typeset pages like this: $ doas pkg_add gv $ man -Tps pledge | gv - > 5.Where can I find information on wifi support? $ man -k wireless https://www.openbsd.org/faq/faq6.html#Wireless Yours, Ingo
Re: Current FreeBSD looking to switch to OpenBSD
You will find all of your answers on the FAQ, in regards to the PDF stuff well you can export man pages as PDF's. https://www.openbsd.org/faq/ Good luck and enjoy OpenBSD Original Message Subject: Current FreeBSD looking to switch to OpenBSD Local Time: June 10, 2017 7:30 PM UTC Time: June 10, 2017 5:30 PM From: baho-u...@columbus.rr.com To: misc@openbsd.org 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
Re: LACP problem
On 09/06/2017 04:07, Lyndon Nerenberg wrote: > The first step is to have the switch display its idea of the LACP > configuration and status. That's turning into a bit of a mission Seems TP-LINK don't set an enable password by default so I can't get what I need via ssh until I've set that. To set it I need to connect to the console port, which means finding the cable and a serial-to-USB adapter. I have all the above (somewhere), it's just going to take some time. Is there no other diagnostic information I can get from the OpenBSD side?
Current FreeBSD looking to switch to OpenBSD
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
Re: Can I use OpenBSD as a desktop system?
I would say it depends. 1. What are your requirements -Do you need to propriety programs like Skype? Skype don't run on openbsd -Do you need the latest software? You might don't find the latest software on the ports. Of course you can always port it if its open source on OpenBSD but its time consuming. -What do you think should happen when a program has a memory bug if you think that it should be terminated then openbsd is fine for you. -Do you need a really secure OS? Security is openbsd focus. 2. What is your hardware? -OpenBSD doesn't support newer hardware. Skylake etc I bought my laptop last summer and my laptop wasn't usable until a couple of months ago. Skylake wasn't supported, I couldn't use the browser, the webcam, the wifi, the bluetooth or the card reader and writing to my usb was extremely slow. I uninstall openbsd and installed it a couple of months ago. Now wifi works (although still not perfect) and browser works fine. I usually don't need webcam or card reader so I don't mind that much that they don't work. I also have a second laptop in case I need webcam or card reader.
Re: Can I use OpenBSD as a desktop system?
May i suggest you to check https://sivers.org/openbsd It helped me when i was just starting because mr sivers share a few tips and config files to begin working with openBSD in minutes. In my case in did change the window manager later from ratpoison to i3 and then finally i was able to config cwm. (Really cool to have all system up and running in 60 mb RAM usage!!) Manuel El 10/06/2017, a las 08:07, Mihai Popescu escribió: >> Can I use OpenBSD as a desktop system? > > I don't think so, because OpenBSD does not care about desktop users. > In fact, the solely purpose of OpenBSD system is to make/build the next > release. >
Firefox and Seamonkey total lockup on -current(i386)
Since the last two upgrades of -current on i386 I've had total lockups
(no keys working) with Firefox and Seamonkey. Firefox works for about a
minute before locking up; Seamonkey doesn't even start.
Firefox-esr works OK and so does Chromium. It isn't a hardware problem;
the same thing has happened on two different machines.
There is no problem with the 6.1 -release version.
Anyone else seeing this?
dmesg:
OpenBSD 6.1-current (GENERIC.MP) #108: Fri Jun 9 20:46:40 MDT 2017
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Genuine Intel(R) CPU T2400 @ 1.83GHz ("GenuineIntel" 686-class) 1.83 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,SSE3,MWAIT,VMX,EST,TM2,xTPR,PDCM,PERF,SENSOR
real mem = 2137407488 (2038MB)
avail mem = 2083217408 (1986MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: date 08/29/06, BIOS32 rev. 0 @ 0xfd6b0, SMBIOS rev. 2.4 @
0xe0010 (68 entries)
bios0: vendor LENOVO version "79ET67WW (1.11 )" date 08/29/2006
bios0: LENOVO 1951WAZ
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT ECDT TCPA APIC MCFG HPET BOOT SSDT SSDT SSDT
acpi0: wakeup devices LID_(S3) SLPB(S3) EXP0(S4) EXP1(S4) EXP2(S4) EXP3(S4)
PCI1(S4) USB0(S3) USB1(S3) USB2(S3) USB7(S3) HDEF(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpiec0 at acpi0
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 166MHz
cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Genuine Intel(R) CPU T2400 @ 1.83GHz ("GenuineIntel" 686-class) 1.83 GHz
cpu1:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,SSE3,MWAIT,VMX,EST,TM2,xTPR,PDCM,PERF,SENSOR
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
acpimcfg0 at acpi0 addr 0xf000, bus 0-63
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (AGP_)
acpiprt2 at acpi0: bus 2 (EXP0)
acpiprt3 at acpi0: bus 3 (EXP1)
acpiprt4 at acpi0: bus 4 (EXP2)
acpiprt5 at acpi0: bus 12 (EXP3)
acpiprt6 at acpi0: bus 21 (PCI1)
acpicpu0 at acpi0: !C3(100@17 io@0x1015), !C2(500@1 io@0x1014), C1(1000@1
halt), PSS
acpicpu1 at acpi0: !C3(100@17 io@0x1015), !C2(500@1 io@0x1014), C1(1000@1
halt), PSS
acpipwrres0 at acpi0: PUBS, resource for USB0, USB2, USB7
acpitz0 at acpi0: critical temperature is 127 degC
acpitz1 at acpi0: critical temperature is 99 degC
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
"PNP0303" at acpi0 not configured
"IBM0057" at acpi0 not configured
"IBM0071" at acpi0 not configured
"ATM1200" at acpi0 not configured
acpibat0 at acpi0: BAT0 model "COMPATIBLE" serial 1242 type LION oem "SANYO"
acpiac0 at acpi0: AC unit online
acpithinkpad0 at acpi0
acpidock0 at acpi0: GDCK not docked (0)
acpivideo0 at acpi0: VID_
acpivideo1 at acpi0: VID_
bios0: ROM list: 0xc/0xe400! 0xce800/0x1000 0xcf800/0x1000 0xdc000/0x4000!
0xe/0x1
cpu0: Enhanced SpeedStep 1829 MHz: speeds: 1833, 1333, 1000 MHz
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82945GM Host" rev 0x03
inteldrm0 at pci0 dev 2 function 0 "Intel 82945GM Video" rev 0x03
drm0 at inteldrm0
intagp0 at inteldrm0
agp0 at intagp0: aperture at 0xd000, size 0x1000
inteldrm0: apic 1 int 16
inteldrm0: 1024x768, 32bpp
wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
"Intel 82945GM Video" rev 0x03 at pci0 dev 2 function 1 not configured
azalia0 at pci0 dev 27 function 0 "Intel 82801GB HD Audio" rev 0x02: msi
azalia0: codecs: Analog Devices AD1981HD, Conexant/0x2bfa, using Analog Devices
AD1981HD
audio0 at azalia0
ppb0 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x02: apic 1 int 20
pci1 at ppb0 bus 2
em0 at pci1 dev 0 function 0 "Intel 82573L" rev 0x00: msi, address
00:16:41:aa:de:2d
ppb1 at pci0 dev 28 function 1 "Intel 82801GB PCIE" rev 0x02: apic 1 int 21
pci2 at ppb1 bus 3
ath0 at pci2 dev 0 function 0 "Atheros AR5212" rev 0x01: apic 1 int 17
ath0: AR5424 10.3 phy 6.1 rf5424 10.2 eeprom 5.3, WOR2W, address
00:16:cf:4b:25:b5
ppb2 at pci0 dev 28 function 2 "Intel 82801GB PCIE" rev 0x02: apic 1 int 22
pci3 at ppb2 bus 4
ppb3 at pci0 dev 28 function 3 "Intel 82801GB PCIE" rev 0x02: apic 1 int 23
pci4 at ppb3 bus 12
uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x02: apic 1 int 16
uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x02: apic 1 int 17
uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x02: apic 1 int 18
uhci3 at pci0 dev 29 function 3 "Intel 82801GB USB" rev 0x02: apic 1 int 19
ehci0 at pci0 dev 29 function 7 "Intel 82801GB USB" rev 0x02: apic 1 int 19
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0
Re: Can I use OpenBSD as a desktop system?
> Can I use OpenBSD as a desktop system? I don't think so, because OpenBSD does not care about desktop users. In fact, the solely purpose of OpenBSD system is to make/build the next release.
Re: watchdog - "Intel 6300ESB WDT" rev 0x00 at pci0 dev 4 function 0 not configured
On Tue, Mar 14, 2017 at 08:10:50PM -0400, Jiri B wrote: > On Tue, Mar 14, 2017 at 03:52:17PM -0700, Mike Larkin wrote: > > > [...] > > > virtio0 at pci0 dev 3 function 0 "Qumranet Virtio Network" rev 0x00 > > > vio0 at virtio0: address 52:54:00:b8:93:d9 > > > virtio0: msix shared > > > "Intel 6300ESB WDT" rev 0x00 at pci0 dev 4 function 0 not configured > > > ... > > > > > > # sysctl -a | grep watch > > > # > > > > > > Shouldn't this be detected as ichwdt(4)? > > > > > > ichwdt(4) - Intel 6300ESB ICH watchdog timer device > > > > > > > Looks like it was only ever "built" for i386, and not extensively tested > > even > > then: > > > > revision 1.411 > > date: 2005/05/02 17:26:00; author: grange; state: Exp; lines: +2 -1; > > Add ichwdt(4): Intel 6300ESB ICH watchdog timer driver. Disabled for > > now due to lack of testing. If you have a machine that uses this > > device please contact me. > > > > -ml > > Hi, > > it seems i6300esb is only watchdog usable on qemu-kvm. There's also some > ib700 but it is ISA device and diag288 which is applicable only to IBM s/390 > and > zSeries. > > Should I give a try to i386 with rebuilt kernel? i6300esb is also default > watchdog > in RHV[1]/oVirt but I doubt anybody uses OpenBSD on it except me sporadically > :) Did you get anywhere with this? I'm looking at the same thing right now, especially as my OpenBSD boxes on libvirt keep hanging. > [1] > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.0/html/virtual_machine_management_guide/sect-configuring_a_watchdog > > j. >
Re: Can I use OpenBSD as a desktop system?
On 10 June 2017 at 06:55, Nicolas Schmidt wrote: > >>> On 06/09/17 15:39, SOUL_OF_ROOT 55 wrote: >>> Can I use OpenBSD as a desktop system? >> >> You? No, I doubt it. > ... >> But, you are welcome, and invited > ... >> Nick. > > Nick, I don't think you were being either welcoming or inviting there. > > To answer OP's question: Yes of course you can, and I did so in the past. The > experience wasn't bad, although of course using any free Unix as a desktop > system is guaranteed to deliver some pain at least (don't expect it to "just > work"). I disagree a bit. Over the years, I've run a variety of Linux systems, plus all the BSD systems, including Dragonfly. Quite awhile ago, I settled on OpenBSD as my primary system, and I run it on all my machines where the hardware is supported, which pretty much means something other than Nvidia video hardware (I have one such beast, on which I run Slackware). Installing OpenBSD is as painless as any of them and probably takes less time than any of them to get to the initial boot-up. I have a script that sets up PKG_PATH and then pkg_adds the packages I need. I run a minimal setup, with a window manager and a few supporting applications, e.g., dmenu, rox, I do find that I have to modify the default datasizes in /etc/login.conf to prevent firefox from running out of memory and collapsing. I also set up an /etc/doas.conf (thank you Ted!) so things that require root privileges can be done without a fuss. I've chosen this system because of the attention to security, its quality (it is just rock solid), and the documentation (the best, by a significant margin). Performance was an issue for me in the past, but that is no longer the case. I've gotten the impression that a lot of effort has gone into performance recently and it shows. I run 'current', by the way, and the only problems I've encountered were my own doing. /Don > > Nicolas
Re: Can I use OpenBSD as a desktop system?
>> On 06/09/17 15:39, SOUL_OF_ROOT 55 wrote: >> Can I use OpenBSD as a desktop system? > > You? No, I doubt it. ... > But, you are welcome, and invited ... > Nick. Nick, I don't think you were being either welcoming or inviting there. To answer OP's question: Yes of course you can, and I did so in the past. The experience wasn't bad, although of course using any free Unix as a desktop system is guaranteed to deliver some pain at least (don't expect it to "just work"). Nicolas
Re: Can I use OpenBSD as a desktop system?
Yes, u can! And you can read the FAQ about X Window System: https://www.openbsd.org/faq/faq11.html ;) In fact, i use on Dell AlienWare AW13 :p Le 06/09/17 à 21:39, SOUL_OF_ROOT 55 a écrit : > Can I use OpenBSD as a desktop system? > -- ~ " Fully Basic System Distinguish Life! " ~ " Libre as a BSD " +=<<< Stephane HUC as PengouinBSD or CIOTBSD b...@stephane-huc.net signature.asc Description: OpenPGP digital signature
Re: Can I use OpenBSD as a desktop system?
typing startx isn't even needed if you enable xenodm at install Je 2017-06-10 00:00, Edgar Pettijohn skribis: As long as you can type startx at the command prompt, then yes. Sent from BlueMail On Jun 9, 2017, 3:07 PM, at 3:07 PM, Johan Mellberg wrote: Yes. 2017-06-09 21:39 GMT+02:00 SOUL_OF_ROOT 55 : Can I use OpenBSD as a desktop system?
