shell script problem
Hi all Please take a look at the script below wich I've wrote : 1- cat /foo/bar.txt | while read $LINE12- do3- cat /foo/bar/foo/bar.txt | while read $LINE24- do 5- if [ $LINE1 = $LINE2 ]; then6- sw=17- echo Current value of sw is : $sw8- break9- fi10- done11- echo Value of sw is : $sw12- if [ $sw = 0 ]; then13- DO SOMETHING14- fi15- sw=016- done You probebly guessed what I want to do. But the problem is that when the value of sw sets to 1 (in the first if statement) and the loop breaks , the value of sw is not '1' anymore in echo Value of sw is : $sw !!! Thanks in advance ... ___ 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: shell script problem
On Sun, 23 Dec 2012 01:05:35 -0800 (PST), Jack Mc Lauren wrote: Hi all Please take a look at the script below wich I've wrote : 1- cat /foo/bar.txt | while read $LINE12- do3- cat /foo/bar/foo/bar.txt | while read $LINE24- do 5- if [ $LINE1 = $LINE2 ]; then6- sw=17- echo Current value of sw is : $sw8- break9- fi10- done11- echo Value of sw is : $sw12- if [ $sw = 0 ]; then13- DO SOMETHING14- fi15- sw=016- done This is totally distorted! Allow me to re-arrange it. cat /foo/bar.txt | while read $LINE1 do cat /foo/bar/foo/bar.txt | while read $LINE2 do if [ $LINE1 = $LINE2 ]; then sw=1 echo Current value of sw is : $sw break fi done echo Value of sw is : $sw if [ $sw = 0 ]; then DO SOMETHING fi sw=0 done First, the lines with read have to be: cat /foo/bar.txt | while read $LINE1 cat /foo/bar/foo/bar.txt | while read $LINE2 Reason: $LINE1 and $LINE2 will be evaluated here, they are empty string, causing read to throw an error. You probebly guessed what I want to do. But the problem is that when the value of sw sets to 1 (in the first if statement) and the loop breaks , the value of sw is not '1' anymore in echo Value of sw is : $sw !!! Thanks in advance ... For testing, I've replaced the $sw=0 line with an echo command. I've created two files foo.txt and bar.txt for test, both have one line in common (3rd line in my example data). If I run the script, I get this output: Value of sw is :- after 1st line (uninitialized) Value of sw is : 0 - after 2nd line DO SOMETHING! Current value of sw is : 1 - after 3nd line (common entry) Value of sw is : 0 - after 4th line DO SOMETHING! Value of sw is : 0 - after 5th line DO SOMETHING! It seems that the condition $LINE1=$LINE2 properly triggers the current value echo command, while all non-common lines trigger the DO SOMETHING action. If you indended something else, please elaborate. -- 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: shell script problem
On Sun, 23 Dec 2012 10:34:34 +0100, Polytropon wrote: First, the lines with read have to be: cat /foo/bar.txt | while read $LINE1 cat /foo/bar/foo/bar.txt | while read $LINE2 Reason: $LINE1 and $LINE2 will be evaluated here, they are empty string, causing read to throw an error. Excuse me - I made a mistake! Of course those two lines have to be: cat /foo/bar.txt | while read LINE1 and cat /foo/bar/foo/bar.txt | while read LINE2 The $ infront of the variable names have to be removed. The variable _name_, not its content, has to be provided to read as a parameter. The script so far: #!/bin/sh cat foo.txt | while read LINE1 do cat bar.txt | while read LINE2 do if [ $LINE1 = $LINE2 ]; then sw=1 echo Current value of sw is : $sw break fi done echo Value of sw is : $sw if [ $sw = 0 ]; then echo DO SOMETHING! fi sw=0 done -- 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: shell script problem
On 23/12/2012 09:43, Polytropon wrote: On Sun, 23 Dec 2012 10:34:34 +0100, Polytropon wrote: First, the lines with read have to be: cat /foo/bar.txt | while read $LINE1 cat /foo/bar/foo/bar.txt | while read $LINE2 Reason: $LINE1 and $LINE2 will be evaluated here, they are empty string, causing read to throw an error. Excuse me - I made a mistake! Of course those two lines have to be: cat /foo/bar.txt | while read LINE1 and cat /foo/bar/foo/bar.txt | while read LINE2 The $ infront of the variable names have to be removed. The variable _name_, not its content, has to be provided to read as a parameter. The script so far: #!/bin/sh cat foo.txt | while read LINE1 do cat bar.txt | while read LINE2 do if [ $LINE1 = $LINE2 ]; then sw=1 echo Current value of sw is : $sw break fi done echo Value of sw is : $sw if [ $sw = 0 ]; then echo DO SOMETHING! fi sw=0 done Hmmm I'd just like to draw your attention to the comm(1) program, which lets you find lines common to two files, or only in one or other of a pair of inputs, very easily. The only slight gotcha is that the input files have to be sorted. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
bind 192.168.1.1 to all interfaces
Hi, FreeBSD. I have many vlans on server. IPs on those vlans are like 10.X.X.X/Y I have run DHCP. But some times users on vlan can ON their soho router like DIR-300 or so and connect their internet cable to LAN port of that router. So in my vlan I have two DHCP servers. One is mine and second is on that router. Some users get wrong IPs from that router. Can I bind 192.168.1.1 address of router to server so restrict such router to work normally? Or s there any other method to prevent such ilegal DHCP servers on LAN? -- Eugen mailto:kes-...@yandex.ru ___ 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: shell script problem
On Sun, 23 Dec 2012 09:57:02 + Matthew Seaman matt...@freebsd.org wrote: Hmmm I'd just like to draw your attention to the comm(1) program, which lets you find lines common to two files, or only in one or other of a pair of inputs, very easily. The only slight gotcha is that the input files have to be sorted. For which purpose the sort program is most useful. -- Steve O'Hara-Smith st...@sohara.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: how to configure host login account to use jail?
Damien Fleuriot wrote: On 23 Dec 2012, at 03:43, Fbsd8 fb...@a1poweruser.com wrote: Have jails up and running on host with ip address of 10.0.10.10 10.0.10.11 10.0.10.12 10.0.10.13 10.0.10.14 The host rc.conf has ifconfig_xl0=DHCP # nix connected to isp ifconfig_rl0=inet 10.0.10.2 #lan nic I want lan users to login to their jail by ip address using ssh. How do I setup host user accounts so they login to their associated jail? Is this something I code in the host user account or is it done by the remote ssh login command? How do other jail users do this? I assign public IPs to my jails and let people SSH to them. Ok but as my question asks, how do you configure things to get that to work? I am after the details. ___ 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: bind 192.168.1.1 to all interfaces
Le Sun, 23 Dec 2012 14:17:47 +0200, Eugen Konkov kes-...@yandex.ru a écrit : Hello, Or s there any other method to prevent such ilegal DHCP servers on LAN? At work we use dhcp_probe http://www.net.princeton.edu/software/dhcp_probe/ It works quite fine, when someone plug a dhcp server it is detected and we shutdown the switch port. I don't know if it runs on FreeBSD, it runs on Centos 6. Regards. ___ 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 configure host login account to use jail?
On 23/12/2012 13:11, Fbsd8 wrote: Ok but as my question asks, how do you configure things to get that to work? I am after the details. You need to run an instance of sshd in each jail. Because sshd defaults to binding to INADDR_ANY, you need to modify the sshd configuration in the host system, so it binds to a specific address, otherwise it will likely block out the jailed sshd's: ListenAddress 192.0.2.1 ListenAddress 2001:DB8::1 ListenAddress 127.0.0.1 ListenAddress ::1 sshd in the jails doesn't need any similar configuration change. You don't need user accounts in your host system for the jail users -- each jail can have it's own passwd file etc. However, it can be useful to make sure that UID numbers for regular users in host and jails don't overlap. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: how to configure host login account to use jail?
Matthew Seaman wrote: On 23/12/2012 13:11, Fbsd8 wrote: Ok but as my question asks, how do you configure things to get that to work? I am after the details. You need to run an instance of sshd in each jail. Because sshd defaults to binding to INADDR_ANY, you need to modify the sshd configuration in the host system, so it binds to a specific address, otherwise it will likely block out the jailed sshd's: ListenAddress 192.0.2.1 ListenAddress 2001:DB8::1 ListenAddress 127.0.0.1 ListenAddress ::1 sshd in the jails doesn't need any similar configuration change. You don't need user accounts in your host system for the jail users -- each jail can have it's own passwd file etc. However, it can be useful to make sure that UID numbers for regular users in host and jails don't overlap. Cheers, Matthew What does the remote ssh login command look like? ssh on the host does not use the standard port 22. It uses 2299 instead. this stopped all the ssh break-in attempts. ___ 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: shell script problem
2012/12/23 Polytropon free...@edvax.de On Sun, 23 Dec 2012 10:34:34 +0100, Polytropon wrote: First, the lines with read have to be: cat /foo/bar.txt | while read $LINE1 cat /foo/bar/foo/bar.txt | while read $LINE2 Reason: $LINE1 and $LINE2 will be evaluated here, they are empty string, causing read to throw an error. Excuse me - I made a mistake! Of course those two lines have to be: cat /foo/bar.txt | while read LINE1 and cat /foo/bar/foo/bar.txt | while read LINE2 The $ infront of the variable names have to be removed. The variable _name_, not its content, has to be provided to read as a parameter. The script so far: #!/bin/sh cat foo.txt | while read LINE1 * echo Pid Process: $$* do cat bar.txt | while read LINE2 do if [ $LINE1 = $LINE2 ]; then sw=1 echo Current value of sw is : $sw *ps -ax |grep bar * break fi done echo Value of sw is : $sw if [ $sw = 0 ]; then echo DO SOMETHING! fi sw=0 done Has you can see, pipe make a subshell and sw is lost. Hope this help - (° Dhénin Jean-Jacques / ) 48, rue de la Justice 78300 Poissy ^^ dhe...@gmail.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
Upgrade icu failed
Dear list, I checked the file /usr/ports/UPDATING and there is noted 20121218 for icu to execute the command: portmaster -w -r icu (my system is already on pkgng as described a in the UPDATING file, 20121015). If I execute now portmaster i get the following error message: * === icu-4.8.1.1_1 1/1 === Currently installed version: icu-4.8.1.1_1 === Port directory: /usr/ports/devel/icu === Starting check for build dependencies === Gathering dependency list for devel/icu from ports === Launching child to update pkg-1.0.3_1 to pkg-1.0.4_1 === icu-4.8.1.1_1 1/1 pkg-1.0.3_1 (1/16) === Currently installed version: pkg-1.0.3_1 === Port directory: /usr/ports/ports-mgmt/pkg === Starting check for build dependencies === Gathering dependency list for ports-mgmt/pkg from ports === No dependencies for ports-mgmt/pkg === Cleaning for pkg-1.0.4_1 You are about to convert your system to pkgng while you have ports/packages installed with the old pkg_install tools. You can choose to: - keep pkg_install as the package management system by adding this line to /etc/make.conf: WITHOUT_PKGNG=yes - switch to pkgng: 1) Add WITHOUT_PKGNG to /etc/make.conf 2) Install ports-mgmt/pkg 3) Convert your package database by running pkg2ng 4) Remove WITHOUT_PKGNG from /etc/make.conf *** [pre-everything] Error code 1 Stop in /usr/ports/ports-mgmt/pkg. === make failed for ports-mgmt/pkg === Aborting update === Update for pkg-1.0.3_1 failed === Aborting update Is this a know problem or the there someting in the UPDATING file not mentioned? In /etc/make.conf I have: WITH_PKGNG=yes (as descriped in 20121015) Thanks, Matthias -- Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning. -- Rich Cook ___ 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: Upgrade icu failed
On Sun, 23 Dec 2012 17:16:02 +0100, Matthias Fechner wrote: Dear list, I checked the file /usr/ports/UPDATING and there is noted 20121218 for icu to execute the command: portmaster -w -r icu (my system is already on pkgng as described a in the UPDATING file, 20121015). If I execute now portmaster i get the following error message: * === icu-4.8.1.1_1 1/1 === Currently installed version: icu-4.8.1.1_1 === Port directory: /usr/ports/devel/icu === Starting check for build dependencies === Gathering dependency list for devel/icu from ports === Launching child to update pkg-1.0.3_1 to pkg-1.0.4_1 === icu-4.8.1.1_1 1/1 pkg-1.0.3_1 (1/16) === Currently installed version: pkg-1.0.3_1 === Port directory: /usr/ports/ports-mgmt/pkg === Starting check for build dependencies === Gathering dependency list for ports-mgmt/pkg from ports === No dependencies for ports-mgmt/pkg === Cleaning for pkg-1.0.4_1 You are about to convert your system to pkgng while you have ports/packages installed with the old pkg_install tools. You can choose to: - keep pkg_install as the package management system by adding this line to /etc/make.conf: WITHOUT_PKGNG=yes - switch to pkgng: 1) Add WITHOUT_PKGNG to /etc/make.conf 2) Install ports-mgmt/pkg 3) Convert your package database by running pkg2ng 4) Remove WITHOUT_PKGNG from /etc/make.conf *** [pre-everything] Error code 1 Stop in /usr/ports/ports-mgmt/pkg. === make failed for ports-mgmt/pkg === Aborting update === Update for pkg-1.0.3_1 failed === Aborting update Is this a know problem or the there someting in the UPDATING file not mentioned? In /etc/make.conf I have: WITH_PKGNG=yes (as descriped in 20121015) What's the output from pkg_info? Have you done any other upgrades of ports since migrating to pkgng? ___ 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: Upgrade icu failed
Am 23.12.12 17:29, schrieb Walter Hurry: What's the output from pkg_info? pkg info gives me a full list of all installed ports, pkg_info complains about a lot of corrupted package infos, but i think this is related to, pkg is new and pkg_info is the old tool. Have you done any other upgrades of ports since migrating to pkgng? yes, I did my last upgrade 12.12.2012. Till the note in /usr/ports/UPDATING 20121212. After these steps I executed portmaster -a, which was successfully. Thanks, Matthias -- Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning. -- Rich Cook ___ 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: Upgrade icu failed
On Sun, 23 Dec 2012 17:44:26 +0100, Matthias Fechner wrote: Am 23.12.12 17:29, schrieb Walter Hurry: What's the output from pkg_info? pkg info gives me a full list of all installed ports, pkg_info complains about a lot of corrupted package infos, but i think this is related to, pkg is new and pkg_info is the old tool. Have you done any other upgrades of ports since migrating to pkgng? yes, I did my last upgrade 12.12.2012. Till the note in /usr/ports/UPDATING 20121212. After these steps I executed portmaster -a, which was successfully. pkg_info should be reporting 'no packages installed'. What is the output from pkg2ng? ___ 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[2]: bind 192.168.1.1 to all interfaces
Здравствуйте, Patrick. Вы писали 23 декабря 2012 г., 15:17:43: PL Le Sun, 23 Dec 2012 14:17:47 +0200, PL Eugen Konkov kes-...@yandex.ru a écrit : PL Hello, Or s there any other method to prevent such ilegal DHCP servers on LAN? PL At work we use dhcp_probe PL http://www.net.princeton.edu/software/dhcp_probe/ PL It works quite fine, when someone plug a dhcp server it is detected and PL we shutdown the switch port. PL I don't know if it runs on FreeBSD, it runs on Centos 6. PL Regards. Unfortunately we use unmanaged switches -- С уважением, Eugen mailto:kes-...@yandex.ru ___ 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: shell script problem
2012/12/23 Polytropon free...@edvax.de #!/bin/sh cat foo.txt | while read LINE1 do cat bar.txt | while read LINE2 do if [ $LINE1 = $LINE2 ]; then sw=1 echo Current value of sw is : $sw * ps -l | grep $$ * # see subshell here break fi done * echo Process: $$* # And the parent echo Value of sw is : $sw if [ $sw = 0 ]; then echo DO SOMETHING! fi sw=0 done I suggest : -%- #!/bin/sh cat foo.txt | while read LINE1 do echo 'One' $$tmp cat bar.txt |while read LINE2 do if [ $LINE1 = $LINE2 ]; then echo 'ok' $$tmp break fi done if [ `cat $$tmp` = One ]; then echo One ! fi if [ `cat $$tmp` = ok ]; then echo ok ! fi done Best regards - (° Dhénin Jean-Jacques / ) 48, rue de la Justice 78300 Poissy ^^ dhe...@gmail.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: bind 192.168.1.1 to all interfaces
Eugen Konkov kes-kes at yandex.ru writes: ... So in my vlan I have two DHCP servers. One is mine and second is on that router. Some users get wrong IPs from that router. ... Or s there any other method to prevent such ilegal DHCP servers on LAN? http://www.tcpipguide.com/free/t_DHCPSecurityIssues.htm jb ___ 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
Changes to kern.geom.debugflags?
I had brought up a machine months ago with freebsd-9-stable. I configured it
to boot off of a single disk, with ZFS, expecting I would likely later attach
the other disk to the zpool. I tried to do that today, but find that I can't
write the bootloader to either disk.
Google searching shows what I used last time, that if you get a:
gpart: /dev/da0a: Operation not permitted
you need to run
sysctl kern.geom.debugflags=0x10
But, that doesn't change anything for me now. I can write the boot label
(using gpart bootcode -p /boot/zfsboot ${disk}) to neither disk, getting the
same error in both cases.
Has something changed recently? I'm currently using a Dec 22 9-stable
codebase, built locally with GENERIC kernel.
- 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
Re: how to configure host login account to use jail?
Fbsd8 wrote: Matthew Seaman wrote: On 23/12/2012 13:11, Fbsd8 wrote: Ok but as my question asks, how do you configure things to get that to work? I am after the details. You need to run an instance of sshd in each jail. Because sshd defaults to binding to INADDR_ANY, you need to modify the sshd configuration in the host system, so it binds to a specific address, otherwise it will likely block out the jailed sshd's: ListenAddress 192.0.2.1 ListenAddress 2001:DB8::1 ListenAddress 127.0.0.1 ListenAddress ::1 sshd in the jails doesn't need any similar configuration change. You don't need user accounts in your host system for the jail users -- each jail can have it's own passwd file etc. However, it can be useful to make sure that UID numbers for regular users in host and jails don't overlap. Cheers, Matthew What does the remote ssh login command look like? ssh on the host does not use the standard port 22. It uses 2299 instead. this stopped all the ssh break-in attempts. Have things working all except ssh login to jail from an FBSD box on the lan using native ssh command syntax. This is what I have Have single jail for testing assigned ip address of 10.0.10.20 and it has jail option for auto alias create/remove. From the host I logged into the jail and did these commands This turns on ssh in jail echo sshd_enable=YES /etc/rc.conf Turn off dns check for fast jail start echo UseDNS no /etc/ssh/sshd_config Did adduser to create user account in jail to ssh into. Stop and restart jail for changes to take effect ssh on host has been changed to use port 9922. This stopped all the ssh break-in attempts from the public internet. From putty on xp box on lan can ssh to 10.0.10.2 9922 and login to any user account on host. Using 10.0.10.20 22 login to user account on jail just fine. From another lan box running FBSD can ssh into host user accounts using this command ssh host-user-account-name@10.0.10.2 just fine But I can not figure out syntax for native ssh command to login to jail. This is where in need some help in coding the correct -options and what values to use where. I read the man pages on ssh but its clear as mud to me. ___ 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: Upgrading FreeBSD 8.3 amd64
Hi, I've done the upgrade yesterday. It was a clean 8.3 install, I only set up PPPoE and then run the following commands. # cd /usr/ports/misc/mc make install clean # uname -r 8.3-RELEASE # freebsd-update -r 9.1-RELEASE upgrade # freebsd-update install # shutdown -r now # freebsd-update install # cd /usr/ports/ports-mgmt/portupgrade make install clean # /usr/local/sbin/portupgrade -f ruby # rm /var/db/pkg/pkgdb.db # /usr/local/sbin/portupgrade -f ruby18-bdb # rm /var/db/pkg/pkgdb.db /usr/ports/INDEX-*.db # /usr/local/sbin/portupgrade -af # freebsd-update install # shutdown -r now # freebsd-update IDS outfile.ids This is the content of outfile.ids: Looking up update.FreeBSD.org mirrors... 3 mirrors found. Fetching metadata signature for 9.1-RELEASE from update5.FreeBSD.org... done. Fetching metadata index... done. Fetching 1 metadata patches. done. Applying metadata patches... done. Fetching 1 metadata files... done. Inspecting system... done. /boot/kernel/linker.hints has SHA256 hash ebf78144f48f13af88e5e3752735a709b084d7e6aaee10b05e57f2a117cbc366, but should have SHA256 hash 07b927068b34c4671a323e6a8aaa80ad22dc5fc4b3741b8a4060da1764510350. /etc/group has SHA256 hash 108de8653d4a6d451cc3f018780277d2fe2d770df7a7d984f5160dc753e06678, but should have SHA256 hash d788718c25a04a14cc1818ac2afa8b76a3fd899583691972d0d5127947e3504f. /etc/hosts has SHA256 hash 9684014402be7ecd32b9047181f595d124df6cf6a79dd323b0bd5685dccc2a81, but should have SHA256 hash f795387981b68599c3df984f2ce4ac4a32bf420d57faf1fb55f249b885414d64. /etc/master.passwd has SHA256 hash cd9046284ac3e571eb9f0273f9bfc118e7094e0b9312fd1789f6385e43a26cd3, but should have SHA256 hash 6f1da238cc0a55ed360a215039bc6cb5ce5369d20b8fbceb8a1941c5124e6a4e. /etc/motd has SHA256 hash fa311ce1a08aea0c818d57b904c979941dabb726d1fb2ddaa368102bd6f2fb95, but should have SHA256 hash 98f082efc89da5e887e72bc4dcfa3e5fc8bada9d19db4bdbba9a32692a7c82a7. /etc/passwd has SHA256 hash e4bcb10c66a0440efb58591daadaeec894e75e5392da9e00f3881822d0647a11, but should have SHA256 hash 3135de169a0ff94c0c97aeb525a07ea10e5ed81c9b825e219f7eea8deb97c444. /etc/ppp/ppp.conf has 0755 permissions, but should have 0600 permissions. /etc/ppp/ppp.conf has SHA256 hash 623683de09ab97394221c64ccdec3569aa240854d907a4811f91c9ed92253dd4, but should have SHA256 hash f3dd3d0da252bd47681a261a1f0d46a8fc6ae84ff3cbd34b81b586bc87e49655. /etc/pwd.db has SHA256 hash 62eb1eafbfa8fe718e68bf784e542d09ccdc09012ef43d254ae48e9846a1df4d, but should have SHA256 hash bf86739ee052821992412b61a6673811588c382fa63ab38cc47c1a59305376eb. /etc/shells has SHA256 hash 4c25fb7c79fe5057217a70cfa1c27f41959bb7daa703a94774ec5ac9d29a9266, but should have SHA256 hash beab7e474ee12b051b98889f368bbd490340a908f6f2287f9238e818b830a1fd. /etc/spwd.db has SHA256 hash b25126503c347feb67b76a5f27f44c318a675ddc82f4984b5ec0d2fc5a45fd30, but should have SHA256 hash 1cbfbea78d316e4e8d29f53f0770b8ff1f3a731e993c3ae717f36304715d7a5b. When I run ppp -ddial alice now, I get warnings Bad label in /etc/ppp/ppp.conf (line x) - missing colon, but PPPoE still works. Why are the checksums bad? FWIW snd_hdspe now is available. Regards, Ralf ___ 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
Merry Christmas everyon1
___ 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
