- Original Nachricht
Von: Fabian Raetz fabian.ra...@gmail.com
An: Carsten Kunze carsten.ku...@arcor.de
Datum: 03.08.2014 21:56
Betreff: Re: sshfs as non-root: fuse_mount: Permission d enied
The sysctl kern.usermount must be set to some nozero value.
You may want to take
I'll regroup. I don't have access to an OpenBSD system at the moment
but I'm trying to recall the readme and man page for ntfs-3g which also
uses fuse.
Using fuse which may lead to a privilege escalation, I think, ... and
that is why ntfs-3g has to be run as root and pass uid and gid options
I'll regroup. I don't have access to an OpenBSD system at the moment
but I'm trying to recall the readme and man page for ntfs-3g which also
uses fuse.
Using fuse which may lead to a privilege escalation, I think, ... and
that is why ntfs-3g has to be run as root and pass uid and gid
to be run as root and pass uid and gid
options.
I'm guessing that sshfs will be similar.
Fabian suggested to set kern.usermount to a non-zero value, now it
works
as expected. Maybe this could help ntfs-3g also, I don't know.
(Setting uid/gid is not a nice solution. But if it's necessary
On June 10, 2014 6:24:17 AM CEST, Miod Vallat m...@online.fr wrote:
http://www.openbsd.org/anoncvs.html shows the 'cvs update' command
being
run by root (# shell prompt), and I wouldn't expect any non-root
user
to have write permission to /usr/src anyway. So... why is doing the
cvs-update
On 2014-06-10, Alexander Hall alexan...@beard.se wrote:
On June 10, 2014 6:24:17 AM CEST, Miod Vallat m...@online.fr wrote:
http://www.openbsd.org/anoncvs.html shows the 'cvs update' command
being
run by root (# shell prompt), and I wouldn't expect any non-root
user
to have write permission
In message http://marc.info/?l=openbsd-miscm=140224659303522w=1,
Miod Vallat wrote (about an anoncvs update to /usr/src)
you should not run this command as root
http://www.openbsd.org/anoncvs.html shows the 'cvs update' command being
run by root (# shell prompt), and I wouldn't expect any non
On Mon, Jun 09, 2014 at 03:07:17PM -0700, Jonathan Thornburg wrote:
In message http://marc.info/?l=openbsd-miscm=140224659303522w=1,
Miod Vallat wrote (about an anoncvs update to /usr/src)
you should not run this command as root
http://www.openbsd.org/anoncvs.html shows the 'cvs update
On Mon, Jun 09, 2014 at 03:07:17PM -0700, Jonathan Thornburg wrote:
http://www.openbsd.org/anoncvs.html shows the 'cvs update'
command being run by root (# shell prompt)
One example (the latest one added) in the Using CVS to ... section
uses $, as do all the examples in the Example usages
http://www.openbsd.org/anoncvs.html shows the 'cvs update' command being
run by root (# shell prompt), and I wouldn't expect any non-root user
to have write permission to /usr/src anyway. So... why is doing the
cvs-update as root a bad idea?
Is this a kind of bad joke? Running anything
Denis Fondras wrote:
Hello all,
I am burning my last neurons with a behavior I can't explain. I wonder
why getaddrinfo() fails when called after chroot() with root user.
I have this piece of code :
...
error = getaddrinfo(rpki.liopen.eu, NULL, NULL, ai_out
On Wed, May 14, 2014 at 07:41:47PM +0200, Denis Fondras wrote:
After chroot, /etc/resolv.conf is no longer available.
Thank you very much Ted Vadim.
Other daemons like ntpd have a helper process that runs outside chroot
and does all of the DNS resolution for them.
Ok, I'll
Hello all,
I am burning my last neurons with a behavior I can't explain. I wonder
why getaddrinfo() fails when called after chroot() with root user.
I have this piece of code :
/*--- test.c ---*/
#include sys/types.h
#include stdio.h
#include sys/socket.h
#include netdb.h
#include pwd.h
int
On 05/14/14 18:57, Denis Fondras wrote:
Hello all,
I am burning my last neurons with a behavior I can't explain. I wonder
why getaddrinfo() fails when called after chroot() with root user.
I have this piece of code :
/*--- test.c ---*/
#include sys/types.h
#include stdio.h
#include
On Wed, May 14, 2014 at 18:57, Denis Fondras wrote:
Hello all,
I am burning my last neurons with a behavior I can't explain. I wonder
why getaddrinfo() fails when called after chroot() with root user.
After chroot, /etc/resolv.conf is no longer available.
If this an expected behavior, what
Le 14/05/2014 19:14, Peter J. Philipp a écrit :
I wonder if you're using the wrong function. There is gethostbyname for
forward lookups?
I read it was deprecated.
Denis
2014-05-14 20:57 GMT+04:00 Denis Fondras open...@ledeuns.net:
Hello all,
I am burning my last neurons with a behavior I can't explain. I wonder
why getaddrinfo() fails when called after chroot() with root user.
I have this piece of code :
/*--- test.c ---*/
#include sys/types.h
#include
After chroot, /etc/resolv.conf is no longer available.
Thank you very much Ted Vadim.
Other daemons like ntpd have a helper process that runs outside chroot
and does all of the DNS resolution for them.
Ok, I'll look on this side.
Thank you,
Denis
/No/Go boil my head in a cauldron brimming with rancid rhino rectal
fluid, while surrounded by little blue sexually aroused smurfs chanting,
Great is Willie Wonker of the Chocolate Factory Dynasty!!
Running security(8):
Checking root sh paths, umask values:
/etc/profile /root/.profile
Root
The umask is set in /etc/login.conf:
default:\
...
...
:umask=022:\
...
...
staff:\
...
...
:umask=027:\
...
...
Is this still a problem? (e.g. cron jobs)
- Forwarded message from Charlie Root r
I want to be able to log in as root by SSH with a specific IP address.
This is so rsync can log in to the server easily and backup many files
owned by many different users and groups. Rather than a script on the
server logging into the server with the backups with many files and
many different
ssh -lroot youriphere -p1157
-l ==login
-p == port number
On Mon, Sep 30, 2013 at 11:59 AM, John Tate j...@johntate.org wrote:
I want to be able to log in as root by SSH with a specific IP address.
This is so rsync can log in to the server easily and backup many files
owned by many
On Mon, Sep 30, 2013 at 8:29 AM, John Tate j...@johntate.org wrote:
I want to be able to log in as root by SSH with a specific IP address.
This is so rsync can log in to the server easily and backup many files
owned by many different users and groups. Rather than a script on the
server logging
On Mon, 30 Sep 2013, John Tate wrote:
I want to be able to log in as root by SSH with a specific IP address.
This is so rsync can log in to the server easily and backup many files
owned by many different users and groups. Rather than a script on the
server logging into the server
Le 2013-09-30 08:29, John Tate a écrit :
I want to be able to log in as root by SSH with a specific IP address.
This is so rsync can log in to the server easily and backup many files
owned by many different users and groups. Rather than a script on the
server logging into the server
oops. meant to send to list...
(this time with cheesy ASCII graphics which will probably get mauled by
most mail clients)
On 09/30/2013 02:29 AM, John Tate wrote:
I want to be able to log in as root by SSH with a specific IP address.
This is so rsync can log in to the server easily
Hi,
I have been running OpenBSD 4.9 on a Tyan S5160 for a couple years now
just fine. I backed up my data and did a fresh install of 5.3. The
install went flawlessly but after the install and the reboot, the system
boots but then panics when looking for the root device.
I have tried
On Fri, Jun 07, 2013 at 17:19, Aaron Martinez wrote:
I have a single sata hdd installed as my OS drive that shows up and sd1
during install that I install the OS onto and an areca 1210 4 port sata
raid card installed for storage that shows up as sd0 during install.
arc0 at pci2 dev 14
it
was asking for the root device and that worked as well.
Is there a way to make it so that I don't have to do this every time?
I put the successful boot with the -a option dmesg below.
Thanks again,
Aaron
OpenBSD/i386 BOOT 3.21
boot -a
booting hd0a:/bsd: 8425188+1102788 [52+382544+368841]=0x9cdb6c
Hi,
I have added a second hard drive in my virtual machine, as my root
partition is full. My idea was to add a new disk to the system, then
migrate the root partition to the new disk.
What I did so far :
- In recovery, add the second hard drive, fdisk to initialize it, then
disklabel to add
On Tue, May 14, 2013 at 11:08:49AM +0200, Adrien wrote:
Hi,
I have added a second hard drive in my virtual machine, as my root
partition is full. My idea was to add a new disk to the system, then
migrate the root partition to the new disk.
What I did so far :
- In recovery, add
that no
such file or directory. Seems my drive is good as during the early
bootstage I have hd0+ (my old hdd) and hd1+ (new hdd).
Can this be due to the fact my filesystem is currently read-only, as I have
no more space left on my root partition ?
2013/5/14 Otto Moerbeek o...@drijf.net
On Tue, May 14, 2013
as during the early
bootstage I have hd0+ (my old hdd) and hd1+ (new hdd).
Can this be due to the fact my filesystem is currently read-only, as I have
no more space left on my root partition ?
2013/5/14 Otto Moerbeek o...@drijf.net
On Tue, May 14, 2013 at 11:08:49AM +0200, Adrien
OK, so :
1. Added new hdd within my virtual machine.
2. Started virtual machine, initialized the disk with fdisk :
root@bsd:~# fdisk -i sd2
Do you wish to write new MBR and partition table? [n] y
Writing MBR at offset 0.
3. Added new slice with Disklabel
root@bsd:~# disklabel -E sd2
Label
On Tue, May 14, 2013 at 03:52:03PM +0200, Adrien wrote:
OK, so :
1. Added new hdd within my virtual machine.
2. Started virtual machine, initialized the disk with fdisk :
root@bsd:~# fdisk -i sd2
Do you wish to write new MBR and partition table? [n] y
Writing MBR at offset 0.
3
. Started virtual machine, initialized the disk with fdisk :
root@bsd:~# fdisk -i sd2
Do you wish to write new MBR and partition table? [n] y
Writing MBR at offset 0.
3. Added new slice with Disklabel
root@bsd:~# disklabel -E sd2
Label editor (enter '?' for help at any prompt)
p
FAQ 8.1 - I forgot my root password...
http://www.openbsd.org/faq/faq8.html#LostPW
...
re:
Mount the partitions. Both / and /usr will need to be mounted read-write.
Assuming they are on separate partitions (as they should be), the following
will work:
# fsck -p / mount -uw /
# fsck
On Apr 11, 2013, at 4:15 PM, f5b f...@163.com wrote:
FAQ 8.1 - I forgot my root password...
http://www.openbsd.org/faq/faq8.html#LostPW
...
re:
Mount the partitions. Both / and /usr will need to be mounted read-write.
Assuming they are on separate partitions (as they should
2013/4/11 f5b f...@163.com:
FAQ 8.1 - I forgot my root password...
http://www.openbsd.org/faq/faq8.html#LostPW
...
re:
Mount the partitions. Both / and /usr will need to be mounted read-write.
Assuming they are on separate partitions (as they should be), the following
will work
On Wed, Dec 26, 2012 at 10:16:09PM +0100, mhca12 wrote:
What's the status of the root partion-less full disk
encryption changes? Is it already good enough and
are there (semi-)official install images with it enabled?
You can create a crypto disk during or after installation (type !
at any
On Wed, Dec 26, 2012 at 10:25:27PM +0100, Stefan Sperling wrote:
On Wed, Dec 26, 2012 at 10:16:09PM +0100, mhca12 wrote:
What's the status of the root partion-less full disk
encryption changes? Is it already good enough and
are there (semi-)official install images with it enabled?
You
:54PM +0200, lilit-aibolit wrote:
11.03.2012 21:43, Chris Bennett P?P8QP5Q:
This started for me a while back.
Login as root, I can repeat older commands with up down arrows.
History command shows history.
su -l otheruser
Cannot use up down arrows to access history.
History
On Mon, Mar 12, 2012 at 01:03:54PM +0200, lilit-aibolit wrote:
11.03.2012 21:43, Chris Bennett P?P8QP5Q:
This started for me a while back.
Login as root, I can repeat older commands with up down arrows.
History command shows history.
su -l otheruser
Cannot use up down arrows to access
On 2012-03-11, Tobias Ulmer tobi...@tmux.org wrote:
On Sun, Mar 11, 2012 at 02:43:42PM -0500, Chris Bennett wrote:
This started for me a while back.
Login as root, I can repeat older commands with up down arrows.
History command shows history.
su -l otheruser
Cannot use up down arrows
On 2012-03-11, Chris Bennett ch...@bennettconstruction.us wrote:
On Sun, Mar 11, 2012 at 09:02:58PM +0100, Tobias Ulmer wrote:
You most likely set EDITOR to something containing vi. ksh parses that
and switches to vi mode. IMO it's a disgusting feature, but that
appears to be just me.
, 2012 at 02:43:42PM -0500, Chris Bennett wrote:
This started for me a while back.
Login as root, I can repeat older commands with up down arrows.
History command shows history.
su -l otheruser
Cannot use up down arrows to access history.
History command shows correct history.
You most
11.03.2012 21:43, Chris Bennett P?P8QP5Q:
This started for me a while back.
Login as root, I can repeat older commands with up down arrows.
History command shows history.
su -l otheruser
Cannot use up down arrows to access history.
History command shows correct history.
Login remotely
On Mon, Mar 12, 2012 at 10:09:13AM +, Stuart Henderson wrote:
I've wasted countless time because of this feature, it's probably
my no.1 annoyance with the OS. It used to be possible to set this
in a file sourced via ENV so it could be applied automatically,
but sudo now (rightly)
This started for me a while back.
Login as root, I can repeat older commands with up down arrows.
History command shows history.
su -l otheruser
Cannot use up down arrows to access history.
History command shows correct history.
Login remotely as otheruser.
Same problem.
Chris Bennett
On 03/11/12 20:43, Chris Bennett wrote:
This started for me a while back.
Login as root, I can repeat older commands with up down arrows.
History command shows history.
su -l otheruser
Cannot use up down arrows to access history.
History command shows correct history.
Login remotely
On Sun, Mar 11, 2012 at 12:43 PM, Chris Bennett
ch...@bennettconstruction.us wrote:
This started for me a while back.
Login as root, I can repeat older commands with up down arrows.
History command shows history.
su -l otheruser
Cannot use up down arrows to access history.
History command
On Sun, Mar 11, 2012 at 02:43:42PM -0500, Chris Bennett wrote:
This started for me a while back.
Login as root, I can repeat older commands with up down arrows.
History command shows history.
su -l otheruser
Cannot use up down arrows to access history.
History command shows correct
On Sun, Mar 11, 2012 at 3:32 PM, Tobias Ulmer tobi...@tmux.org wrote:
On Sun, Mar 11, 2012 at 02:43:42PM -0500, Chris Bennett wrote:
This started for me a while back.
Login as root, I can repeat older commands with up down arrows.
History command shows history.
su -l otheruser
Cannot use
On Sun, Mar 11, 2012 at 09:02:58PM +0100, Tobias Ulmer wrote:
You most likely set EDITOR to something containing vi. ksh parses that
and switches to vi mode. IMO it's a disgusting feature, but that
appears to be just me.
Wow, that is a disgusting pile of crap!
alias mutt='env EDITOR=vim
obvious step here...
Can you point out what is wrong?
The kernels are loaded from outside the softraid array (sd0a, or sd1a) by
the second stage bootloader. But the second stage bootloader is loaded
from
the array. So, assuming sd2 is your softraid array, and you have an sd2a
root partition
upgrade process be consistent through the standard
installer or should one always go to shell, make manual adjustments and
then run install?
The installer installs kernels into the root partition. You must copy them
to non-RAID partition(s) in order for the second stage bootloader to be
able
?
The installer installs kernels into the root partition. You must copy them
to non-RAID partition(s) in order for the second stage bootloader to be
able to load them. Using your example of a binary upgrade such as a
snapshot,
copy the ramdisk kernel to a non-RAID partition, boot it, conduct
On Tue, Dec 27, 2011 at 01:49:59AM +0100, Paolo Aglialoro wrote:
So this means that on sparc64 life would be way easier ;)
Thanks!
I never tested root-on-softraid on single-stage booting architectures. I
don't have any handy. You'll have to test that yourself!
. But looking
at the changelogs I see the bits that store boot info in softraid
metadata and dynamically figure out the root happened after the 5.0
freeze.
Something to look forward to in 5.1 :). Thanks again...
Why wait? I have two amd64 servers in production on -current
and all is humming along
stage bootloader. But the second stage bootloader is loaded from
the array. So, assuming sd2 is your softraid array, and you have an sd2a
root partition, reboot the install cd and try:
# mount /dev/sd2a /mnt
# cp -p /usr/mdec/boot /mnt/boot
# /usr/mdec/installboot -v /mnt/boot /usr/mdec/biosboot sd2
the softraid array (sd0a, or sd1a) by
the second stage bootloader. But the second stage bootloader is loaded from
the array. So, assuming sd2 is your softraid array, and you have an sd2a
root partition, reboot the install cd and try:
# mount /dev/sd2a /mnt
# cp -p /usr/mdec/boot /mnt/boot
# /usr/mdec
?
The kernels are loaded from outside the softraid array (sd0a, or sd1a) by
the second stage bootloader. But the second stage bootloader is loaded
from
the array. So, assuming sd2 is your softraid array, and you have an sd2a
root partition, reboot the install cd and try:
# mount /dev/sd2a /mnt
# cp
and dynamically figure out the root happened after the 5.0
freeze.
Something to look forward to in 5.1 :). Thanks again...
--
Paul B. Henson | (909) 979-6361 | http://www.csupomona.edu/~henson/
Operating Systems and Network Analyst | hen...@csupomona.edu
California State Polytechnic University
boot info in softraid
metadata and dynamically figure out the root happened after the 5.0
freeze.
Something to look forward to in 5.1 :). Thanks again...
Why wait? I have two amd64 servers in production on -current
and all is humming along magnificently. One is heavily loaded
by large image
On 2011-12-20, johnw johnw.m...@gmail.com wrote:
The aliases are not neccesary. I suspect root's shell is in vi mode.
Check with set -o
-Otto
Yes, i have this one in ~/.kshrc,
export EDITOR=vim.
delete this can solve the problem.
thank all.
If you still want to use vim (or any
=not_emacs
$ ls -al /usr/bin/not_emacs
lrwxr-xr-x 1 root wheel 2 Dec 21 11:03 /usr/bin/not_emacs - vi
'emacs' and use that in EDITOR instead..
Or:
EDITOR=vi
VISUAL=not_emacs
$ ls -al /usr/bin/not_emacs
lrwxr-xr-x 1 root wheel 2 Dec 21 11:03 /usr/bin/not_emacs - vi
Isn't set -o emacs at the end of ~/.kshrc enough? It seems to be (at
least with my somewhat patched ksh).
--
Alexander
of the shell, create a symlink containing
the string 'emacs' and use that in EDITOR instead..
Or:
EDITOR=vi
VISUAL=not_emacs
$ ls -al /usr/bin/not_emacs
lrwxr-xr-x 1 root wheel 2 Dec 21 11:03 /usr/bin/not_emacs - vi
Isn't set -o emacs at the end of ~/.kshrc enough?
It's
On 21.12.2011 23:36, Stuart Henderson wrote:
On 2011-12-21, Alexander Polakov polac...@gmail.com wrote:
Isn't set -o emacs at the end of ~/.kshrc enough?
It's not passed through if you do e.g. sudo -s
Which is why you should use `sudo -i'.
--
Fred -- http://tar-jx.bz
I've been running openbsd 4.6 for a couple years now with root on
softraid, booting off a CF card with a kernel compiled to hardcode
root/swap on sd0.
I read about official support for root on softraid:
http://www.undeadly.org/cgi?action=articlesid=20111002154251
and got the impression it would
Paul B. Henson henson at acm.org writes:
I've been running openbsd 4.6 for a couple years now with root on
softraid, booting off a CF card with a kernel compiled to hardcode
root/swap on sd0.
I read about official support for root on softraid
Anyway, just to clarify my understanding
Josh Grosse josh at jggimi.homeip.net writes:
Paul B. Henson henson at acm.org writes:
I've been running openbsd 4.6 for a couple years now with root on
softraid, booting off a CF card with a kernel compiled to hardcode
root/swap on sd0.
I read about official support for root
my system is i386/current, i do not know why and when,
today, i noticed i can not use the up key to last command at root anymore.
i can use the up key to last command at non root user,
both is use ksh.
any idea?
please help and thank you.
Hi
add the following
lines to the bottom of your .kshrc file in your /root directory:
set -o emacs
alias __A=$(print '\0020') # ^P = up = previous command
alias __B=$(print '\0016') # ^N = down = next command
alias __C=$(print '\0006') # ^F = right = forward a character
alias __D=$(print '\0002
On Tue, Dec 20, 2011 at 03:44:11PM +0100, Francois Pussault wrote:
Hi
add the following
lines to the bottom of your .kshrc file in your /root directory:
set -o emacs
alias __A=$(print '\0020') # ^P = up = previous command
alias __B=$(print '\0016') # ^N = down = next command
alias __C
On 2011-11-06 21.42, David Vasek wrote:
On Sun, 6 Nov 2011, Benny Lofgren wrote:
On 2011-11-06 18.00, Bambero wrote:
Thanks, but without skip=1 dd will copy partition table and mbr too
(first block 521b).
So it may damage my partition table on second machine. I'm I wrong ?
No, you will not
On Mon, Nov 07, 2011 at 03:54:14PM +0100, Benny Lofgren wrote:
On 2011-11-06 21.42, David Vasek wrote:
On Sun, 6 Nov 2011, Benny Lofgren wrote:
On 2011-11-06 18.00, Bambero wrote:
Thanks, but without skip=1 dd will copy partition table and mbr too
(first block 521b).
So it may damage
On Mon, Nov 07, 2011 at 04:03:37PM +0100, Otto Moerbeek wrote:
On Mon, Nov 07, 2011 at 03:54:14PM +0100, Benny Lofgren wrote:
On 2011-11-06 21.42, David Vasek wrote:
On Sun, 6 Nov 2011, Benny Lofgren wrote:
On 2011-11-06 18.00, Bambero wrote:
Thanks, but without skip=1 dd will copy
/wd0a bs=32m | gzip root.img.gz]
and
dd if=root.img of=/dev/wd0a bs=32m [decompression: gzip -d -c
root.img.gz | dd of=/dev/wd0a bs=32m]
And yes, you can ommit additional values.
Dnia piD , 4 lis 2011, 17:43:28 Bambero pisze:
Hello
I want to copy my root partition to another with dd
:43:28 Bambero pisze:
Hello
I want to copy my root partition to another with dd without ssh. Is
this correct:
1. On first machine:
dd if=/dev/rwd0a of=root.img bs=16b skip=1 conv=noerror
2. On second machine:
dd if=root.img of=/dev/rwd0a bs=16b seek=1
May/should I ommit seek, skip, conv
)
device.
And, and I hope this goes without saying, DON'T DO THIS ON A MOUNTED DEVICE.
So, skip the skip. Just do the following:
On the source machine:
Boot from something other than your root disk, or boot into single user
mode and remount root read-only. Then:
dd if=/dev/rwd0a of=/tmp
device when doing this, use the raw (character)
device.
And, and I hope this goes without saying, DON'T DO THIS ON A MOUNTED DEVICE.
So, skip the skip. Just do the following:
On the source machine:
Boot from something other than your root disk, or boot into single user
mode and remount root read
Hello
I want to copy my root partition to another with dd without ssh. Is
this correct:
1. On first machine:
dd if=/dev/rwd0a of=root.img bs=16b skip=1 conv=noerror
2. On second machine:
dd if=root.img of=/dev/rwd0a bs=16b seek=1
May/should I ommit seek, skip, conv, bs parameters ?
Regards
pisze:
Hello
I want to copy my root partition to another with dd without ssh. Is
this correct:
1. On first machine:
dd if=/dev/rwd0a of=root.img bs=16b skip=1 conv=noerror
2. On second machine:
dd if=root.img of=/dev/rwd0a bs=16b seek=1
May/should I ommit seek, skip, conv, bs parameters
Bambero bambero at gmail.com writes:
Hello
I want to copy my root partition to another with dd without ssh. Is
this correct:
1. On first machine:
dd if=/dev/rwd0a of=root.img bs=16b skip=1 conv=noerror
2. On second machine:
dd if=root.img of=/dev/rwd0a bs=16b seek=1
May/should I
On Fri Nov 4 2011 17:43, Bambero wrote:
Hello
I want to copy my root partition to another with dd without ssh. Is
this correct:
1. On first machine:
dd if=/dev/rwd0a of=root.img bs=16b skip=1 conv=noerror
2. On second machine:
dd if=root.img of=/dev/rwd0a bs=16b seek=1
May/should
'unknown serial'
--
Henning Brauer, h...@bsws.de, henn...@openbsd.org
BS Web Services, http://bsws.de, Full-Service ISP
Secure Hosting, Mail and DNS Services. Dedicated Servers, Root to Fully Managed
Henning Brauer Consulting, http://henningbrauer.com/
I saw the commits for this a few weeks past and thought
I'd give it a go.
I have successfully built a RAID1 on two ~500GB physical
drives. The root filesystem is on partition a.
I shutdown the machine and replaced one of the disks with
a fresh unused one to test the rebuild process.
All seems
On Fri, Oct 28, 2011 at 11:30:10PM -0700, Raymond Lillard wrote:
...All seems to have went well, it is still rebuilding, but
in checking status I see no serial in the status output.
Should the serial number contain the duid? Is this
expected or did I miss something? Maybe the serial
relates
Hello,
I tried to boot via `bsd -a' and then asked for root device
I wrote DUID of accessible disk but no success.
root device (default sd0a): fba123e4bd29707a.a
use one of: exit em0 iwn0 sd0[a-p] cd0[a-p] sd1[a-p] sd2[a-p]
I still do not understand meaning of this commit, sorry
I don't know C
You can mount with duid in fstab but I can't find a way to change root
device to a duid in the boot manual. You must use a device found in
/dev/
http://www.openbsd.org/cgi-bin/man.cgi?query=bootsektion=8arch=i386apropos=0manpath=OpenBSD+Current
// Johan
2011/10/9 Jiri B ji...@wolfman.devio.us
It looks it is already possible to have duid for root device:
http://www.openbsd.org/cgi-bin/cvsweb/src/sys/kern/subr_disk.c#rev1.120
I will test during weekend.
jirib
On Thursday 06 October 2011, Jiri B wrote:
would be possible to tell kernel via `bsd -a' or with extended
boot.conf configuration capabilities to use a root device defined
with DUID?
Short answer, no.
My intend is to boot from an external usb stick and to have root device
in the box
On Fri, Oct 07, 2011 at 11:49:17PM +1100, Joel Sing wrote:
On Thursday 06 October 2011, Jiri B wrote:
would be possible to tell kernel via `bsd -a' or with extended
boot.conf configuration capabilities to use a root device defined
with DUID?
Short answer, no.
So what is this commit
Hello,
would be possible to tell kernel via `bsd -a' or with extended
boot.conf configuration capabilities to use a root device defined
with DUID?
My intend is to boot from an external usb stick and to have root device
in the box configured with softraid and keydisk.
jirib
-a' or with extended
boot.conf configuration capabilities to use a root device defined
with DUID?
My intend is to boot from an external usb stick and to have root device
in the box configured with softraid and keydisk.
jirib
boot.conf configuration capabilities to use a root device defined
with DUID?
My intend is to boot from an external usb stick and to have root device
in the box configured with softraid and keydisk.
jirib
of the tap or tun device
you are using to the user you want to bring up the tunnel you can
avoid root.
G
On Fri, Aug 12, 2011 at 5:40 AM, Michael W. Lucas
mwlu...@blackhelicopters.org wrote:
Hi,
I'm trying to get a SSH VPN working between a 4.9 i386 and a recent
5.0 amd64 snapshot
Pretty sure if you change the owner / group of the tap or tun device
you are using to the user you want to bring up the tunnel you can
avoid root.
G
On Fri, Aug 12, 2011 at 5:40 AM, Michael W. Lucas
mwlu...@blackhelicopters.org wrote:
Hi,
I'm trying to get a SSH VPN working between a 4.9 i386
Hi,
I'm trying to get a SSH VPN working between a 4.9 i386 and a recent
5.0 amd64 snapshot (with the MP#49 kernel).
The tunnel works fine if I SSH in as root. My guts really protest at
enabling remote root logins, however. Yes, I can limit the access with
a Match statement.
Surely I can change
301 - 400 of 844 matches
Mail list logo
