# cat /dev/null | zstd --stdout
/usr/bin/zstd: Undefined symbol "stat@FBSD_1.5"
# freebsd-version -ku
11.1-STABLE
11.1-STABLE
# uname -apKU
FreeBSD FBSDFS 11.1-STABLE FreeBSD 11.1-STABLE r326142 amd64 amd64 1101506
1101506
It was built from source:
# svnlite info /usr/src/
Path:
/etc/rc
+ stty status ^T
/etc/rc: cannot create /dev/null: Operation not supported
+ trap : 2
+ trap 'echo '\''Boot interrupted'\''; exit 1' 3
+ HOME=/
+ PATH=/sbin:/bin:/usr/sbin:/usr/bin
+ export HOME PATH
+ [ '' = autoboot ]
+ autoboot=no
+ _boot=quietstart
+ /sbin/sysctl -n
/dev/null: Operation not supported
+ trap : 2
+ trap 'echo '\''Boot interrupted'\''; exit 1' 3
+ HOME=/
+ PATH=/sbin:/bin:/usr/sbin:/usr/bin
+ export HOME PATH
+ [ '' = autoboot ]
+ autoboot=no
+ _boot=quietstart
+ /sbin/sysctl -n vfs.nfs.diskless_valid
/etc/rc: cannot create /dev/null: Operation
On 2015-07-17 01:41, James Gritton wrote:
On 2015-07-15 13:52, Per olof Ljungmark wrote:
FreeBSD 10.2-PRERELEASE #0 r284949
The jail can be started, but when /etc/rc is executed:
root@mar:/ # sh -x /etc/rc
+ stty status ^T
/etc/rc: cannot create /dev/null: Operation not supported
+ trap
On 2015-07-15 13:52, Per olof Ljungmark wrote:
FreeBSD 10.2-PRERELEASE #0 r284949
The jail can be started, but when /etc/rc is executed:
root@mar:/ # sh -x /etc/rc
+ stty status ^T
/etc/rc: cannot create /dev/null: Operation not supported
+ trap : 2
+ trap 'echo '\''Boot interrupted'\''; exit
FreeBSD 10.2-PRERELEASE #0 r284949
The jail can be started, but when /etc/rc is executed:
root@mar:/ # sh -x /etc/rc
+ stty status ^T
/etc/rc: cannot create /dev/null: Operation not supported
+ trap : 2
+ trap 'echo '\''Boot interrupted'\''; exit 1' 3
+ HOME=/
+ PATH=/sbin:/bin:/usr/sbin:/usr
On Fri, Oct 06, 2006 at 08:36:05PM +0200, Ivan Voras wrote:
Roland Smith wrote:
Are you sure that you have no rulesets?
Yup. The command devfs rule showsets shows nothing. This is on
somewhat old RELENG_6.
Weird. I assume that the system created the rulesets that I see on my
machine,
Brent Casavant wrote:
Not with FreeBSD in particular. However, from time to time I've
run across a piece of software that makes bad assumptions about
deleting various input or output files. If run as root, the
program/library might accidentally delete a character special
device such as /dev
might accidentally delete a character special
device such as /dev/null.
Hmm, that's... inconvenient. I usually support root-almighty thing,
but allowing deletion from dynamically populated /dev seems
counterproductive.
The command 'devfs rule -s 2 apply 100' should fix it, I think.
Roland
Roland Smith wrote:
The command 'devfs rule -s 2 apply 100' should fix it, I think.
?
If I read devfs(8) correctly, this should apply rule 100 of ruleset 2.
Since I have no rulesets or rules, it doesn't work. :)
___
freebsd-stable@freebsd.org
On Fri, Oct 06, 2006 at 06:09:09PM +0200, Ivan Voras wrote:
Roland Smith wrote:
The command 'devfs rule -s 2 apply 100' should fix it, I think.
?
If I read devfs(8) correctly, this should apply rule 100 of ruleset 2.
Since I have no rulesets or rules, it doesn't work. :)
Are you
Roland Smith wrote:
Are you sure that you have no rulesets?
Yup. The command devfs rule showsets shows nothing. This is on
somewhat old RELENG_6.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To
Hi All
From someday I've some very strange thing sometime my /dev/null just
vanish.
Anyone have this problem ?
I'm running FreeBSD RELENG_6
Regards.
--
Albert SHIH
Universite de Paris 7 (Denis DIDEROT)
U.F.R. de Mathematiques.
7 i?me ?tage, plateau D, bureau 10
Heure local/Local time
On Fri, 6 Oct 2006, Albert Shih wrote:
From someday I've some very strange thing sometime my /dev/null just
vanish.
Anyone have this problem ?
Not with FreeBSD in particular. However, from time to time I've
run across a piece of software that makes bad assumptions about
deleting
On Mon, Nov 01, 2004 at 09:19:12AM +0800, Iva Hesy wrote:
I have a gateway running FreeBSD 4.10-p3. Normally, the mode of
/dev/null should be 666, but recently, I find that its mode is changed
to 600 automatically after reboot, I have checked all /etc/rc* and
/usr/local/etc/rc.d/*, but I can't
On Mon, 2004-11-01 at 09:30 -0800, Kris Kennaway wrote:
On Mon, Nov 01, 2004 at 09:19:12AM +0800, Iva Hesy wrote:
I have a gateway running FreeBSD 4.10-p3. Normally, the mode of
/dev/null should be 666, but recently, I find that its mode is changed
to 600 automatically after reboot, I have
On Mon, Nov 01, 2004 at 02:49:48PM -0500, Sven Willenberger wrote:
On Mon, 2004-11-01 at 09:30 -0800, Kris Kennaway wrote:
On Mon, Nov 01, 2004 at 09:19:12AM +0800, Iva Hesy wrote:
I have a gateway running FreeBSD 4.10-p3. Normally, the mode of
/dev/null should be 666, but recently, I
On Mon, 1 Nov 2004, Sven Willenberger wrote:
SW I have a gateway running FreeBSD 4.10-p3. Normally, the mode of
SW /dev/null should be 666, but recently, I find that its mode is changed
SW to 600 automatically after reboot, I have checked all /etc/rc* and
SW /usr/local/etc/rc.d/*, but I
It could be a port doing this at startup, but we still need more
debugging..
Kris
I think that sshd2 does this. because I installed it only recently...
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
No, it just happened after system reboot...:-)
If I chmod it to 666it will re-chmod it to 600 after system reboot.
On Tue, 2 Nov 2004 09:08:15 +0300 (MSK), Dmitry Morozovsky
[EMAIL PROTECTED] wrote:
I remember I stepped into this once or twice in the past. Bad umask at
mergemaster/MAKEDEV time
I have a gateway running FreeBSD 4.10-p3. Normally, the mode of
/dev/null should be 666, but recently, I find that its mode is changed
to 600 automatically after reboot, I have checked all /etc/rc* and
/usr/local/etc/rc.d/*, but I can't get anything that led
Howdy. This question was originally framed as a why doesn't
uptime work for users in 4.4, when it used to in 4.3, but after looking
into things further, it's now a why is /dev/null set to mod 0600? On
a 4.3 system that I have, the perms on dev/null are 666.
I've chmod'ed all
On Sun, 23 Sep 2001 at 17:52:13 -0700, Sean Chittenden wrote:
Howdy. This question was originally framed as a why doesn't
uptime work for users in 4.4, when it used to in 4.3, but after
looking into things further, it's now a why is /dev/null set to mod
0600? On a 4.3 system that I
On Sun, Sep 23, 2001 at 05:52:13PM -0700, Sean Chittenden wrote:
Howdy. This question was originally framed as a why doesn't
uptime work for users in 4.4, when it used to in 4.3, but after looking
into things further, it's now a why is /dev/null set to mod 0600? On
a 4.3 system that I
24 matches
Mail list logo
