diego righi wrote:
> So let's say I'm a fool, I use a foolish partition layout, and the intel x86
> and amd64 architectures are tricky/shitty architectures with stupid bioses
> which work bad, ok?
> So why openbsd 6.4 i386 and amd64 bootloaders (not biosboot, boot!)
> express different behavior?
So let's say I'm a fool, I use a foolish partition layout, and the intel x86
and amd64 architectures are tricky/shitty architectures with stupid bioses
which work bad, ok?
So why openbsd 6.4 i386 and amd64 bootloaders (not biosboot, boot!)
express different behavior? Wasn't openbsd about
Summery + update:
So I thought I'd post one final update for the time being, it's been a long
two day's reading man pages and looking though mailing lists/forums/reddit
posts, and summary of where I'm at in case anyone in the future wants help.
I'll
Firstly, no matter how I try to install I
Why are so many people lining up to die on the "One big root partition"
hill? Partition your disks for fuck's sake, or if you are too lazy to
do that, just let the installer do it for you. And, no, it doesn't
"just work", it doesn't, it just hasn't broken yet.
Also, both install.i386 and
Hi,
Hope this will help you:
https://www.openbsd.org/macppc.html
search down to Boot device considerations (ultra0 for example boot
ultra0:,ofwboot /bsd)
Also perhaps this guide will help you in firmware
http://www.firmworks.com/QuickRef.html
(there is the devalias command in open
On 2018-10-24, Markus Rosjat wrote:
> Hi there,
>
> it seems to get sasl working with ldap is a lifetime task. Sad thing I
> had it working but only after adding/deleting packages of the specific
> versions of cyrus-sasl and I dont know which you really need to get it
> working in a "clean"
So now I try to reply, I don't want to sound like a troll, because I'm
an openbsd
user and supporter since very long time and I know that with a proper bug report
the full dmesg should be provided and possibly even more...
...but to keep things short I've this ECS GF8100VM-M5 motherboard that I
I can confirm the same problem on 6.4 GENERIC.MP#364 amd64
Is there any solution?
diego righi wrote:
> Big "a" slice may not be advised and not secure for production, but it
> always worked.
Do you have evidence?
> (and on i386 it still works, even on amd64 with the i386 bootloader)
Evidence supplied?
BTW, the i386 and amd64 bootloaders are largely identical. You better
Big "a" slice may not be advised and not secure for production, but it
always worked.
(and on i386 it still works, even on amd64 with the i386 bootloader)
So I agree that it is not good practice but to quick test machines I've did
it many times.
(and never found in the FAQ nor in the manpages that
On Thu, Oct 25, 2018 at 07:02:20PM +, mabi wrote:
> Indeed, I just created one huge "a" slice with 500 GB for my / root
> partition. I will try first to create a smaller/many slices...
>
This has occurred three times just this week. I'm curious why you did this;
is there a new FAQ or
Indeed, I just created one huge "a" slice with 500 GB for my / root partition.
I will try first to create a smaller/many slices...
@Kristjan: "entry point at ..." no it didn't even get to this line, it just
rebooted at the line counting all these numbers, I think that it the very first
line of
I’m trying to run OpenBSD and Tiger on one hard drive on a Mac G4 tower. I’ve
successfully installed 6.4 onto the drive and I can still boot from Tiger, so
that’s good. I then copied ofwboot to the Tiger partition (since it’s the first
HFS+ partition).
I have an Silicon Image 3112-based PCI
Does it get to the "entry point at ..." line?
V V čet., 25. okt. 2018 ob 20:02 je oseba diego righi
napisala:
> did you make only one big a slice?
> try to put the i386 bootloader ;)
>
> On Thu, Oct 25, 2018, 18:20 mabi wrote:
>
> > Hi,
> >
> > I just installed OpenBSD 6.4 on an older Dell
did you make only one big a slice?
try to put the i386 bootloader ;)
On Thu, Oct 25, 2018, 18:20 mabi wrote:
> Hi,
>
> I just installed OpenBSD 6.4 on an older Dell PowerEdge R410 server. The
> installation went fine but upon reboot I get to the "boot>" prompt then the
> first line of the
Hi,
I just installed OpenBSD 6.4 on an older Dell PowerEdge R410 server. The
installation went fine but upon reboot I get to the "boot>" prompt then the
first line of the OpenBSD boot starts with all the numbers displaying but like
2 seconds later the whole server reboots. Any idea what that
Trying to change my resolution to 1650x1050:
$ gtf 1650 1050 60
> Modeline "1648x1050_60.00" 144.01 1648 1752 1928 2208 1050 1051 1054 1087
-Hsync +Vsync
$ xrandr --newmode "1648x1050_60.00" 144.01 1648 1752 1928 2208 1050 1051
1054 1087 -Hsync +Vsync
> xrandr: Failed to get size of gamma for
Thanks, Andre
I reverted my change to rc.subr
I tried what you suggested and it seemed to work,
(believe it or not,
I tried somehting similar this morning but i must have had typo in my
syntax)
Thanks Tom Smyth
On Thu, 25 Oct 2018 at 13:53, Andre Stoebe wrote:
>
> Use "rcctl set unbound timeout
Use "rcctl set unbound timeout 300", which sets "unbound_timeout=300" in
rc.conf.local. The variables are documented in rc.d(8).
Regards
André
Hello,
to resolve the rcctl start unbound timeout issue,
I tried increasing daemon_timeout value in multiple files (and failing)
finally i edited line 300 of /etc/rc.d/rc.subr
- [ -z "${daemon_timeout}" ] && daemon_timeout=30
+ [ -z "${daemon_timeout}" ] && daemon_timeout=300
On 10/25/18 9:12 AM, Alexandre Ratchov wrote:
> i did a quick test, playback works in chrome; any hints on how to
> reproduce the sound problem?
Thankyou. It is my fault. I must have been tired or it's been working so long
without any notice side effects that I missed the obvious.
I use the
On Wed, Oct 24, 2018 at 10:23:27PM +0100, Kevin Chadwick wrote:
> I've made the pledge and entered the veil with Chrome.
>
> Sound works without restarting sndiod in other applications like aucat and
> mozilla apps.
>
> For some reason the sound does not work in chrome even without enabling the
Hi Predrag,
Thanks for taking a look,
im running
OpenBSD fns1.ogmaconnect.com 6.4 GENERIC.MP#364 amd64
It would appear that the killed message was due to insufficient memory on
the
machine,
However the issue with rcctl start unbound still remains despite the
increase
of the ram on the vm
ok so
Den ons 24 okt. 2018 kl 20:48 skrev Carlos Aguilar :
> Then, when I execute the following command as unprivileged user sg:
> sg:/home/sg$mv /var/www/cgi-bin/my-site/posts/messages/*.txt /tmp
> I got the following error message:
>
> mv: /tmp/OneFile.txt: set owner/group: Operation not permitted
>
Update:
I noticed upon selecting the boot menu there were two ways to boot the usb
in the Mac's efi, I selected the one labled "windows". The computer has
never had windows installed and it's for booting the usb but I never saw
anything noting that this would happen. I selected it and instantly
25 matches
Mail list logo
