dmesg -a lines' explanation? NEWBIE

Christopher Nehren apeiron+usenet at coitusmentis.info
Sat Mar 26 22:18:34 PST 2005


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2005-03-27, David Armour scribbled these
curious markings:
> <snippage>

Ditto.

> chmod: 
> #permissions: No such file or directory
>
> chmod: 
> are: No such file or directory
>
> chmod: 
> set: No such file or directory
>
> chmod: 
> properly: No such file or directory
>
> chmod: 
> at: No such file or directory
>
> chmod: 
> boot: No such file or directory

Looks like you've got a runaway quote somewhere in your startup scripts.
The #permissions part makes me think that you have a line that you
thought would read something like this:
chmod $filename #permissions are set properly at boot

but, for whatever reason, the shell didn't see the # indicating the
comment -- perhaps because it's inside a quote that isn't closed
properly. I'm not familiar with your setup, but in either case I'd grep
through /etc and /usr/local/etc (maybe even /usr/X11R6/etc) for that
string, and see what I found.

Best Regards,
Christopher Nehren
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (FreeBSD)

iD8DBQFCRlAqk/lo7zvzJioRAiBHAKCrLVQbgP6TOdY6SkRpJk1eWLmQZwCgnhby
cTdP7K+wIWt8BAtVzqi6JMU=
=XP45
-----END PGP SIGNATURE-----

-- 
I abhor a system designed for the "user", if that word is a coded
pejorative meaning "stupid and unsophisticated". -- Ken Thompson
If you ask the wrong questions, you get answers like "42" and "God".
Unix is user friendly. However, it isn't idiot friendly.



More information about the freebsd-questions mailing list