how to do a custom install?
due to strange disk problems i was down for around 30 hours. i am currently wiping dos/win off in favor of 7.2-R and i have a question about doing a custom install that would let me slice the drive into more that four pieces. i am building, by default, /, /var SWAP, and /usr it has been years since my custom install where [[*some*]] technique let me slice something like, say, /, /var, /tmp, /usr/local/ SWAP, and /usr anybody remember what keys to hit in the installation procedure? tia, gary -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org The 7.31a release of Jottings: http://jottings.thought.org/index.php ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
diskless - NFS root mount problem
Hi,
I'm trying to setup diskless operation between my FreeBSD desktop (server) and
my laptop (client)
I have NFS_ROOT and all other necessary options compiled into my kernel, I have
this in /etc/exports:
==
/ -ro -maproot=root -alldirs 192.168.0.3
/usr -ro -alldirs 192.168.0.3
==
and this in dhcpd.conf
==
subnet 192.168.0.0 netmask 255.255.255.0 {
use-host-decl-names on;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.0.255;
option routers 192.168.0.1;
host laptop {
hardware ethernet 00:1E:68:45:0D:98;
fixed-address 192.168.0.3;
filename pxeboot;
option root-path 192.168.0.1:/;
}
==
when I attempt to (diskless) boot the laptop - stage one and two of the boot
process are fine...actually stage tree which is the kernel is also fine...the
kernel boots and starts bringing the system up...however it's unable to mount
the NFS root for some reason and the system freezes here:
==
...
...
Trying to mount root from ufs:/dev/ad4s1a
Trying to mount root from nfs:
NFS ROOT: 192.168.0.1:/
nfs send error 13 for server 192.168.0.1:/
bge0: link state changed to DOWN
bge0: link state changed to UP
==
I think error 13 means attempt to write on read-only mounted NFS...but it does
not make sense, does it?
do you have any ideas what could be the problem?
thanks
-
Вижте водещите новини от Vesti.bg!
http://www.vesti.bg
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: how to do a custom install?
-Original Message- From: Gary Kline Sent: Sun 15/11/2009 8:03 PM due to strange disk problems i was down for around 30 hours. i am currently wiping dos/win off in favor of 7.2-R and i have a question about doing a custom install that would let me slice the drive into more that four pieces. i am building, by default, /, /var SWAP, and /usr it has been years since my custom install where [[*some*]] technique let me slice something like, say, /, /var, /tmp, /usr/local/ SWAP, and /usr anybody remember what keys to hit in the installation procedure? tia, gary I can't say that I remember the keystrokes, but you can have multiple disk slices (aka Windows/DOS partitions) and within each slice, multiple BSD partitions (IIRC up to 8). I have mine partitioned into (generally) / - 1GB swap - 2x - 4x RAM /tmp - 4GB /var - 20GB /usr - 40% /backup - remainder I use the whole disk for BSD (single slice) and create the partitions as whatever size suits. Dave. -- David Rawling PD Consulting And Security Email: d...@pdconsec.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how to do a custom install?
Gary Kline wrote: due to strange disk problems i was down for around 30 hours. i am currently wiping dos/win off in favor of 7.2-R and i have a question about doing a custom install that would let me slice the drive into more that four pieces. i am building, by default, /, /var SWAP, and /usr it has been years since my custom install where [[*some*]] technique let me slice something like, say, /, /var, /tmp, /usr/local/ SWAP, and /usr anybody remember what keys to hit in the installation procedure? tia, gary Not sure about the terminology in use here. The old standard was to create one, or more, slice(s) and then partition with bsdlabel. In the sysinstall step for this it will run fdisk. Note that playing by the $MS standard the normal maximum number of slices would be 4, e.g. aka primary partitions in the Dos/Windows world. Fdisk makes slices. An example of a slice on an IDE drive would be ad0s1. After the fdisk step would next come bsdlabel. This is the step that creates partitions within the slice previously made with fdisk. Note the difference in terminology: what Dos/Windows refers to as a primary partition in the Unix world this is a slice. Partitions are created within a slice with bsdlabel. On the sysinstall Custom menu these two options are one above the other, e.g. Fdisk and Label. Select the Fdisk and create a slice, exit fdisk returning to sysinstall and proceed to select the Label menu option to bring up bsdlabel. (IIRC also called disklabel.) An example of a partition would be ad0s1a, ad0s1b for swap, ad0s1c is a reserved wrapper entity, ad0s1d, e, f, g. Usually ad0s1a will be your root, b will be swap, d might be /usr, e might be /var. etc. In the bsdlabel utility there is the option to choose both the partition type and size as well as it's mount point. It is actually possible to have more than 4 slices even when playing by the $MS Dos/Windows standard. Fdisk will allow for the creation of what on Dos are called extended partitions. The numbering for these starts at 5. You won't be able to boot from them and from a *Nix point of view are semi useless except within the context of Dos/Win compatibility. If this is just going to be a FreeBSD machine no need for the so-called extended partition of the Dos/Win world. Just create a slice [fisk], and break that up into partitions [bsdlabel]. If everything goes according to plan after Fdisk, Label, Return to previous menu, etc, at some point later on (IIRC after choosing packaging distributions) sysinstall will later perform the actions you configure in these preparatory steps. For reference peruse the Handbook; it's probably written clearer than I can accomplish. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: rc.subr patch to set FIB to demon
Коньков Евгений wrote:
Hello, .
Link to news:
http://www.kes.net.ua/softdev/fib_patch.html
rc.subr.patch
-
2c2
# $FreeBSD: src/etc/rc.subr,v 1.77.2.1.2.1 2008/11/25 02:59:29 kensmith Exp $
---
# $FreeBSD: src/etc/rc.subr,v 1.77.2.1 2008/05/12 07:29:03 mtm Exp $
605d604
664a664,669
_fib=
if [ ${name}_fib ]; then
eval _fib=\$${name}_fib
_fib=/usr/sbin/setfib $_fib
fi
670c675
$_chroot $command $rc_flags $command_args
---
$_chroot $_fib $command $rc_flags $command_args
674c679
$command $rc_flags $command_args
---
$_fib $command $rc_flags $command_args
Interesting. I see you submitted this as a PR back in March, but there
has been no activity other than to assign it to -net. Perhaps mailing
the freebsd...@... list might raise some interest.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW
signature.asc
Description: OpenPGP digital signature
Re: how to do a custom install?
On Sun, Nov 15, 2009 at 08:59:32PM +1100, David Rawling wrote: -Original Message- From: Gary Kline Sent: Sun 15/11/2009 8:03 PM due to strange disk problems i was down for around 30 hours. i am currently wiping dos/win off in favor of 7.2-R and i have a question about doing a custom install that would let me slice the drive into more that four pieces. You probably only need one slice (which MS calls a primary partition) but, you probably want to subdivide the slice in to FreeBSD partitions. i am building, by default, /, /var SWAP, and /usr it has been years since my custom install where [[*some*]] technique let me slice something like, say, Again, note the difference between slice and partition in FreeBSD. Slices are identified by numbers 1..4 and are the primary division. Partitions are subdivisions of a slice and are identified by letters a..h with 'c' reserved for the system to use. Then, you create mount points which are really directories with names such as / and /var and /usr and mount those drive-slice-partitions to the mount points. Swap is a special type that does not get mounted. jerry /, /var, /tmp, /usr/local/ SWAP, and /usr anybody remember what keys to hit in the installation procedure? tia, gary I can't say that I remember the keystrokes, but you can have multiple disk slices (aka Windows/DOS partitions) and within each slice, multiple BSD partitions (IIRC up to 8). I have mine partitioned into (generally) / - 1GB swap - 2x - 4x RAM /tmp - 4GB /var - 20GB /usr - 40% /backup - remainder I use the whole disk for BSD (single slice) and create the partitions as whatever size suits. Dave. -- David Rawling PD Consulting And Security Email: d...@pdconsec.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Produce identical packages for checksum comparison?
b. f. wrote: Chris wrote: I'm also thinking of building a simple checksum database to track what actually changes and what my options were when I compiled it. It would allow me to better make regression decisions. I could also be free to delete packages and know if I recompile it later that it was the exact same package with the exact same options. Very simple script to do that. Also if say there was an option when compiling ports to produce files with specific time/dates it would be helpful in pinpointing which of my port branches a specific file came from. The elusive reproducible build. Many people are interested in doing this, and it's not as easy as it seems. Even if you edited your filesystem or archives to change the timestamps of package files, the I think that could be accomplished though the port makefiles. toolchain used to create the binary files in packages often injects random seeds, timestamps, file paths, uid/gid information, etc. that I can understand file paths with debug info. Timestamps? Ok sure for a timestamp file being generated during a make that auto increments version numbers. What would change about uid/gid? I can't imagine why that might be in the binaries. As far as tar a simple utility could capture all the owner and group info into a text file as strings and set files to neutral values for uid/gid. A hack for the fact that packages are using tar files. Why would the build tools be injecting random numbers into binaries? I'll look into it. creates differences from one build to the next. You may have to hack several base system utilities, and then directly compare the checksums of binaries in archives after unpacking, or use a more intelligent comparison. See, for instance, one Japanese developer's attempt to do this in NetBSD in order to create better quality control for a commercial product: http://mail-index.netbsd.org/tech-toolchain/2009/02/17/msg000577.html Your description of your system's problems sounds bad. I think you should concentrate on fixing those first. What can I say? I multitask. If I concentrated on one problem at a time I would never get anything done. For my systems problem I think I'm going to have to either abandon jails or maybe try nfs instead of nullfs. Otherwise I'll have to learn the kernel code and how to debug the Freebsd kernel. Thanks for the confirmation that I'm not the only one to think about it and the link. Enjoy the day. Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
weird save-entropy behaviour
Greetings. Yesterday, i noticed a very weird behaviour on my computer (which is running 8.0-RC3 btw. The shells were not responding and the load was insane, and constantly going up. At the time i managed to lock myself out, the load was 84 and growing (i have a screenshot if anyone is interested). That happened last night. Today, the computer was ok and i managed to ssh into it. The root account was spammed with two types of cron mails. half of them said: mv: /var/db/entropy/saved-entropy.2: No such file or directory and the other half said: override r operator/operator for /var/db/entropy/saved-entropy.2? (y/n [n]) not overwritten So i know that it's the save-entropy cron job, but i doubt that was supposed to happen, and i have never touched that directory. Anyone has an idea? ps. this has happened before, and i had to go to the place the computer is at and reset it. (the tty's did not respond either) -- Real programmers don't document. If it was hard to write, it should be hard to understand. signature.asc Description: This is a digitally signed message part.
No /dev/da0
Hello, I am writing to this list because I haven't found anything that helps me in the 'web' nor in usenet. First I have to apologize for my bad english and mey bad knowing of what I'm doing with FreeBSD, I am not a 'hacker' but just a user. Well my problem is mounting my digital camera. If I remember correctly I did it with mount_msdosfs /dev/da0s1 /lumix I think that was under FreeBSD 6.n But now, upgraded to 7.2, there ist no /dev/da0. Attached to an iBook with Mac OS X 10.4 the cards were well mounted as 'disk2s1'. If I attach the camera to the FreeBSD PC the console gives [attaching the camera] | umass0: Panasonic DMC-FX8, class 0/0, rev 1.10/0.10, addr 4 on |uhub0 |(probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 |(probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error |(probe0:umass-sim0:0:0:0): SCSI Status: Check Condition |(probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 |(probe0:umass-sim0:0:0:0): Not ready to ready change, medium may have |changed |(probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data) |da0 at umass-sim0 bus 0 target 0 lun 0 |da0: MATSHITA DMC-FX8 0100 Removable Direct Access SCSI-2 device |da0: 1.000MB/s transfers |da0: 14MB (29121 512 byte sectors: 64H 32S/T 14C) But there is no /dev/da0 # ls /dev/da* ls: No match. If I detach it the console writes [detaching the camera] | umass0: at uhub0 port 8 (addr 4) disconnected |(da0:umass-sim0:0:0:0): lost device |(da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x39, scsi |status == | 0x0 |(da0:umass-sim0:0:0:0): removing device entry |umass0: detached I haven't any clue if it's FreeBSD's fault, the camera's or mine. Is there somone who can give me some hint? Sabine ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: freebsd-questions Digest, Vol 284, Issue 11
Date: Sat, 14 Nov 2009 20:29:59 -0600 From: CyberLeo Kitsana cyber...@cyberleo.net Subject: [FreeBSD Questions] Filesystem image as root To: FreeBSD Questions freebsd-questions@freebsd.org Cc: CyberLeo cyber...@cyberleo.net Message-ID: 4aff67a7.6040...@cyberleo.net Content-Type: text/plain; charset=ISO-8859-1 I have been thinking and experimenting for weeks, but I cannot figure this out. I have an Intel SS4200 NAS that I wish to use as a ZFS NAS with FreeBSD 8.0. The device has 4 SATA bays, and I don't want to use one for a UFS root disk. I don't want to use up hundreds of megabytes of RAM preloading an mfsroot that can never shrink. The single IDE connector is accessible via the legacy ISA ports, and is thus limited to PIO modes (about 1.6MB/sec max, even with an actual hard drive instead of a CF card). You are off by an order of magnitude (base 2 or 10): Pio mode 0 is ~3.3 MB/s Pio mode 4 is ~16.7 MB/s http://www.pcguide.com/ref/hdd/if/ide/modesPIO-c.html You can probably set PIO mode 4 for with: # atacontrol mode ad0 PIO4 I am currently using ~ 159MB on my root partition, At 16.7MB/s that is a 10 second load time; and as you said, frequently used files will be cached. (I have a CF card that has 15MB/s symmetric read/write. Don't know how special it is.) With a CF card there should be no seek delay of ~ 10 ms (for reads anyway, deleting blocks probably takes 10ms). Regards, James Phillips SNIPPED pivot_root attempt I can't help with. My summary: maybe you are trying too hard :) __ Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now http://ca.toolbar.yahoo.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how to do a custom install?
On Sun, 15 Nov 2009 01:03:03 -0800, Gary Kline kl...@thought.org wrote: anybody remember what keys to hit in the installation procedure? Let me access my brain... open(brain); Start installation which brings up sysinstall. Choose CUSTOM. First set up slice in FDISK, press 'd' to nuke 'em all, then 'c' to create a new slice covering the whole disk (I think this is what you want), give it active attribute with 's', then 'q' to quit and write changes. Choose standard MBR. The go to PARTITIONS. With 'c' (each one) create: 1 GB - FS - mount as / 2 GB - SWAP 1 GB - FS - mount as /tmp 1 GB - FS - mount as /var 10 GB - FS - mount as /usr 50 GB - FS - mount as /usr/local * - FS - mount as /home Adjust numbers to your individual needs, 'q' when done. After that, proceed with installation. Choose packages, services and other stuff as you want. Always keep in mind: READ what's on the screen. Not doing that could lead to massive data destruction. Oh wait, who am I talking to? You already know that, and I didn't say anything. :-) According to terminology: In MICROS~1 land, slices are called DOS primary partitions. There can be 4 of them. FreeBSD can create more than 4 slices per disk. What FreeBSD calls partitions (i. e. subdivisions of a slice, each holding a file system) have no expression in MICROS~1 land and could maybe be compared to logical volumes inside a DOS extended partition. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Produce identical packages for checksum comparison?
On 11/15/09, Chris christopher...@telting.org wrote: b. f. wrote: Chris wrote: ... Even if you edited your filesystem or archives to change the timestamps of package files, the I think that could be accomplished though the port makefiles. I think that the exact reproduction of whole archives will be problematic, unless you have a means of changing the ctime of the binaries that have been built to a predetermined value. toolchain used to create the binary files in packages often injects random seeds, timestamps, file paths, uid/gid information, etc. that I can understand file paths with debug info. Timestamps? Ok sure for a timestamp file being generated during a make that auto increments version numbers. What would change about uid/gid? I can't imagine why that might be in the binaries. ar(1) and some of the other utilities inject this information into certain binary files. Try running 'objdump -a' on, for example, some static archive like /usr/lib/libc.a. Of course this information can be manipulated, but you have to do it. See the patches in the link I cited earlier for other examples. ... Why would the build tools be injecting random numbers into binaries? Usually to provide some degree of uniqueness. I'm not saying that it is always done, just that it _may_ be done. See, for example, the gcc sources or the -frandom-seed option description in gcc(1). And it may not be just the compiler toolchain -- a port may do it. Occasionally, there are other sources of non-determinism. For example, in a recent thesis, a researcher who was trying to use reproducible builds to defeat a longstanding security threat found that the tcc compiler produced non-deterministic builds because of a defect in sign-extending some casts, and a problem with long double output. He also cited another researcher's finding that a certain java compiler's output was dependent upon the address of heap memory addresses used during compilation. See: http://www.dwheeler.com/trusting-trust/dissertation/wheeler-trusting-trust-ddc.pdf ... If I concentrated on one problem at a time I would never get anything done. ?! :) b. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: diskless - NFS root mount problem
snip all Please compare my working configuration to yours to check. I found lots of odd problems in your post and I thought it'd be best to just run with this clean slate. Network config: One low-power PC Engines ALIX board running as the NFS server, with a microdrive partitioned off for it's own system, plus a separate mounted partition for diskless clients. This config works best with one diskless client, and is not the documented way from FreeBSD handbook to accomplish diskless workstations. I'll note what I immediately saw as an error in your config during these snippets. alix# bsdlabel /dev/ad0s1 # /dev/ad0s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 1048576 164.2BSD 2048 16384 8 c: 120001770unused0 0 # raw part, don't edit h: 10951585 10485924.2BSD 2048 16384 28552 alix# cat /etc/fstab /dev/ad0s1a / ufs rw 0 0 /dev/ad0s1h /diskless ufs rw 0 0 alix# cat /etc/exports /diskless -maproot=0:0-network 192.168.0.0 -mask 255.255.255.0 *** maproot needs a user and group definition. alix# cat /etc/rc.conf rpcbind_enable=YES nfs_server_enable=YES rpc_statd_enable=YES rpc_lockd_enable=YES *** rpc_lockd provides file locking, rpc_lockd depends on rpc_statd ** Diskless side *** I believe the root filesystem information is passed on from dhcp, to pxeboot, to the kernel, in order to mount the root filesystem. You can have a 0-size fstab file for read-write access, or provide the read-only nfs root here. If you want it read only, it's best to specify it here, such as below alix# cat /diskless/etc/fstab 192.168.0.1:/diskless / nfs ro 0 0 alix# cat /diskless/etc/rc.conf rpcbind_enable=YES nfs_client_enable=YES rpc_statd_enable=YES rpc_lockd_enable=YES *** File locking needed lockd/statd support on the client, also. Think of editing /etc/passwd (the proper way) when you need file locking. This will result in a basic, 1-workstation diskless setup working. The difference is that the FreeBSD rc startup looks for a /conf directory which can provide multiple overrides to multiple workstations. I tried setting up a livecd with a /conf directory only to find that the /conf is checked, no matter which medium it's booting off of. This config does NOT cover the DHCP scope, TFTP, IPs or other settings that might be pertinent to booting diskless-ly. Note that by sharing your exact / filesystem as an export is a bad idea. It will essentially create a NFS server on a NFS server round robin and probably won't connect. It's why you setup a separate partition (EVEN if it's a file-backed filesystem mounted with the help of mdconfig on a separate mountpoint on your filesystem). Once you revise your config, please try again. --Tim ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Re: diskless - NFS root mount problem
Hi Tim, thanks a lot for your answer, I'll try that out tomorrow. cheers, mgp Please compare my working configuration to yours to check. I found lots of odd problems in your post and I thought it'd be best to just run with this clean slate. Network config: One low-power PC Engines ALIX board running as the NFS server, with a microdrive partitioned off for it's own system, plus a separate mounted partition for diskless clients. This config works best with one diskless client, and is not the documented way from FreeBSD handbook to accomplish diskless workstations. I'll note what I immediately saw as an error in your config during these snippets. alix# bsdlabel /dev/ad0s1 # /dev/ad0s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 1048576 164.2BSD 2048 16384 8 c: 120001770unused0 0 # raw part, don't edit h: 10951585 10485924.2BSD 2048 16384 28552 alix# cat /etc/fstab /dev/ad0s1a / ufs rw 0 0 /dev/ad0s1h /diskless ufs rw 0 0 alix# cat /etc/exports /diskless -maproot=0:0-network 192.168.0.0 -mask 255.255.255.0 *** maproot needs a user and group definition. alix# cat /etc/rc.conf rpcbind_enable=YES nfs_server_enable=YES rpc_statd_enable=YES rpc_lockd_enable=YES *** rpc_lockd provides file locking, rpc_lockd depends on rpc_statd ** Diskless side *** I believe the root filesystem information is passed on from dhcp, to pxeboot, to the kernel, in order to mount the root filesystem. You can have a 0-size fstab file for read-write access, or provide the read-only nfs root here. If you want it read only, it's best to specify it here, such as below alix# cat /diskless/etc/fstab 192.168.0.1:/diskless / nfs ro 0 0 alix# cat /diskless/etc/rc.conf rpcbind_enable=YES nfs_client_enable=YES rpc_statd_enable=YES rpc_lockd_enable=YES *** File locking needed lockd/statd support on the client, also. Think of editing /etc/passwd (the proper way) when you need file locking. This will result in a basic, 1-workstation diskless setup working. The difference is that the FreeBSD rc startup looks for a /conf directory which can provide multiple overrides to multiple workstations. I tried setting up a livecd with a /conf directory only to find that the /conf is checked, no matter which medium it's booting off of. This config does NOT cover the DHCP scope, TFTP, IPs or other settings that might be pertinent to booting diskless-ly. Note that by sharing your exact / filesystem as an export is a bad idea. It will essentially create a NFS server on a NFS server round robin and probably won't connect. It's why you setup a separate partition (EVEN if it's a file-backed filesystem mounted with the help of mdconfig on a separate mountpoint on your filesystem). Once you revise your config, please try again. --Tim - Вижте водещите новини от Vesti.bg! http://www.vesti.bg ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: weird save-entropy behaviour
On Sunday 15 November 2009 17:30:02 Ed Jobs wrote: Yesterday, i noticed a very weird behaviour on my computer (which is running 8.0-RC3 btw. The shells were not responding and the load was insane, and constantly going up. At the time i managed to lock myself out, the load was 84 and growing (i have a screenshot if anyone is interested). That happened last night. Today, the computer was ok and i managed to ssh into it. The root account was spammed with two types of cron mails. half of them said: mv: /var/db/entropy/saved-entropy.2: No such file or directory and the other half said: override r operator/operator for /var/db/entropy/saved-entropy.2? (y/n [n]) not overwritten So i know that it's the save-entropy cron job, but i doubt that was supposed to happen, and i have never touched that directory. Anyone has an idea? Did the operator uid change or perhaps shared with another uid? Check both `id operator` and `id 2`. Secondly, why did this stop? Seems like a weird question to ask, but since this script is supposed to run every 11 minutes, there should not be a reason for this to stop, if there's a race condition. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: weird save-entropy behaviour
On Monday 16 November 2009 00:12, Mel Flynn wrote:
Did the operator uid change or perhaps shared with another uid?
Check both `id operator` and `id 2`.
Secondly, why did this stop? Seems like a weird question to ask, but since
this script is supposed to run every 11 minutes, there should not be a
reason for this to stop, if there's a race condition.
# id operator
uid=2(operator) gid=5(operator) groups=5(operator)
# id 2
uid=2(operator) gid=5(operator) groups=5(operator)
As for the orer part, why did it stop, i really have no clue. All the messages
arrived at root's mailbox at 5:57, tho the date in them said that they were
sent at 5:50.
It's really strange because I was locked out from the computer at 2:29, so
it's not something I did. and there's nothing that cron runs at that time.
by the way:
the mails that i got were not only about /var/db/entropy/saved-entropy.2, but
/var/db/entropy/saved-entropy.{1,2,3,4,5,6,8} as well
--
Real programmers don't document. If it was hard to write, it should be hard to
understand.
signature.asc
Description: This is a digitally signed message part.
Re: weird save-entropy behaviour
On Sunday 15 November 2009 23:38:10 Ed Jobs wrote: On Monday 16 November 2009 00:12, Mel Flynn wrote: Did the operator uid change or perhaps shared with another uid? Check both `id operator` and `id 2`. Secondly, why did this stop? Seems like a weird question to ask, but since this script is supposed to run every 11 minutes, there should not be a reason for this to stop, if there's a race condition. # id operator uid=2(operator) gid=5(operator) groups=5(operator) # id 2 uid=2(operator) gid=5(operator) groups=5(operator) As for the orer part, why did it stop, i really have no clue. All the messages arrived at root's mailbox at 5:57, tho the date in them said that they were sent at 5:50. It's really strange because I was locked out from the computer at 2:29, so it's not something I did. and there's nothing that cron runs at that time. Does the cron log (/var/log/cron) show that it was run as operator around the time it started? /usr/sbin/cron[47350]: (operator) CMD (/usr/libexec/save-entropy) Even if it wasn't, I don't see a reason for such a buildup. Unlesssince stdin isn't sending anything, it could be the scripts wait indefinitely for user confirmation, then finally get killed off by some limit. There should be some hint at that in /var/log/messages around 5:50. The script should probably do mv -f in line 76. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: freebsd-questions Digest, Vol 284, Issue 11
James Phillips wrote: Date: Sat, 14 Nov 2009 20:29:59 -0600 From: CyberLeo Kitsana cyber...@cyberleo.net Subject: [FreeBSD Questions] Filesystem image as root The single IDE connector is accessible via the legacy ISA ports, and is thus limited to PIO modes (about 1.6MB/sec max, even with an actual hard drive instead of a CF card). You are off by an order of magnitude (base 2 or 10): Pio mode 0 is ~3.3 MB/s Pio mode 4 is ~16.7 MB/s http://www.pcguide.com/ref/hdd/if/ide/modesPIO-c.html You can probably set PIO mode 4 for with: # atacontrol mode ad0 PIO4 If only that were true in this case. (85eef1f3)[r...@ss4200 ~]# atacontrol mode ad0 PIO4 current mode = PIO2 (85eef1f3)[r...@ss4200 ~]# atacontrol mode ad0 PIO4 current mode = PIO2 (85eef1f3)[r...@ss4200 ~]# dd if=/dev/ad0 of=/dev/null bs=4096 count=4096 4096+0 records in 4096+0 records out 16777216 bytes transferred in 10.111748 secs (1659181 bytes/sec) Nothing I've tried seems to boost the throughput, hence the desire to use a compressed cached filesystem image. Thanks for the suggestions, though! -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net cyber...@cyberleo.net Furry Peace! - http://.fur.com/peace/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: weird save-entropy behaviour
On Monday 16 November 2009 00:58, Mel Flynn wrote: Does the cron log (/var/log/cron) show that it was run as operator around the time it started? /usr/sbin/cron[47350]: (operator) CMD (/usr/libexec/save-entropy) Even if it wasn't, I don't see a reason for such a buildup. Unlesssince stdin isn't sending anything, it could be the scripts wait indefinitely for user confirmation, then finally get killed off by some limit. There should be some hint at that in /var/log/messages around 5:50. The script should probably do mv -f in line 76. you were right. there was something at the messages. Nov 15 05:50:49 hostname sshd[1126]: error: accept: Software caused connection abort Nov 15 05:50:49 hostname last message repeated 6 times weird. the only thing in auth.log about sshd[1126] is: Nov 13 12:31:51 hostname sshd[1126]: Server listening on :: port 22. Nov 13 12:31:51 hostname sshd[1126]: Server listening on 0.0.0.0 port 22. and the message that was in the messages log too. -- Real programmers don't document. If it was hard to write, it should be hard to understand. signature.asc Description: This is a digitally signed message part.
Trivial questions about CNTL-ALT-DEL and CNTL-ALT-BACKSPACE
Many thanks to those who responded regarding my two questions. With regards to the CNTL-ALT-BACKSPACE sequence and its ability (or lack thereof) to cause an immediate shutdown of the X server... well... I _did_ go and read the Handbook section that Manolis Kiagias kindly posted a link to, and I have now tried _both_ of the two ways described there to re-enable CNTL-ALT-BACKSPACE functionality for the X server, and sadly I must report that for me, at least _neither_ of those methods worked. I did everything exactly and precisely as described. I even cut and pasted the code in the Handbook that was suggested for the /usr/local/etc/hal/fdi/policy/x11-input.fdi file, and still, CNTL-ALT-BACKSPACE is producing no effect whatsoever for me. This is on 7.2-RELEASE/amd64. What now? send-pr? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Trivial questions about CNTL-ALT-DEL and CNTL-ALT-BACKSPACE
Ronald F. Guilmette wrote: Many thanks to those who responded regarding my two questions. With regards to the CNTL-ALT-BACKSPACE sequence and its ability (or lack thereof) to cause an immediate shutdown of the X server... well... I _did_ go and read the Handbook section that Manolis Kiagias kindly posted a link to, and I have now tried _both_ of the two ways described there to re-enable CNTL-ALT-BACKSPACE functionality for the X server, and sadly I must report that for me, at least _neither_ of those methods worked. I did everything exactly and precisely as described. I even cut and pasted the code in the Handbook that was suggested for the /usr/local/etc/hal/fdi/policy/x11-input.fdi file, and still, CNTL-ALT-BACKSPACE is producing no effect whatsoever for me. This is on 7.2-RELEASE/amd64. What now? send-pr? Keep the x11-input.fdi section from the Handbook, and also add the following line to /etc/X11/xorg.conf, at the end of the ServerLayout section: Option DontZap false Restart your system, it should work now. (Just tried it on mine. It won't work without both of these changes). Please report back if it works for you! By the way Xorg configuration becomes more and more elusive. Initially, DontZap was enough. Then it had no effect at all and the fdi file was needed. Now seems both are needed. What's next? I'll test this in a few other systems and update the Handbook section if it seems to be the latest norm. Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
no sshd on new server...
ok, i have my new server-to-be underway but having problems exec'ing /usr/sbin/sshd. i can ssh out to existing computers, but cannot ssh or scp stuff in. so my question is: how do i create /etc/ssh/ssh_host_dsa_key ? checking around does no good. tia for any insights, gary -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org The 7.31a release of Jottings: http://jottings.thought.org/index.php ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: no sshd on new server...
Gary Kline wrote: ok, i have my new server-to-be underway but having problems exec'ing /usr/sbin/sshd. i can ssh out to existing computers, but cannot ssh or scp stuff in. so my question is: how do i create /etc/ssh/ssh_host_dsa_key ? checking around does no good. tia for any insights, gary Add: sshd_enable=YES to /etc/rc.conf and then execute: /etc/rc.d/sshd start (or reboot your system) The keys will be automatically created at first startup of the ssh daemon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: no sshd on new server...
On Sun, 15 Nov 2009 15:49:33 -0800, Gary Kline kl...@thought.org wrote: ok, i have my new server-to-be underway but having problems exec'ing /usr/sbin/sshd. i can ssh out to existing computers, but cannot ssh or scp stuff in. so my question is: how do i create /etc/ssh/ssh_host_dsa_key ? checking around does no good. Maybe I remember incorrectly, but doesn't sshd create this file on its first startup? Do you have sshd_enable=YES in /etc/rc.conf? Is sshd running, or do you get error messages regarding the host DSA key file? -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Trivial questions about CNTL-ALT-DEL and CNTL-ALT-BACKSPACE
On Mon, 16 Nov 2009 01:49:04 +0200, Manolis Kiagias son...@otenet.gr wrote: By the way Xorg configuration becomes more and more elusive. Initially, DontZap was enough. Then it had no effect at all and the fdi file was needed. Now seems both are needed. What's next? If this continues, I'll run my 5.4-p8 workstation with old fashioned X (already X.org) until I die. :-) No, honestly: X is going to be more and more annoying. Have you noticed the long startup time? Nearly a half minute (!!!) on a 1.5 GHz system! I know that there is lots of work done to make life easier for X developers, especially getting rid of many OS specific stuff, but... Finally, sliding more off-topic: Not only X gets slower with each release, the same applies for almost all X applications, except the old fashioned ones. Sad. Just: Sad. Thanks for your patience so I could say this. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Bad Blocks... Should I RMA?
In one of my systems, I've got a Seagate SATA 500GB drive (ST3500320AS) which is actually not very old... purchased 12/11/2008. It's never given me any problems, but just a few minutes ago, while compiling a small C program, I got a set of three irrecoverable errors in quick succession... apparently all read errors from the same single block. Here's the relevant lines from /var/log/messages: Nov 15 15:24:17 coredump kernel: ad4: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=256230591 Nov 15 15:24:43 coredump kernel: ad4: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=256230591 Nov 15 15:24:46 coredump kernel: ad4: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=256230591 (Don't be confused... The name of the host system here is coredump... my lame attempt at humor.) So anyway, this is one of those Seagate drives with 5-year warranty. (I only buy the 5-year ones these days... don't trust anything less.) This situation happened at a (relatively) opportune moment. I have zip, nada, nothing on the drive that needs to be either backed up or relocated to another drive. This drive is essentially blank at the moment. So, the question is, should I: 1) RMA the drive back to Seagate? 2) Somehow try to lock-out the bad sector(s)? (If so, how?) 3) Other? If it was failing all over the place (and on multiple blocks), then yea, sure, I'd RMA it back to Seagate in a heartbeat. But heck! It's only one sector. And what's one sector between friends? Before posting this, I googled around a bit for the crrent Accepted Wisdom regarding such sitiations. Most seems to say that bad blocks (even one?) are an early warning of impending doom (for the drive), and suggest trashing or RMA'ing the drive. I just sorta wanted to know if folks here would agree or disagree with that. One thing concerns me about the thought of RMA'ing the drive back... The last time I RMA'd a drive (years ago a different brand) I got back as a replacement a ``refurb'' drive. Hummm. If I RMA this drive, it is possible that Seagate would replace it with a refurb whose remaining life may perhaps prove to be even less than the drive I am RMA'ing? Do Seagate RMA drive replacements come with fresh platters? Regards, rfg P.S. If I _do_ end up RMA'ing the thing back, do I need to worry about scrubing the drive squeaky clean first... you know... using one of these multiple write-over progs (like `wipe') if I am paranoid... as I am... about the possibility of old credit card numbers lying around in unallocated sectors on the drive? (The drive is empty _now_, but earlier it was in serious/heavy use.) I guess what I'm asking is: Do Segate and the other manufacturers care enough about their customer's privacy to securely wipe old drives/platters that come in to them for RMA? Or do I need to worry 'bout that for my own self? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how to do a custom install?
On Sun, Nov 15, 2009 at 08:59:32PM +1100, David Rawling wrote: -Original Message- From: Gary Kline Sent: Sun 15/11/2009 8:03 PM due to strange disk problems i was down for around 30 hours. i am currently wiping dos/win off in favor of 7.2-R and i have a question about doing a custom install that would let me slice the drive into more that four pieces. i am building, by default, /, /var SWAP, and /usr it has been years since my custom install where [[*some*]] technique let me slice something like, say, /, /var, /tmp, /usr/local/ SWAP, and /usr anybody remember what keys to hit in the installation procedure? tia, gary I can't say that I remember the keystrokes, but you can have multiple disk slices (aka Windows/DOS partitions) and within each slice, multiple BSD partitions (IIRC up to 8). I have mine partitioned into (generally) / - 1GB swap - 2x - 4x RAM /tmp - 4GB /var - 20GB /usr - 40% /backup - remainder I use the whole disk for BSD (single slice) and create the partitions as whatever size suits. Dave. yeah, i kinda, sorta remember now. you type A for the entire drive, then keep slicing off pieces. hmm, i think once i did that and got a big, fat X for the 5th one maybe i didn't enter the A that time. just for the heck of it, i'll retry, tx, gary -- David Rawling PD Consulting And Security Email: d...@pdconsec.net -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org The 7.31a release of Jottings: http://jottings.thought.org/index.php ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Trivial questions about CNTL-ALT-DEL and CNTL-ALT-BACKSPACE
Polytropon wrote: On Mon, 16 Nov 2009 01:49:04 +0200, Manolis Kiagias son...@otenet.gr wrote: By the way Xorg configuration becomes more and more elusive. Initially, DontZap was enough. Then it had no effect at all and the fdi file was needed. Now seems both are needed. What's next? If this continues, I'll run my 5.4-p8 workstation with old fashioned X (already X.org) until I die. :-) I feel your pain... No, honestly: X is going to be more and more annoying. Have you noticed the long startup time? Nearly a half minute (!!!) Don't have any startup time problems myself. I mostly run on Atom CPUs, nothing fancy. on a 1.5 GHz system! I know that there is lots of work done to make life easier for X developers, especially getting rid of many OS specific stuff, but... Finally, sliding more off-topic: Not only X gets slower with each release, the same applies for almost all X applications, except the old fashioned ones. Just the fact that I now have to edit an xml file to simply add a Greek keyboard layout is annoying enough. Combine with the fact that for some reason keyboard / mouse may or may not be detected depending on the machine, phase of the moon etc, needing AutoAddInputDevices and AllowEmptyInput hacks, I'd call it nightmare on HAL street... But that's enough ranting for tonight, I had an entire blog post complaining about it. Let's just hope we can cope with the documentation changes so we have some place to resort to! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: no sshd on new server...
Polytropon wrote:
On Sun, 15 Nov 2009 15:49:33 -0800, Gary Kline kl...@thought.org wrote:
ok, i have my new server-to-be underway but having problems exec'ing
/usr/sbin/sshd. i can ssh out to existing computers, but cannot ssh
or scp stuff in. so my question is: how do i create
/etc/ssh/ssh_host_dsa_key ? checking around does no good.
Maybe I remember incorrectly, but doesn't sshd create this file
on its first startup?
Do you have
sshd_enable=YES
in /etc/rc.conf? Is sshd running, or do you get error messages
regarding the host DSA key file?
This is version specific. If you're really old fashioned (v4, for
example ;-), you can look in /etc/rc.network for a cookbook:
case ${sshd_enable} in
[Yy][Ee][Ss])
if [ -x /usr/bin/ssh-keygen ]; then
if [ ! -f /etc/ssh/ssh_host_key ]; then
echo ' creating ssh1 RSA host key';
/usr/bin/ssh-keygen -t rsa1 -N \
-f /etc/ssh/ssh_host_key
fi
if [ ! -f /etc/ssh/ssh_host_rsa_key ]; then
echo ' creating ssh2 RSA host key';
/usr/bin/ssh-keygen -t rsa -N \
-f /etc/ssh/ssh_host_rsa_key
fi
if [ ! -f /etc/ssh/ssh_host_dsa_key ]; then
echo ' creating ssh2 DSA host key';
/usr/bin/ssh-keygen -t dsa -N \
-f /etc/ssh/ssh_host_dsa_key
fi
fi
;;
esac
or just reboot after setting sshd_enable=YES. In newer versions,
/etc/rc.d/sshd start checks if the files exist and creates any of the
3 which don't, or you can force this check and creation with
/etc/rc.d/sshd keygen. In all cases that I know of, it's just the
ssh-keygen program being run on your behalf.
--
--Jon Radel
j...@radel.com
smime.p7s
Description: S/MIME Cryptographic Signature
Re: Trivial questions about CNTL-ALT-DEL and CNTL-ALT-BACKSPACE
On Mon, 16 Nov 2009 02:21:28 +0200, Manolis Kiagias son...@otenet.gr wrote: Just the fact that I now have to edit an xml file to simply add a Greek keyboard layout is annoying enough. The fact that annoys me is that configuration seems to have disassembled into several parts that are not located in a central file (such as xorg.conf has been); I have no problem with editing text files if I need to, but now it's getting somewhat complicated - I'm not confortable with the fact that FreeBSD is (getting) complicated, I always loved it because everything is so simple. Combine with the fact that for some reason keyboard / mouse may or may not be detected depending on the machine, phase of the moon etc, needing AutoAddInputDevices and AllowEmptyInput hacks, I'd call it nightmare on HAL street... This famous quote comes to mind: HAL: Look Dave, I can see you're really upset about this. I honestly think you ought to sit down calmly, take a stress pill, and think things over. ... Maybe this is all fine as long as you have up-to-date hardware that will deliver all the data needed for the autodetection and autoconfiguration magic, but what's if you're *insisting* on using a 21 Eizo CRT and a three button Sun mouse (where the middle mouse button does both middle-click and wheel)? And then I really ask myself: Will the xmodmap hack (i. e. or i. has been the canonical way) still work for my Sun keyboard that I insist on using? But that's enough ranting for tonight, I had an entire blog post complaining about it. But I am not complaining! :-) I've been told that those changes are absolutely needed to design the creation of new software more efficiently and cheaper; this is often confused with bloat, but it's not, it's evolution! And there's no way around. I would be more happy if things would really get better, or even not worse, but sadly, they seem to. Software gets slower as well as less accessible - Gtk 2, used by many programs, is a good (bad) example. Am I supposed to buy new computer to replace perfectly running systems just to keep the overall usage speed of everything at the same level? Oh wait, that's economy. Let us be thankful we have commerce. Buy more. Buy more now. Buy. And be happy. So much from the famous quoting department. :-) Let's just hope we can cope with the documentation changes so we have some place to resort to! I hope documentation refers to how documentation should be properly done, and how it IS done in FreeBSD, and not the (sorry) Linux way of documentation. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Bad Blocks... Should I RMA?
On Sun, 15 Nov 2009 16:06:55 -0800, Ronald F. Guilmette r...@tristatelogic.com wrote: So, the question is, should I: 1) RMA the drive back to Seagate? Yes. 2) Somehow try to lock-out the bad sector(s)? (If so, how?) [...] If it was failing all over the place (and on multiple blocks), then yea, sure, I'd RMA it back to Seagate in a heartbeat. But heck! It's only one sector. And what's one sector between friends? If there's already error messaging to the OS, then the drive's firmware has noticed that it can't compensate errors anymore. This means: Probably there isn't only one bad sector - there are lots of them. (The drive uses spare sectors to move data to them when a sector in use gets bad.) Backup all your important data and get rid of this drive, this will save you possibly upcoming trouble. Before posting this, I googled around a bit for the crrent Accepted Wisdom regarding such sitiations. Most seems to say that bad blocks (even one?) are an early warning of impending doom (for the drive), and suggest trashing or RMA'ing the drive. I just sorta wanted to know if folks here would agree or disagree with that. From my knowledge and experience, this is correct. One thing concerns me about the thought of RMA'ing the drive back... The last time I RMA'd a drive (years ago a different brand) I got back as a replacement a ``refurb'' drive. Hummm. If I RMA this drive, it is possible that Seagate would replace it with a refurb whose remaining life may perhaps prove to be even less than the drive I am RMA'ing? Do Seagate RMA drive replacements come with fresh platters? There's always smartctl (from port smartmontools) to do some checking on the drive you get back. P.S. If I _do_ end up RMA'ing the thing back, do I need to worry about scrubing the drive squeaky clean first... you know... using one of these multiple write-over progs (like `wipe') if I am paranoid... as I am... about the possibility of old credit card numbers lying around in unallocated sectors on the drive? (The drive is empty _now_, but earlier it was in serious/heavy use.) You could first mount all the partitions (from a live CD or DVD) of the disk and then to the magical remark read-file command (rm -rf /), and afterwards running dd if=/dev/zero of=/dev/ad0 bs=1m for a while. Check that ad0 really is the drive you want to clean, or else. :-) I guess what I'm asking is: Do Segate and the other manufacturers care enough about their customer's privacy to securely wipe old drives/platters that come in to them for RMA? Or do I need to worry 'bout that for my own self? I've got no experience with how Seagate treats his customers. To be sure, at least clean your disk a bit as mentioned above, because that's for YOUR security. If Seagate is intelligent enough to send you a new drive back with a FAT or NTFS file system on it... you'll delete it anyway. Help the manufacturer - help you. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Bad Blocks... Should I RMA?
Ronald F. Guilmette r...@tristatelogic.com writes: Nov 15 15:24:17 coredump kernel: ad4: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=256230591 This is *not* necessarily a big deal, despite what your other response told you. Errors on reads do not mean that your drive's bad-sector table is full; only errors on write indicate that. If you can try manufacturer's drive diagnostics, do that. If you can't, then it's harder to fix things up, but not impossible; write back if you really can't use a low-level diag. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
bash prompt update lagging
Hi,
I use the same bash config on Linux, FreeBSD and Cygwin, for the most part,
and I just noticed that on my FreeBSD system the prompt is updating one
command too late.
r...@kanga:/root$ pwd
/home/msoulier
r...@kanga:~$ cd /root
r...@kanga:~$ pwd
/root
r...@kanga:/root$
As you can see, the prompt with my current location doesn't update until the
command _following_ my directory change.
r...@kanga:/root$ echo $PS1
\[\033[1;32m\]\[\033[0;36m\]\u\[\033[1;32...@\[\033[0;36m\]\h\[\033[1;32m\]:\[\033[0;37m\]${SHORT_PWD}\[\033[1;32m\]$\[\033[0;37m\]
I'm wondering if this is a bash bug on bsd, or if I'm doing something wrong.
Has anyone seen this?
Thanks,
Mike
--
Michael P. Soulier msoul...@digitaltorque.ca
Any intelligent fool can make things bigger and more complex... It takes a
touch of genius - and a lot of courage to move in the opposite direction.
--Albert Einstein
pgpa3IweNPAgg.pgp
Description: PGP signature
Re: No /dev/da0
On Sun, Nov 15, 2009 at 07:11:14PM +0100, Sabine Baer wrote: Hello, I am writing to this list because I haven't found anything that helps me in the 'web' nor in usenet. First I have to apologize for my bad english and mey bad knowing of what I'm doing with FreeBSD, I am not a 'hacker' but just a user. Well my problem is mounting my digital camera. If I remember correctly I did it with mount_msdosfs /dev/da0s1 /lumix I think that was under FreeBSD 6.n But now, upgraded to 7.2, there ist no /dev/da0. Attached to an iBook with Mac OS X 10.4 the cards were well mounted as 'disk2s1'. If I attach the camera to the FreeBSD PC the console gives [attaching the camera] | umass0: Panasonic DMC-FX8, class 0/0, rev 1.10/0.10, addr 4 on |uhub0 |(probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 |(probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error |(probe0:umass-sim0:0:0:0): SCSI Status: Check Condition |(probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 |(probe0:umass-sim0:0:0:0): Not ready to ready change, medium may have |changed |(probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data) |da0 at umass-sim0 bus 0 target 0 lun 0 |da0: MATSHITA DMC-FX8 0100 Removable Direct Access SCSI-2 device |da0: 1.000MB/s transfers |da0: 14MB (29121 512 byte sectors: 64H 32S/T 14C) But there is no /dev/da0 # ls /dev/da* ls: No match. If I detach it the console writes [detaching the camera] | umass0: at uhub0 port 8 (addr 4) disconnected |(da0:umass-sim0:0:0:0): lost device |(da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x39, scsi |status == | 0x0 |(da0:umass-sim0:0:0:0): removing device entry |umass0: detached I haven't any clue if it's FreeBSD's fault, the camera's or mine. Is there somone who can give me some hint? Sabine Have you tried playing around with camcontrol(8)? Maybe after you've plugged it in, try: # camcontrol load 0:0:0 then: # camcontrol devlist and then try mounting it if it shows up given the above command. Sometimes, you have to: # camcontrol stop 0:0:0 # camcontrol rescan 0:0:0 # camcontrol load 0:0:0 to get it to behave. Before unplugging it, unmount it and then: # camcontrol eject 0:0:0 Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: bash prompt update lagging
On Sun, 15 Nov 2009 18:14:25 -0500, Michael P. Soulier
msoul...@digitaltorque.ca wrote:
\[\033[1;32m\]\[\033[0;36m\]\u\[\033[1;32...@\[\033[0;36m\]\h\[\033[1;32m\]:\[\033[0;37m\]${SHORT_PWD}\[\033[1;32m\]$\[\033[0;37m\]
I'm wondering if this is a bash bug on bsd, or if I'm doing something wrong.
Your PS1 seems to include ${SHORT_PWD}, a variable. It seems
that it is not updated immediately after the cd command.
Has anyone seen this?
No. I don't have any path information at all when I use your PS1.
p...@r55:$
By the way, this is bash-3.2.25 on FreeBSD/x86 7.
But I tried to replace the ${SHORT_PWD} by the \w control
sequence (as mentioned in man bash). This is the result:
$ export
PS1=\[\033[1;32m\]\[\033[0;36m\]\u\[\033[1;32...@\[\033[0;36m\]\h\[\033[1;32m\]:\[\033[0;37m\]\w\[\033[1;32m\]$\[\033[0;37m\]
p...@r55:~$ cd /etc
p...@r55:/etc$ cd /usr/src/sys
p...@r55:/usr/src/sys$
And the \W short form:
p...@r55:/usr/src/sys$ export
PS1=\[\033[1;32m\]\[\033[0;36m\]\u\[\033[1;32...@\[\033[0;36m\]\h\[\033[1;32m\]:\[\033[0;37m\]\w\[\033[1;32m\]$\[\033[0;37m\]
p...@r55:sys$ cd /bin
p...@r55:bin$ cd /usr/local
p...@r55:local$
The username and hostname are cyan, @, : and $ are bright green.
Is this what you've intended the prompt to look like?
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Partition naming, fstab, and geli
Say I have performed a standard installation of FreeBSD onto a single IDE drive with the following entries in /etc/fstab: /dev/ad0s1b none swap sw 0 0 /dev/ad0s1a / ufs rw 1 1 /dev/ad0s1d /var ufs rw 2 2 /dev/ad0s1e /tmp ufs rw 2 2 /dev/ad0s1f /usr ufs rw 2 2 Then I added more drives. 1. The Handbook suggests there is a convention that when partitioning a a drive that's been added, to label the first new partition on that drive as 'e' as opposed to 'a' (which is reserved for the /root partition). Does the following satisfy that convention, or would starting with 'a' in each case make more sense? /dev/ad1e /foo1 ufs rw 2 2 /dev/ad1f /bar1 ufs rw 2 2 /dev/ad1g /baz1 ufs rw 2 2 /dev/ad2e /foo2 ufs rw 2 2 /dev/ad2f /bar2 ufs rw 2 2 /dev/ad3e /foo3 ufs rw 2 2 /dev/ad3f /bar3 ufs rw 2 2 2. My second question is in regards to using the 'xx' fstype to have the system ignore that device. Consider, for example, a geli encrypted partition. The .eli device doesn't exist at boot time. I discovered by accident that the system won't boot with an fstab entry for a device that doesn't exist. So if I was to record an entry in fstab, I couldn't use /dev/ad1e.eli /home/david/private ufs rw 0 0 Does that mean that the following is what's typically to record fstab entries for ignored devices? /dev/ad1e.eli /home/david/private xx rw 0 0 /dev/ad3e /fakexx rw 0 0 /dev/ad3f /reservedxx rw 0 0 Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Partition naming, fstab, and geli
On Sun, 15 Nov 2009 19:23:15 -0700, David Allen the.real.david.al...@gmail.com wrote: 1. The Handbook suggests there is a convention that when partitioning a a drive that's been added, to label the first new partition on that drive as 'e' as opposed to 'a' (which is reserved for the /root partition). Does the following satisfy that convention, or would starting with 'a' in each case make more sense? /dev/ad1e /foo1 ufs rw 2 2 /dev/ad1f /bar1 ufs rw 2 2 /dev/ad1g /baz1 ufs rw 2 2 /dev/ad2e /foo2 ufs rw 2 2 /dev/ad2f /bar2 ufs rw 2 2 /dev/ad3e /foo3 ufs rw 2 2 /dev/ad3f /bar3 ufs rw 2 2 The Handbook says in 18.3.1 sub 3: A disk can have up to eight partitions, labeled a-h. A few of the partition labels have special uses. The a partition is used for the root partition (/). Thus only your system disk (e.g, the disk you boot from) should have an a partition. The b partition is used for swap partitions, and you may have many disks with swap partitions. The c partition addresses the entire disk in dedicated mode, or the entire FreeBSD slice in slice mode. The other partitions are for general use. Note the last sentence. Due to this statement, I think the usage of 'e' is arbitrary, 'd' could be okay, too, but when the Handbook says 'e' in the example (maybe with the intention of 'e' like in 'example'?), you can use 'e', too, especially when you want to use more than one partition. I have to admit that I never put slices on extra hard disks, I'm always using the whole disk, so # newfs /dev/ad3 would give me /dev/ad3 (which is the same as /dev/ad3c), and the entry /dev/ad3 /foo ufs rw 2 2 would go into fstab. I'm sure you already know this because it seems that you read up until 18.3.2.2 - you're omitting slices, dedicated mode. :-) Bottom line: The naming convention mentioned in the Handbook and your examples are completely okay. 2. My second question is in regards to using the 'xx' fstype to have the system ignore that device. Consider, for example, a geli encrypted partition. The .eli device doesn't exist at boot time. I discovered by accident that the system won't boot with an fstab entry for a device that doesn't exist. That's completely intended. :-) So if I was to record an entry in fstab, I couldn't use /dev/ad1e.eli /home/david/private ufs rw 0 0 Does that mean that the following is what's typically to record fstab entries for ignored devices? /dev/ad1e.eli /home/david/private xx rw 0 0 /dev/ad3e /fakexx rw 0 0 /dev/ad3f /reservedxx rw 0 0 I would say: No. The entry for those partitions should rather be: /dev/ad1e.eli /home/david/private ufs rw,noauto 0 0 /dev/ad3e /fakeufs rw,noauto 0 0 /dev/ad3f /reservedufs rw,noauto 0 0 The ufs in the FS field tells the system which FS to use when later mounting (e. g. with requiring a pass phrase from the operator), and noauto in the options field that prohibits mounting the file system at startup. If you used xx in the FS field, you could not easily # mount /reserved because the mount command wouldn't know which FS to use (allthough I think UFS might be a default here). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Default cannot install 8.0 rc2 in mobo P5QL-EM Hello, I am trying to install FreeBSD 8.0 rc2 on mobo ASUS P5QL-EM, but under the boot of the install dvd I get this run_interrupt_driven_hooks: still w
Hello, I am trying to install FreeBSD 8.0 rc2 on mobo ASUS P5QL-EM, but under the boot of the install dvd I get this run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config and then 120, 180 etc. Anyone know whats wrong? thanks -- View this message in context: http://old.nabble.com/Default-cannot-install-8.0-rc2-in-mobo-P5QL-EM-Hello%2C-I-am-trying-to-install-FreeBSD-8.0-rc2-on-mobo-ASUS-P5QL-EM%2C-but-under-the-boot-of-the-install-dvd-I-get-this--run_interrupt_driven_hooks%3A-still-waiting-after-60-seconds-for-xpt_config--and-then-120%2C-180-etc.--Anyone-know-whats-wrong--thanks-Reply-With-Quote-Multi-Quote-This-Message-Quick-reply-to-this-message-Thanks-tp26366441p26366441.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Trivial questions about CNTL-ALT-DEL and CNTL-ALT-BACKSPACE
On Mon, 16 Nov 2009, Polytropon wrote: On Mon, 16 Nov 2009 01:49:04 +0200, Manolis Kiagias son...@otenet.gr wrote: By the way Xorg configuration becomes more and more elusive. Initially, DontZap was enough. Then it had no effect at all and the fdi file was needed. Now seems both are needed. What's next? If this continues, I'll run my 5.4-p8 workstation with old fashioned X (already X.org) until I die. :-) No, honestly: X is going to be more and more annoying. Have you noticed the long startup time? Nearly a half minute (!!!) on a 1.5 GHz system! That's way too long for just X. Bloated desktop environment? Disk contention? I know that there is lots of work done to make life easier for X developers, especially getting rid of many OS specific stuff, but... Finally, sliding more off-topic: Not only X gets slower with each release, the same applies for almost all X applications, except the old fashioned ones. It sounds like we have very different experiences. While I wouldn't say the current xorg is a lot faster (not counting DRM), it's certainly not slower on any of the systems I have to test. But I don't know what video board you're using either. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Trivial questions about CNTL-ALT-DEL and CNTL-ALT-BACKSPACE
On Mon, 16 Nov 2009, Polytropon wrote: On Mon, 16 Nov 2009 02:21:28 +0200, Manolis Kiagias son...@otenet.gr wrote: Just the fact that I now have to edit an xml file to simply add a Greek keyboard layout is annoying enough. The fact that annoys me is that configuration seems to have disassembled into several parts that are not located in a central file (such as xorg.conf has been); I have no problem with editing text files if I need to, but now it's getting somewhat complicated - I'm not confortable with the fact that FreeBSD is (getting) complicated, I always loved it because everything is so simple. But xorg is not FreeBSD, so this is an unreasonable statement. FreeBSD is simple. X has never been particularly simple, and the fact that complexity grows over time is nothing new, either. But I am not complaining! :-) I've been told that those changes are absolutely needed to design the creation of new software more efficiently and cheaper; this is often confused with bloat, but it's not, it's evolution! And there's no way around. Of course there is: if you're happy with the state of your software, stop there! Don't upgrade. Don't replace what's working with something newer. That option is usually more difficult than it initially seems. The rest of the world tends to keep on evolving. I would be more happy if things would really get better, or even not worse, but sadly, they seem to. Software gets slower as well as less accessible - Gtk 2, used by many programs, is a good (bad) example. Am I supposed to buy new computer to replace perfectly running systems just to keep the overall usage speed of everything at the same level? As above, you don't *have* to upgrade. Keep the old software, and the old hardware will run it. Like everybody, I grumble about changes that don't seem to improve things at the user level. But I try to remember that without change, nothing can improve. It's also worth remembering that open source projects like xorg give the users the rare privilege of being able to make a difference. Test code, provide hardware, document bugs or fixes, do or fund development. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Default cannot install 8.0 rc2 in mobo P5QL-EM Hello, I am trying to install FreeBSD 8.0 rc2 on mobo ASUS P5QL-EM, but under the boot of the install dvd I get this run_interrupt_driven_hooks: sti
vuthecuong schrieb: Hello, I am trying to install FreeBSD 8.0 rc2 on mobo ASUS P5QL-EM, but under the boot of the install dvd I get this run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config and then 120, 180 etc. Anyone know whats wrong? thanks If there is a firewire port on your board you could try to disable firewire in the BIOS settings. This is a known problem. Uwe ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Bad Blocks... Should I RMA?
Lowell Gilbert wrote: Ronald F. Guilmette r...@tristatelogic.com writes: Nov 15 15:24:17 coredump kernel: ad4: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=256230591 This is *not* necessarily a big deal, despite what your other response told you. Errors on reads do not mean that your drive's bad-sector table is full; only errors on write indicate that. If you can try manufacturer's drive diagnostics, do that. If you can't, then it's harder to fix things up, but not impossible; write back if you really can't use a low-level diag. Yes -- this is correct. It's possible for a disk to be unable to read a sector, but rewriting the sector would either succeed and leave the sector fully working again, or cause it to be remapped in which case the disk will subsequently perform perfectly well[*]. Beyond running the manufacturers diagnostics, as the OP has said he has nothing particularly valuable on the drive, it might be worth running a few passes of dban or similar on the disk --- this will overwrite every part of the platter and should make it abundantly clear if there is a real and persistent problem. If you can't afford to scrub the disk, then just keep it under observation: if the problems recur within a few weeks then yes, definitely RMA that drive. Cheers, Matthew [*] If the error messages have disappeared since, then this has probably already happened. -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: Partition naming, fstab, and geli
On 11/15/09, Polytropon wrote: On Sun, 15 Nov 2009 19:23:15 -0700, David Allen wrote: 1. The Handbook suggests there is a convention that when partitioning a a drive that's been added, to label the first new partition on that drive as 'e' as opposed to 'a' (which is reserved for the /root partition). Does the following satisfy that convention, or would starting with 'a' in each case make more sense? /dev/ad1e /foo1 ufs rw 2 2 /dev/ad1f /bar1 ufs rw 2 2 /dev/ad1g /baz1 ufs rw 2 2 /dev/ad2e /foo2 ufs rw 2 2 /dev/ad2f /bar2 ufs rw 2 2 /dev/ad3e /foo3 ufs rw 2 2 /dev/ad3f /bar3 ufs rw 2 2 The Handbook says in 18.3.1 sub 3: A disk can have up to eight partitions, labeled a-h. A few of the partition labels have special uses. The a partition is used for the root partition (/). Thus only your system disk (e.g, the disk you boot from) should have an a partition. The b partition is used for swap partitions, and you may have many disks with swap partitions. The c partition addresses the entire disk in dedicated mode, or the entire FreeBSD slice in slice mode. The other partitions are for general use. Note the last sentence. Due to this statement, I think the usage of 'e' is arbitrary, 'd' could be okay, too, but when the Handbook says 'e' in the example (maybe with the intention of 'e' like in 'example'?), you can use 'e', too, especially when you want to use more than one partition. Well, you and I seem to be on the same page, but I was referring to the following: 2.6.5 Creating Partitions Using Disklabel Table 2-3. Partition Layout for Subsequent Disks The rest of the disk is taken up with one big partition. This could easily be put on the a partition, instead of the e partition. However, convention says that the a partition on a slice is reserved for the filesystem that will be the root (/) filesystem. You do not have to follow this convention, but sysinstall does, so following it yourself makes the installation slightly cleaner. You can choose to mount this filesystem anywhere; this example suggests that you mount them as directories /diskn, where n is a number that changes for each disk. But you can use another scheme if you prefer. The 'e' partition is again used in the Handbook section 18.3 Adding Disks. I guess I'm looking for the pedantic answer, but I'll settle for less. I have to admit that I never put slices on extra hard disks, I'm always using the whole disk, so # newfs /dev/ad3 would give me /dev/ad3 (which is the same as /dev/ad3c), and the entry /dev/ad3 /foo ufs rw 2 2 would go into fstab. I'm sure you already know this because it seems that you read up until 18.3.2.2 - you're omitting slices, dedicated mode. :-) I'd prefer the same with the first disk, but sysinstall won't accomodate it, and on most installations, it's more work trying to work around sysinstall than it is using it. So non-dedicated it is. Bottom line: The naming convention mentioned in the Handbook and your examples are completely okay. Great. 2. My second question is in regards to using the 'xx' fstype to have the system ignore that device. Consider, for example, a geli encrypted partition. The .eli device doesn't exist at boot time. I discovered by accident that the system won't boot with an fstab entry for a device that doesn't exist. That's completely intended. :-) LOL. Surprised me. I figured a 'noauto' for a non-existent device would be acceptable. So if I was to record an entry in fstab, I couldn't use /dev/ad1e.eli /home/david/private ufs rw 0 0 Does that mean that the following is what's typically to record fstab entries for ignored devices? /dev/ad1e.eli /home/david/private xx rw 0 0 /dev/ad3e /fakexx rw 0 0 /dev/ad3f /reservedxx rw 0 0 I would say: No. The entry for those partitions should rather be: /dev/ad1e.eli /home/david/private ufs rw,noauto 0 0 /dev/ad3e /fakeufs rw,noauto 0 0 /dev/ad3f /reservedufs rw,noauto 0 0 But the eli device doesn't exist until after it's attached, which, in my case, will happen manually and on-demand after boot. The ufs in the FS field tells the system which FS to use when later mounting (e. g. with requiring a pass phrase from the operator), and noauto in the options field that prohibits mounting the file system at startup. A pass phrase from the operator? Not likely. It's not a desktop. Each of the following will result in the system not booting: # there is no ad4 /dev/ad4a /foo ufs rw,noauto 0 0 #
Re: Bad Blocks... Should I RMA?
Lowell Gilbert wrote: Ronald F. Guilmette r...@tristatelogic.com writes: Nov 15 15:24:17 coredump kernel: ad4: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=256230591 This is *not* necessarily a big deal, despite what your other response told you. Errors on reads do not mean that your drive's bad-sector table is full; only errors on write indicate that. If you can try manufacturer's drive diagnostics, do that. If you can't, then it's harder to fix things up, but not impossible; write back if you really can't use a low-level diag. Yes -- this is correct. It's possible for a disk to be unable to read a sector, but rewriting the sector would either succeed and leave the sector fully working again, or cause it to be remapped in which case the disk will subsequently perform perfectly well[*]. Beyond running the manufacturers diagnostics, as the OP has said he has nothing particularly valuable on the drive, it might be worth running a few passes of dban or similar on the disk --- this will overwrite every part of the platter and should make it abundantly clear if there is a real and persistent problem. If you can't afford to scrub the disk, then just keep it under observation: if the problems recur within a few weeks then yes, definitely RMA that drive. Cheers, Matthew [*] If the error messages have disappeared since, then this has probably already happened. -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: no sshd on new server...
On Mon, Nov 16, 2009 at 01:57:18AM +0200, Manolis Kiagias wrote: Gary Kline wrote: ok, i have my new server-to-be underway but having problems exec'ing /usr/sbin/sshd. i can ssh out to existing computers, but cannot ssh or scp stuff in. so my question is: how do i create /etc/ssh/ssh_host_dsa_key ? checking around does no good. tia for any insights, gary Add: sshd_enable=YES to /etc/rc.conf and then execute: /etc/rc.d/sshd start (or reboot your system) The keys will be automatically created at first startup of the ssh daemon yup, this did the trick. i had assumed that ths 'sshd_enable=YES' line was there. but rc.conf was all but empty. tx again. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org The 7.31a release of Jottings: http://jottings.thought.org/index.php ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: no sshd on new server...
On Mon, Nov 16, 2009 at 01:00:14AM +0100, Polytropon wrote: On Sun, 15 Nov 2009 15:49:33 -0800, Gary Kline kl...@thought.org wrote: ok, i have my new server-to-be underway but having problems exec'ing /usr/sbin/sshd. i can ssh out to existing computers, but cannot ssh or scp stuff in. so my question is: how do i create /etc/ssh/ssh_host_dsa_key ? checking around does no good. Maybe I remember incorrectly, but doesn't sshd create this file on its first startup? Do you have sshd_enable=YES in /etc/rc.conf? Is sshd running, or do you get error messages regarding the host DSA key file? there were stderrs output when i tried to exec sshd. reason was that the rc.conf entry was not in rc.conf. (this is all going into my .howto file gary -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org The 7.31a release of Jottings: http://jottings.thought.org/index.php ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
