Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

freebsd-hackers-digest V5 #752

7 views
Skip to first unread message

owner-freebsd-...@freebsd.org

unread,
Mar 23, 2003, 8:04:25 AM3/23/03
to

freebsd-hackers-digest Sunday, March 23 2003 Volume 05 : Number 752

In this issue:
OID problem with Init?
Re: misc/41772: can't disable keybell [PATCH]
Re: misc/41772: can't disable keybell [PATCH]
RE: jail support for ping, traceroute, etc.. crude hack
Re: OID problem with Init?
Re: ld.so and hard links
Re: Lots of kernel core dumps
Re: Lots of kernel core dumps
Re: boot without user and password
Re: Lots of kernel core dumps
Binary Security Updates
Love from abroad
Re: misc/41772: can't disable keybell [PATCH]
Re: bug in subr_bus.c?
Re: generalized mergemaster(8)
Re: FreeBSD Installation Problems

----------------------------------------------------------------------

Date: 22 Mar 2003 06:52:50 -0600
From: Ben Burke <b...@dubuque365.com>
Subject: OID problem with Init?

Hello Everyone,

I was looking for a good way to run "make installworld" in single-user
mode on a machine which I don't have any kind of remote hands or
serial-console access to. The first thought that came to my head was to
temporarily put the commands at the end of rc.shutdown. I'm not sure if
the machine is still multi-user at that point. Anyway it worked, but on
such a slow machine it didn't complete before init timed out the
shutdown script. So I looked at init...

On line 1576 (spacing changed, comment added for email):
if (
sysctlbyname("kern.shutdown_timeout", &shutdowntimeout, &len, NULL, 0)
== -1 || shutdowntimeout < 2
) shutdowntimeout = DEATH_SCRIPT; /* DEATH_SCRIPT = 120 */

I know that there was a "kern.shutdown_timeout" in FBSD 3, but there
doesn't seem to be one now in FBSD 4.8-RC (from yesterday).

So my questions are:
1. Does init check for this seemingly retired OID on purpose?
2. What's "The Right Way" or even "A Right Way" to do an installworld
on a remote machine?

Thanks in advance!

------------------------------

Date: Sat, 22 Mar 2003 09:42:45 -0500 (EST)
From: John Baldwin <j...@FreeBSD.org>
Subject: Re: misc/41772: can't disable keybell [PATCH]

On 22-Mar-2003 sor...@cydem.org.ua wrote:
>
>> http://www.freebsd.org/cgi/query-pr.cgi?pr=41772
> This appears to be _VERY_ old problem (I don't remember
> it on 2.2.7-RELEASE, though)
> In short: the beeper still produces noises (clicks) when
> shut up with `kbdcontrol -b off`

Using kbdcontrol -b off on my laptop running current does
turn off the sound already. On a stable machine I still
do see the problem. Incidentally, using quiet.off doesn't
shut it up either which is very confusing since quiet sets
SC_QUIET_BELL.

> (as well a this one:
> 'http://www.FreeBSD.org/cgi/query-pr.cgi?pr=kern/44257' -
> it works well for my EIDE controller).

PCI ID's for the ICH4 controllere were committed prior to 4.7.
However, thanks for your submission.

> FreeBSD 4.6.2-RELEASE:
> =======================8<=======================
> --- ./syscons.c.ORIG Fri Mar 21 23:10:05 2003
> +++ ./syscons.c Fri Mar 21 23:10:37 2003
> @@ -3385,6 +3385,9 @@
> if (scp != scp->sc->cur_scp && (scp->sc->flags & SC_QUIET_BELL))
> return;
>
> + if (!(duration && pitch))
> + return;
> +
> if (scp->sc->flags & SC_VISUAL_BELL) {
> if (scp->sc->blink_in_progress)
> return;
> =======================8<=======================

This patch would inadvertently turn off visual bell's if you
set the duration or pitch to zero manually. A better patch
might be:

Index: syscons.c
===================================================================
RCS file: /usr/cvs/src/sys/dev/syscons/syscons.c,v
retrieving revision 1.399
diff -u -r1.399 syscons.c
- --- syscons.c 3 Mar 2003 16:24:44 -0000 1.399
+++ syscons.c 22 Mar 2003 14:38:58 -0000
@@ -3547,7 +3547,7 @@
if (scp != scp->sc->cur_scp)
scp->sc->blink_in_progress += 2;
blink_screen(scp->sc->cur_scp);
- - } else {
+ } else if (duration != 0 && pitch != 0) {
if (scp != scp->sc->cur_scp)
pitch *= 2;
sysbeep(pitch, duration);

Can you verify that this fix works for you?

- --

John Baldwin <j...@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/

------------------------------

Date: Sat, 22 Mar 2003 09:17:33 -0700
From: <sor...@cydem.org.ua>
Subject: Re: misc/41772: can't disable keybell [PATCH]

> Incidentally, using quiet.off doesn't
> shut it up either which is very confusing since quiet sets
> SC_QUIET_BELL.

it does, actually
the `man kbdcontrol` doesn't say that it also checks to see
if the beeping console is not current:

if (scp != scp->sc->cur_scp && (scp->sc->flags & SC_QUIET_BELL))

> + } else if (duration != 0 && pitch != 0) {

why using "if (duration != 0 && pitch != 0)" is
better than "if (!(duration && pitch))"?

> Can you verify that this fix works for you?

OK, I'll check it after work

22.03.2003; 09:09:34
[SorAlx] http://cydem.org.ua/

------------------------------

Date: Sat, 22 Mar 2003 11:19:52 -0800
From: "Mooneer Salem" <moo...@translator.cx>
Subject: RE: jail support for ping, traceroute, etc.. crude hack

Hello,

Another possibility would be to deny access to IP_FW_* and IP_DUMMYNET_*
in getsockopt(), or at least limit access to the IP addresses the jail
is assigned (there's a struct thread pointer in the struct sockopt that it
receives, meaning we can get to ucred and the jail's struct prison pointer).
This should mitigate some of the security concerns.

Thanks,

- --
Mooneer Salem
GPLTrans: http://www.translator.cx/
lifeafterking.org: http://www.lifeafterking.org/

- -----Original Message-----
From: owner-free...@FreeBSD.ORG
[mailto:owner-free...@FreeBSD.ORG]On Behalf Of "."@babolo.ru
Sent: Monday, March 17, 2003 2:57 AM
To: Peter Jeremy
Cc: moo...@translator.cx; freebsd...@FreeBSD.ORG
Subject: Re: jail support for ping, traceroute, etc.. crude hack


> On Mon, Mar 17, 2003 at 10:06:27AM +0300, "."@babolo.ru wrote:
> >It is time to invent "ping socket" and "traceroute socket"
> >in addition to tcp, udp, divert so on?
>
> Whilst this might seem nice, actually implementing so that it is
> both useful and safe is not easy.
>
> For a "ping socket", this is reasonably easy if all you want is the
> ability to send "ICMP ECHO REQUEST" packets and receive any "ICMP ECHO
> REPLY" packets associated with previous request packets. It's not
> totally trivial because the kernel has to keep the state for outgoing
> packets to ensure that only the correct incoming packets are
> forwarded. (This is a security issue - you don't want somone finding
> out hosts someone outside that jail is pinging). Remember to allow
> for multiple responses to a single request and for long delays. You
> might also want to implement resource restrictions to prevent someone
> flooding the system with request packets.
Not so easy to do but easy understandable for me.

> A "traceroute socket" is harder: There's no "ICMP TRACEROUTE" packet.
> Instead, traceroute(8) sends outgoing IP packets with varying TTL
> sizes and monitors incoming ICMP looking for check for "HOST
> UNREACHABLE - TIME EXCEEDED IN TRANSIT" packets. Again, the kernel
> would need to validate the incoming packets against outgoing packets.
"traceroute socket" is just a curiosity.
It seems to me better use UDP socket with some controls
and "ping socket" from above.
But way to obtain "ping socket" coupled with UDP socket
is above my brain.

Or may be more common way? Semiraw socket
for ability send some classes of IP packets
and seceive all induced ICMP
ICMP ECHO REQUEST, any UDP and other protocols
exept TCP with correct source IP address
is probably secure enough for use by root in jail.

> In both cases, you also need to work out how to handle other random
> ICMP packets that be received as a result of the outgoing packets.

------------------------------

Date: Sat, 22 Mar 2003 15:55:33 -0600
From: Dan Nelson <dne...@allantgroup.com>
Subject: Re: OID problem with Init?

In the last episode (Mar 22), Ben Burke said:
> So my questions are:
> 1. Does init check for this seemingly retired OID on purpose?
> 2. What's "The Right Way" or even "A Right Way" to do an installworld
> on a remote machine?

Serial console :)

Otherwise, you can just installworld in multiuser mode, and reboot
after it's done. The advise to install in single-user mode is just so
that people logged in while you install don't have problems due to
binaries getting installed before required libraries, etc.

- --
Dan Nelson
dne...@allantgroup.com

------------------------------

Date: Sun, 23 Mar 2003 01:59:44 +0300 (MSK)
From: "."@babolo.ru
Subject: Re: ld.so and hard links

> On Sat, 2003-03-22 at 07:30, Terry Lambert wrote:
> > You could potentially save a lot of memory. *However*. You may
> > not want to do this, since you are defeating priviledge seperation
> > that is what made you want to use jails in the first place.
>
> There's a Linux Jail like thing called vserver, it has a feature where
> you hardlink a whole bunch of stuff for different jails (it has tools
> for building a set of jails from a given tree). It does a copy on write
> for any of these hardlinked files so you don't get the security issue.
>
> No idea if it's possible to implement something like that for a jail :)
schg flag is sufficient to do impossible
hardlinked files change in jail IMHO
Or I forgot something?

------------------------------

Date: Sun, 23 Mar 2003 00:10:38 +0100
From: Daniela <d...@liwest.at>
Subject: Re: Lots of kernel core dumps

> I know, but 5.0-RELEASE was
>
> a) A work-in-progress, not a perfect, bug-free release
>
> b) A snapshot of 5.0-CURRENT
>
> You read the 5.0 Early Adopter's Guide, right? Bugs like this are
> expected at this stage in the development process, and if you
> encounter them then you need to either give up on 5.x and go back to
> 4.x-STABLE, or upgrade to 5.0-CURRENT if they are already fixed there.
>
> Kris

Yes, I read the Early Adopter's Guide.
Is there any way to solve this without upgrading to -current?
I want a stable server, of course, but I still want to help the FreeBSD f=
olks=20
to make 5.0 the best release ever. This requires testing to be done.

Daniela

------------------------------

Date: Sat, 22 Mar 2003 15:22:32 -0800
From: Kris Kennaway <kr...@obsecurity.org>
Subject: Re: Lots of kernel core dumps

- --SUOF0GtieIMvvwua
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Sun, Mar 23, 2003 at 12:10:38AM +0100, Daniela wrote:

> Yes, I read the Early Adopter's Guide.
> Is there any way to solve this without upgrading to -current?

If you wanted to dig through the CVS commit logs to find the change
that fixed this problem (this may be difficult), you could back-port
it, but other than that, not really.

Kris

- --SUOF0GtieIMvvwua
Content-Type: application/pgp-signature
Content-Disposition: inline

- -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)

iD8DBQE+fPA4Wry0BWjoQKURAtHBAJ42MoQmOq/8q7XwsupzOGAQ0vMfVwCfT+AT
hYrpS4F+jp2grmJgSRVOw9s=
=lhrr
- -----END PGP SIGNATURE-----

- --SUOF0GtieIMvvwua--

------------------------------

Date: Sun, 23 Mar 2003 00:36:01 +0100
From: Willem van Engen <wve...@stack.nl>
Subject: Re: boot without user and password

There is also the autologin (al) option in gettytab(5) that logs in a user
instead of prompting for a username/password. You can run X from his .profile

btw. isn't this more appropriate for freebsd-questions instead of -hackers?

On Thu, 20 Mar 2003 16:18:43 +0000
"Emilio Manuel" <curio...@hotmail.com> wrote:

> I want to know how a FreeBSD box, just after finish booting process,
> can start automatically a session with a predeterminate user without
> doing the normal login process (ie, without typing user and password).
>
> I wan to do this under Xwindows because I pretend to use this box as a
> "dumb X terminal" that can display messages send from another UNIX
> machine.
>
> Security themes don't bother me, cause I use this box in a small local
>
> network without conflictive users.
>
> Thank you in advance.

------------------------------

Date: Sat, 22 Mar 2003 17:37:25 -0600
From: Anti <fea...@attbi.com>
Subject: Re: Lots of kernel core dumps

On Sun, 23 Mar 2003 00:10:38 +0100
Daniela <d...@liwest.at> wrote:

> > I know, but 5.0-RELEASE was
> >
> > a) A work-in-progress, not a perfect, bug-free release
> >
> > b) A snapshot of 5.0-CURRENT
> >
> > You read the 5.0 Early Adopter's Guide, right? Bugs like this are
> > expected at this stage in the development process, and if you
> > encounter them then you need to either give up on 5.x and go back to
> > 4.x-STABLE, or upgrade to 5.0-CURRENT if they are already fixed there.
> >
> > Kris
>
> Yes, I read the Early Adopter's Guide.
> Is there any way to solve this without upgrading to -current?
> I want a stable server, of course, but I still want to help the FreeBSD folks
> to make 5.0 the best release ever. This requires testing to be done.
>
> Daniela


current isn't really any less stable than 5.0 release, likely more stable...

------------------------------

Date: Sun, 23 Mar 2003 03:47:07 +0000
From: Colin Percival <colin.p...@wadham.ox.ac.uk>
Subject: Binary Security Updates

Ok, I've decided that my binary security updates code is now
release-worthy. Right now I'm only building updates for 4.7-RELEASE; as
soon as 4.8-RELEASE comes out I'll start building updates for that as well.
Note that this code only works properly if you performed a binary
install of the -RELEASE and have not recompiled anything (ie, haven't
applied any updates since October), so theoretically nobody should be using
this until after 4.8 is released.
Everything is at http://www.daemonology.net/freebsd-update/ including a
portified version of the client and the resulting package. MD5 hashes are
dac0f4bdf3d23b642bcbbac0e544821e, 12f69c9d0a2bf1f5278e49f0a4821aa7,
b96bfc6bffcbfa18130250e36e6109d6, and 227819b9403a6f727566bd6ad5a79684 for
server, client, client port, and client package respectively.

Feedback is welcome. ;)

Colin Percival
PS. This is probably of interest to people reading stable@ as well, but
that would apparently constitute excessive cross-posting.

------------------------------

Date: Sat, 22 Mar 2003 22:03:20 01600
From: "Elfriede" <ii...@home.se>
Subject: Love from abroad

<html>
<body
<br>
Hi, Elfriede he<!--8482113022835-->r<!--84821130227658345446-->e,<br>
<br><!-- u ygobey mzhj-->
<a href=3D"http://www.myrussianlover.com/?oc=3D2390">A ni<!--8482113022800-=
- ->ce lady wa<!--8482113022858801881-->nts to corr<!--84821130224056-->espon=
d with you.<!----> che<!--8482113022263755-->ck her o<!--848211302245443558=
32-->ut</a><br><BR>
<br>
<br>
<a href=3D"http://www.myrussianlover.com/remove/?oc=3D23900">Le<!--84821130=
2230727661-->t me kn<!--848211302204-->ow an<!--8482113022568-->d I won't w=
ri<!--848211302227060712-->te y<!--8482113022470500-->ou again.<!----> Than=
<!--84821130224604882-->ks</a><br><BR>
<br>
<br>
</a></div></body></html>
</body>
</html>

------------------------------

Date: Sat, 22 Mar 2003 23:14:16 -0700
From: <sor...@cydem.org.ua>
Subject: Re: misc/41772: can't disable keybell [PATCH]

> Using kbdcontrol -b off on my laptop running current does
> turn off the sound already.

I tested `kbdcontrol -b off` on FreeBSD 5.0-RELEASE, and it
still did not turn off the beeper. I have also checked
'syscons.c', v. 1.399 ([0]), and foud only one change
concerning keybell:
'if (cold || shutdown_in_progress || !enable_bell)' -
('enable_bell' added, which must be "hw.syscons.bell"
sysctl var), that enables to turn the keybell off globally,
but not for separate vtys.

> Incidentally, using quiet.off doesn't
> shut it up either which is very confusing since quiet sets
> SC_QUIET_BELL.

I tested this again, and it works fine:

`kbdcontrol -b quiet.normal`
`(sleep 2;echo -e "\x07";sleep 2)&`
When, after executing this command, i quickly switch to
another vty, I hear no bell; when I stay on the same vty,
I can hear the bell.

> PCI ID's for the ICH4 controllere were committed prior to 4.7.

good, found my controller's ID in the latest CVSweb ATA-PCI tree

> This patch would inadvertently turn off visual bell's if you
> set the duration or pitch to zero manually. A better patch
> might be:
>
> Index: syscons.c
> ===================================================================
> RCS file: /usr/cvs/src/sys/dev/syscons/syscons.c,v
> retrieving revision 1.399
> diff -u -r1.399 syscons.c
> --- syscons.c 3 Mar 2003 16:24:44 -0000 1.399
> +++ syscons.c 22 Mar 2003 14:38:58 -0000
> @@ -3547,7 +3547,7 @@
> if (scp != scp->sc->cur_scp)
> scp->sc->blink_in_progress += 2;
> blink_screen(scp->sc->cur_scp);
> - } else {
> + } else if (duration != 0 && pitch != 0) {
> if (scp != scp->sc->cur_scp)
> pitch *= 2;
> sysbeep(pitch, duration);
>
> Can you verify that this fix works for you?

yes, it does
but, I think, this may produce faster code:
+ } else if (duration && pitch) {

I also found couple more problems:

00.
`kbdcontrol -b 128.800`
`(sleep 2;echo -e "\x07";sleep 2)&`
If I stay on the same vty, I hear 800Hz bell, if I switch
to another vty, I hear ~400Hz bell.

`kbdcontrol -b normal`
`(sleep 2;echo -e "\x07";sleep 2)&`
If I stay on the same vty, I hear normal bell, if I switch
to another vty, I hear a bell with pitch twice as _high_.

01.
`kbdcontrol quiet.115.400` - won't set SC_QUIET_BELL flag


[0]
(http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/root/src \
/src/sys/dev/syscons/syscons.c?rev=1.399&content-type=text/plain)

22.03.2003; 23:12:44
[SorAlx] http://cydem.org.ua/

------------------------------

Date: Sun, 23 Mar 2003 17:55:07 +0700 (ICT)
From: John-Mark Gurney <gurn...@resnet.uoregon.edu>
Subject: Re: bug in subr_bus.c?

On Fri, 21 Mar 2003, Matthew N. Dodd wrote:

> On Fri, 21 Mar 2003, John-Mark Gurney wrote:
> > So, the driver can:
> > a) delete it's own children, but if it gets removed via
> > device_delete_child, this work is already down for you.
>
> If you create children then you're going to be involved in removing them.
>
> There are helper routines that simplify some operations but I don't
> believe any changes to subr_bus.c are needed.

I finally got it working.. I'm not sure exactly what I did, but I can
load/unload the driver w/o crashing the machine...

The bus code could use some locking in it... like you can't delete_child
from child_detache... and/or better docs on how to handle children... I'm
not even sure how I was doing things wrong, but I think it might of been
problems with my code not calling bus_generic_detach before calling
device_child_delete...

Hmmm.. I'm still not sure exactly why things started behaving properly...
I know a few times I was trying to delete a device that was in the process
of being detached (which of course would try to detach it again)...

Quite confusing.. :(

Thanks for your help though.

later.

John-Mark

------------------------------

Date: Sun, 23 Mar 2003 12:06:06 +0100
From: Michael Ranner <mra...@inode.at>
Subject: Re: generalized mergemaster(8)

- --Boundary-00=_eUZf+bj/Sm49djI
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Content-Disposition: inline

Am Freitag, 21. März 2003 20:27 schrieb Garance A Drosihn:
> >
> > /var/tmp/temproot/etc/rc.d/ and /etc/rc.d/ have 17 differing files.
> > (I)nstall, (D)elete, or (R)ecursively examine? [R]
> >
> >Then I could hit 'I' and update all of /etc/rc.d at once.
>
> At times I've asked Doug about some kind of pattern-support in
> ~/.mergemasterrc, where the user could specify filename-patterns
> of files where they want the default action to be "install"
> instead of "leave for later". There are pros and cons with that
> idea, but that's what I was thinking of for the directories you
> describe.
>
> Doug has suggested that people could maybe do things with the
> MM_PRE_COMPARE_SCRIPT, for special processing like this.

I have a small patch for pattern-support in ~/.mergemasterrc and
already sent my ideas to Doug, but he said "It could/should
be done with MM_PRE_COMPARE_SCRIPT" to me.

Regards

- --
/\/\ichael Ranner

mra...@jawa.at - mra...@bitonline.cc - webm...@mariazell.at
- ----------------------------------------------------------------------
JAWA Management Software GmbH - http://www.jawa.at/
Liebenauer Hauptstrasse 2oo - A-8041 Graz
Tel +43 316 403274 21 - Fax +43 316 403274 10
- ----------------------------------------------------------------------
Mariazell Online - http://www.mariazell.at/
- ----------------------------------------------------------------------

- -----BEGIN GEEK CODE BLOCK-----
GIT/CS/AT dx(-) s+:(++:) a- C++ UBLVS++++$ P++>+++$ L-(+)$ E---
W+++$ N+(++) o-- K- w--()$ O-(--) M@ V-(--) PS+>++ PE(-) Y+ PGP(-)
t+ 5+ X+++(++++) R* tv++ b+(++) DI++ D-(--) G- e h--(*) r++ y?
- ------END GEEK CODE BLOCK------

- --Boundary-00=_eUZf+bj/Sm49djI
Content-Type: text/x-diff;
charset="iso-8859-1";
name="mergemaster.patch"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="mergemaster.patch"

*** mergemaster.orig Wed Mar 5 16:35:54 2003
- --- mergemaster Thu Mar 6 15:47:38 2003
***************
*** 106,115 ****
diff_loop () {

HANDLE_COMPFILE=v

while [ "${HANDLE_COMPFILE}" = "v" -o "${HANDLE_COMPFILE}" = "V" -o \
"${HANDLE_COMPFILE}" = "NOT V" ]; do
! if [ -f "${DESTDIR}${COMPFILE#.}" -a -f "${COMPFILE}" ]; then
if [ "${HANDLE_COMPFILE}" = "v" -o "${HANDLE_COMPFILE}" = "V" ]; then
echo ''
echo ' ====================================================================== '
- --- 106,133 ----
diff_loop () {

HANDLE_COMPFILE=v
+ AUTO_INSTALL_FILE=n
+
+ case "${AUTO_INSTALL}" in
+ [Yy][Ee][Ss])
+ set -f
+ for each in $AUTO_INSTALL_FILES
+ do
+ if expr "$COMPFILE" : ".$each\$" >/dev/null; then
+ AUTO_INSTALL_FILE=y
+ break
+ fi
+ done
+ set +f
+ ;;
+ *)
+ ;;
+ esac

while [ "${HANDLE_COMPFILE}" = "v" -o "${HANDLE_COMPFILE}" = "V" -o \
"${HANDLE_COMPFILE}" = "NOT V" ]; do
! if [ -f "${DESTDIR}${COMPFILE#.}" -a -f "${COMPFILE}" -a \
! "$AUTO_INSTALL_FILE" = "n" ]; then
if [ "${HANDLE_COMPFILE}" = "v" -o "${HANDLE_COMPFILE}" = "V" ]; then
echo ''
echo ' ====================================================================== '
***************
*** 124,130 ****
fi
else
echo ''
! echo " *** There is no installed version of ${COMPFILE}"
echo ''
case "${AUTO_INSTALL}" in
[Yy][Ee][Ss])
- --- 142,152 ----
fi
else
echo ''
! if [ "$AUTO_INSTALL_FILE" = "y" ]; then
! echo " *** Automatic installation of ${COMPFILE}"
! else
! echo " *** There is no installed version of ${COMPFILE}"
! fi
echo ''
case "${AUTO_INSTALL}" in
[Yy][Ee][Ss])

- --Boundary-00=_eUZf+bj/Sm49djI
Content-Type: text/plain;
charset="iso-8859-1";
name="mergemaster.rc"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="mergemaster.rc"

AUTO_INSTALL_FILES="/etc/periodic/.*"

- --Boundary-00=_eUZf+bj/Sm49djI--

------------------------------

Date: Sun, 23 Mar 2003 21:00:41 +0800
From: "Sukhbinder Singh" <sukhb...@hotmail.com>
Subject: Re: FreeBSD Installation Problems

Now I am using a new mailer not the one from hotmail, because i am not able
to edit the settings in the hotmail mailer to not sent html mail. i think
hotmail mailer is made to mail html mails. if anyone have an idea of how to
not mail html mails from hotmail, i mean if anyone knows of how to stop or
configure hotmail not to mail html mails please let me know of how to do
this.

anyway i hope this mailer do not mail html mails. if it is does please let
me know. however now getting back to the free bsd problem can anyone give a
little help in troubleshooting this problem. now when i try to setup freebsd
using floopy disk method it is giving an error message like " No floppy
device found consult the hardware in doc". The FTP now seems to work but
however this gives a message like " Could not open FTP connection to
ftp.freebsd.org: undefined error: 0" how can these 2 error message be
solved. Any help will help.

thanks


- ----- Original Message -----
From: taxman <tax...@acd.net>
To: Sukhbinder Singh <sukhb...@hotmail.com>
Sent: Sunday, March 23, 2003 11:10 AM
Subject: Re: FreeBSD Installation Problems


>
> really, why do you persist in sending html mail to this list? It is
nearly
> unreadable on most peoples mail readers. So you will mostly get ignored.
>
> To answer this question we need to know more details about what you've
tried
> and what exact step in the process it fails at. Please send that in text
> only. Modify your hotmail preferences to do that. Thank you
>
> Tim
>
>
> On Saturday 22 March 2003 08:48 am, Sukhbinder Singh wrote:
> > <html><div style='background-color:'><DIV>Dear Sir,</DIV>
> > <DIV>&nbsp;</DIV>
> > <DIV>&nbsp;&nbsp; I am trying to install FreeBSD into my personal
computer.
> > I am using the FTP installation method using the standard installation.
> > When I try to start the FTP installation I get message such as :-
Warning:
> > no /dev/tun0 device. PPP will not work !.&nbsp;Unable to start PPP. This
> > installation cannot be&nbsp;used. </DIV> <DIV>&nbsp;</DIV>
> > <DIV>Can you please help me to resolve this problem.</DIV>
> > <DIV>&nbsp;</DIV>
> > <DIV>Thanks,</DIV>
> > <DIV>&nbsp;</DIV>
> > <DIV>&nbsp;</DIV></div><br clear=all><hr>MSN 8 with <a
> > href="http://g.msn.com/8HMRENUS/2740">e-mail virus protection service:
</a>
> > 2 months FREE*</html>
> >
> > To Unsubscribe: send mail to majo...@FreeBSD.org
> > with "unsubscribe freebsd-questions" in the body of the message
>
>

------------------------------

End of freebsd-hackers-digest V5 #752
*************************************

To Unsubscribe: send mail to majo...@FreeBSD.org
with unsubscribe freebsd-hackers-digest in the body of the message

0 new messages