Re: Minor setup issues
On 07/15/15 21:50, Dan LaBell wrote:
On Jul 15, 2015, at 5:29 PM, William A. Mahaffey III wrote:
On 07/15/15 12:24, Greg Troxel wrote:
William A. Mahaffey III w...@hiwaay.net writes:
Following recommendations I now login to root by su, rather than
directly at the console. When I do, none of my aliases get set
filename completion using the tab key doesn't work.
man su, see -m
install and then man sudo, see -E
I use sudo -E $(SHELL), more or less, to get a shell that's just like
mine, but with uid 0.
I think this has to be a typo, command substitution is not warranted
$SHELL or ${SHELL} is what's meant, also I think, you just try '-l'
w/ su , or sue tack el. and not Install, [and configure], and then
man sudo
You're the only admin for this system? Sudo would have use your user
login password to get root, not root's password.
Yes, just me, myself I
Also, I'd recommend against su -m leaving environment unchanged.
I'd say remember that exists, to rescue a broken .profile etc, but avoid
habitual use, and just change the directory, after becoming root.
You want your profile read, right? Not changes to PATH, etc done at
command line?
Yes to both of the last questions. I went to 'su -' everything mostly
works. I also recall from last year, messing around w/ NetBSD on my
RPi-B+ time server, that rxvt (what I usually use on this box, FreeBSD
9.3R-p13) has some issues when ssh-ing into NetBSD. When I switch to an
xterm, everything behaves much better, which I am now doing. Thanks :-).
--
William A. Mahaffey III
--
The M1 Garand is without doubt the finest implement of war
ever devised by man.
-- Gen. George S. Patton Jr.
Re: Minor setup issues
On Jul 15, 2015, at 5:29 PM, William A. Mahaffey III wrote:
On 07/15/15 12:24, Greg Troxel wrote:
William A. Mahaffey III w...@hiwaay.net writes:
Following recommendations I now login to root by su, rather than
directly at the console. When I do, none of my aliases get set
filename completion using the tab key doesn't work.
man su, see -m
install and then man sudo, see -E
I use sudo -E $(SHELL), more or less, to get a shell that's just
like
mine, but with uid 0.
I think this has to be a typo, command substitution is not warranted
$SHELL or ${SHELL} is what's meant, also I think, you just try '-l'
w/ su , or sue tack el. and not Install, [and configure], and then
man sudo
You're the only admin for this system? Sudo would have use your user
login password to get root, not root's password.
Also, I'd recommend against su -m leaving environment unchanged.
I'd say remember that exists, to rescue a broken .profile etc, but avoid
habitual use, and just change the directory, after becoming root.
You want your profile read, right? Not changes to PATH, etc done at
command line?
Re: more pilot error
On 07/15/15 19:39, Brett Lymn wrote: On Wed, Jul 15, 2015 at 04:32:45PM -0453, William A. Mahaffey III wrote: dump device configured. I have 6 swap partitions: That seems a bit excessive - the days of 2 * physical RAM plus a bit for swap allocation has not been needed for quite some time. I guess in the general scheme of things the amount of storage you have allocated for swap is not much but, still, it really doesn't need to be that much IMHO. Also, why are they not a raid? At the moment if you lose a disk that hosts the swap chances are the machine will go down. Good questions. I have always heard that you get the best swasp performance w/ the raw kernel driver (under SGI linux), rather than swapping to a RAID device. I have another box (Linux, FC14 64-bit) that swaps to a RAID device, it takes several min. to page in a few hundred MB of paged-out-VM. That may be a linux only issue, but it is consistent w/ my historical recollections. I have 96 GB of swap 64 GB of RAM. When fully operational the box may spend some time doing large CFD calculations which exhaust that amount of RAM (pretty easy to do, actually). The process should be able to continue, albeit more slowly, which I will need. The swap devices are 1 slice on each of 6 HDD's, for max parallelism hopefully max performance. As soon as this machine is fully up running, I am going to redo the linux box to get rid of swapping on a raid device ( allocate disk-space more usefully), will be going back to swapping on raw partitions due to crappy performance of swap-on-raid on that box. The HDD's are brand new 2.5 drives, which I have had good luck with historically, so I am hoping for more of the same WRT HDD reliability vis-a-vis swapping ( other data partitions). -- William A. Mahaffey III -- The M1 Garand is without doubt the finest implement of war ever devised by man. -- Gen. George S. Patton Jr.
Re: Minor setup issues
William A. Mahaffey III w...@hiwaay.net writes: Following recommendations I now login to root by su, rather than directly at the console. When I do, none of my aliases get set filename completion using the tab key doesn't work. man su, see -m install and then man sudo, see -E I use sudo -E $(SHELL), more or less, to get a shell that's just like mine, but with uid 0. pgpz45iK8W1ZN.pgp Description: PGP signature
Re: Minor setup issues
On Wed, 15 Jul 2015 11:18:48 + William A. Mahaffey III wrote: I have my shiny new NetBSD 6.1.5 server up running, all RAID devices working AOK, several reboots completed, swap configured, etc. All is well except for a few pilot errors. Following recommendations I now login to root by su, rather than directly at the console. When I do, none of my aliases get set filename completion using the tab key doesn't work. This isn't huge, but is irritating. You're probably using sh. If so you will need the following options in .shrc: set -o emacs set -o tabcomplete NetBSD also has ksh which is, as far as I know, pdksh under the hood. A better korn shell clone is mksh, available in pkgsrc. All is well logging in at the console, although the screen is limited to 80 chars/line 25 lines, which restricts what you can see in crowded directories. I am ssh-ing in as my regular user, BTW, that probably makes a difference. When fully operational, there will be no kbd/mouse/monitor hooked up, so I do need to get this either fixed or understood. I found the best way to deal with the console is to specify a vesa mode in /boot.cfg. When booting, choose 5 to drop to a prompt and type vesa list. This will give you a list of vesa modes supported by your hardware. For example, 0x14b. You then type vesa 0x14b and then boot. You can then add your chosen mode to /boot.cfg as follows: menu=Boot normally:rndseed /var/db/entropy-file;vesa 0x14b;boot netbsd -- Gerard Lally
more pilot error
I am having issues getting NFS server client to work on my NetBSD 6.1.5 server: I see the following in the end of my messages file: Jul 15 18:53:21 4256EE1 /netbsd: boot device: raid0 Jul 15 18:53:21 4256EE1 /netbsd: root on raid0a dumps on raid0b Jul 15 18:53:21 4256EE1 /netbsd: root file system type: ffs Jul 15 18:53:21 4256EE1 /netbsd: wsdisplay0: screen 1 added (80x25, vt100 emulation) Jul 15 18:53:21 4256EE1 /netbsd: wsdisplay0: screen 2 added (80x25, vt100 emulation) Jul 15 18:53:21 4256EE1 /netbsd: wsdisplay0: screen 3 added (80x25, vt100 emulation) Jul 15 18:53:21 4256EE1 /netbsd: wsdisplay0: screen 4 added (80x25, vt100 emulation) Jul 15 18:53:22 4256EE1 root: /etc/rc: WARNING: $rpcbind is not enabled. Jul 15 18:53:22 4256EE1 root: /etc/rc: WARNING: /etc/exports is not readable. Jul 15 18:53:22 4256EE1 root: /etc/rc: WARNING: $rpcbind is not enabled. Jul 15 18:53:22 4256EE1 savecore: /dev/rraid0b: Device not configured Jul 15 18:53:22 4256EE1 timed[317]: slave to rpi Jul 15 10:57:37 4256EE1 timed[317]: date changed by rpi from Wed Jul 15 18:53:22 2015 Jul 15 11:00:01 4256EE1 syslogd[159]: restart 2 (unrelated) issues, but I would like to get both resolved. I have no dump device configured. I have 6 swap partitions: 4256EE1 # pstat -hs Device Size UsedAvail Capacity Priority /dev/wd0e16G 0B 16G 0%0 /dev/wd1e16G 0B 16G 0%0 /dev/wd2e16G 0B 16G 0%0 /dev/wd3e16G 0B 16G 0%0 /dev/wd4e16G 0B 16G 0%0 /dev/wd5e16G 0B 16G 0%0 Total96G 0B 96G 0% 4256EE1 # cat fstab # NetBSD /targetroot/etc/fstab # See /usr/share/examples/fstab/ for more examples. /dev/raid0a / ffs rw 1 1 /dev/raid1a /usrffs rw 1 2 /dev/wd0e noneswapsw 0 0 /dev/wd1e noneswapsw 0 0 /dev/wd2e noneswapsw 0 0 /dev/wd3e noneswapsw 0 0 /dev/wd4e noneswapsw 0 0 /dev/wd5e noneswapsw 0 0 /dev/dk0/home ffs rw,log 1 3 kernfs /kern kernfs rw ptyfs /dev/ptsptyfs rw procfs /proc procfs rw /dev/cd0a /cdrom cd9660 ro,noauto /dev/sd0a /media/sd ufs rw,noauto 4256EE1 # Is there a mount flag I can use to specify a dump device (preferably 1 of the swap partitions) ? Also, I presume nfsd *can* work w/o rpcbind running, but I can't seem to locate how to do that in the man pages. Any clues there appreciated. I am on a LAN, this is *not* a public server, so only mount requests from other LAN boxen will be processed. I (think I) configured everything as needed in my rc.conf file: 4256EE1 # cat rc.conf # $NetBSD: rc.conf,v 1.96 2000/10/14 17:01:29 wiz Exp $ # # see rc.conf(5) for more information. # # Use program=YES to enable program, NO to disable it. program_flags are # passed to the program on the command line. # # Load the defaults in from /etc/defaults/rc.conf (if it's readable). # These can be overridden below. # if [ -r /etc/defaults/rc.conf ]; then . /etc/defaults/rc.conf fi # If this is not set to YES, the system will drop into single-user mode. # rc_configured=YES # Add local overrides below # hostname=4256EE1.CFD.COM defaultroute=192.168.0.254 sshd=YES timed=YES wscons=YES # NFS daemons and parameters. # mountd=YES mountd_flags= # NFS mount requests daemon nfs_client=YES # enable client daemons nfs_server=YES # enable server daemons lockd=YES lockd_flags= statd=YES statd_flags= amd=YES 4256EE1 # but the service doesn't start. More pilot error, most assuredly, but any clues appreciated. TIA have a good one. -- William A. Mahaffey III -- The M1 Garand is without doubt the finest implement of war ever devised by man. -- Gen. George S. Patton Jr.
Re: more pilot error
On Wed, Jul 15, 2015 at 04:32:45PM -0453, William A. Mahaffey III wrote: dump device configured. I have 6 swap partitions: That seems a bit excessive - the days of 2 * physical RAM plus a bit for swap allocation has not been needed for quite some time. I guess in the general scheme of things the amount of storage you have allocated for swap is not much but, still, it really doesn't need to be that much IMHO. Also, why are they not a raid? At the moment if you lose a disk that hosts the swap chances are the machine will go down. -- Brett Lymn
Re: more pilot error
On 07/15/15 17:00, Greg Troxel wrote: rpcbind is used to translate service names to ports. Why do you not want to run it? Before anything else, turn it on and reboot and only when it works with try without. Very well, I enabled it in my rc.conf file did a 'rc.d/nfsd start' I now get the following line in my messages file: Jul 15 19:30:12 4256EE1 nfsd[981]: can't register with udp portmap The man page is mum about this, as (mostly) is Google. Any help appreciated. -- William A. Mahaffey III -- The M1 Garand is without doubt the finest implement of war ever devised by man. -- Gen. George S. Patton Jr.
Re: Minor setup issues
On 07/15/15 12:24, Greg Troxel wrote: William A. Mahaffey III w...@hiwaay.net writes: Following recommendations I now login to root by su, rather than directly at the console. When I do, none of my aliases get set filename completion using the tab key doesn't work. man su, see -m install and then man sudo, see -E I use sudo -E $(SHELL), more or less, to get a shell that's just like mine, but with uid 0. What is the PKG_PATH for sudo, I have several commented out, which do I use ? 4256EE1 # uname -a NetBSD 4256EE1.CFD.COM 6.1.5 NetBSD 6.1.5 (GENERIC) amd64 4256EE1 # -- William A. Mahaffey III -- The M1 Garand is without doubt the finest implement of war ever devised by man. -- Gen. George S. Patton Jr.
Re: more pilot error
rpcbind is used to translate service names to ports. Why do you not want to run it? Before anything else, turn it on and reboot and only when it works with try without. pgpFG5HvOqJQ0.pgp Description: PGP signature
Re: Prepping to install: a digression
On 07/14/15 18:12, Robert Elz wrote: Date:Mon, 13 Jul 2015 21:57:46 -0453 From:William A. Mahaffey III w...@hiwaay.net Message-ID: 55a47933.1020...@hiwaay.net | Hm I *think* that's where I am now, from earlier today a few | days ago (from boot attempt from disks, *not* USB): Sorry, have not been looking at mail for (almost) 24 hours... And yes, you are there now. The last I saw you reported you were failing to boot at all, obviously that has been fixed, and I missed it. | Am I looking for the word 'autoconfigure' explicitly ? No, just the messages where all the hardware is listed. The boot device (etc) lines you showed appear right at (or near) the end of the autoconfig process. Since you're at that stage, do what Christos suggested, boot from the USB, and do the raidctl -A softroot raid0 (or if the system you're using is old enough that it doesn't recognise softroot then use just root) You already tested that what's on the root partition seems to be all OK, so with this, at the very least, you should get to the state where you can get to single user mode, even if there's still something not configured correctly that prevents multi-user mode working correctly. Also, to answer a later message ... the boot time messages do get saved to a file - but for that to happen, the filesystem needs to exist first, and for you that hasn't happened (as far as the kernel is concerned) yet. Until after you have a mounted root filesystem there is nowhere available to put a file, so all that data is just buffered in RAM, waiting for later to get written out - that happens as part of the later boot process. But it doesn't matter, aside from the boot time keyboard problem, I suspect everything will work now, or be very close to it. kre Well, I screwed up my courage, did the 'raidctl -A root raid0' rebooted it worked :-) *Hray* Much setup to do, but I think I am off to the races. Thanks to the list for all the help. I will have more questions no doubt, but I am up running now :-) I'd still like to figure out what was going wrong before, but that can wait for now. Thanks again. -- William A. Mahaffey III -- The M1 Garand is without doubt the finest implement of war ever devised by man. -- Gen. George S. Patton Jr.
Minor setup issues
I have my shiny new NetBSD 6.1.5 server up running, all RAID devices working AOK, several reboots completed, swap configured, etc. All is well except for a few pilot errors. Following recommendations I now login to root by su, rather than directly at the console. When I do, none of my aliases get set filename completion using the tab key doesn't work. This isn't huge, but is irritating. All is well logging in at the console, although the screen is limited to 80 chars/line 25 lines, which restricts what you can see in crowded directories. I am ssh-ing in as my regular user, BTW, that probably makes a difference. When fully operational, there will be no kbd/mouse/monitor hooked up, so I do need to get this either fixed or understood. TIA have a good one. -- William A. Mahaffey III -- The M1 Garand is without doubt the finest implement of war ever devised by man. -- Gen. George S. Patton Jr.
