Gentoo notebook: Aggiornamento in difficoltà

Sistemi operativi Linux e software open source
Avatar utente
Zievatron
Messaggi: 1657
Iscritto il: mercoledì 21 dicembre 2011, 23:49

Re: Gentoo notebook: Aggiornamento in difficoltà

Messaggio da Zievatron »

Eseguito.
Non mi sembra sia cambiato niente:

Codice: Seleziona tutto

darkstar / # find / -name *.log
/var/log/portage/elog/summary.log
/var/log/emerge.log
/var/log/emerge-fetch.log
darkstar / # cat /etc/conf.d/rc
cat: /etc/conf.d/rc: File o directory non esistente
Zievatron

Avatar utente
conoscenza
Messaggi: 3821
Iscritto il: venerdì 2 dicembre 2011, 23:27
Località: Parma

Re: Gentoo notebook: Aggiornamento in difficoltà

Messaggio da conoscenza »

quello che ti ho fatto fare serviva solo per attivare il log del boot.
hai riavviato Gentoo?
se si,... e non si è avviato,... postami:
cat /var/log/rc.log
..ovviamente di gentoo chrootato!
Sono allergico a mele morsicate e a finestre con tende.

Segnalate qui le vostre offerte di smartphone e tablet!!!

Avatar utente
Zievatron
Messaggi: 1657
Iscritto il: mercoledì 21 dicembre 2011, 23:49

Re: Gentoo notebook: Aggiornamento in difficoltà

Messaggio da Zievatron »

conoscenza ha scritto:quello che ti ho fatto fare serviva solo per attivare il log del boot.
hai riavviato Gentoo?
se si,... e non si è avviato,... postami:
cat /var/log/rc.log
..ovviamente di gentoo chrootato!
Ma sì che l'ho avviato.
Ha prodotto ancora il kernel panic e, come ti ho mostrato prima con la ricerca dei .log, non è comparso nessun /var/log/rc.log.

Infatti, provando a cercalo specificamente:

Codice: Seleziona tutto

darkstar / # cat /var/log/rc.log
cat: /var/log/rc.log: File o directory non esistente
Zievatron

Avatar utente
conoscenza
Messaggi: 3821
Iscritto il: venerdì 2 dicembre 2011, 23:27
Località: Parma

Re: Gentoo notebook: Aggiornamento in difficoltà

Messaggio da conoscenza »

mi mostri di nuovo:
cat /etc/rc.conf

...strano...
Sono allergico a mele morsicate e a finestre con tende.

Segnalate qui le vostre offerte di smartphone e tablet!!!

Avatar utente
Zievatron
Messaggi: 1657
Iscritto il: mercoledì 21 dicembre 2011, 23:49

Re: Gentoo notebook: Aggiornamento in difficoltà

Messaggio da Zievatron »

Codice: Seleziona tutto

darkstar / # cat /etc/rc.conf
# Global OpenRC configuration settings

# Set rc_interactive to "YES" and you'll be able to press the I key during
# boot so you can choose to start specific services. Set to "NO" to disable
# this feature.
#rc_interactive="YES"

# If we need to drop to a shell, you can specify it here.
# If not specified we use $SHELL, otherwise the one specified in /etc/passwd,
# otherwise /bin/sh
# Linux users could specify /sbin/sulogin
rc_shell=/sbin/sulogin

# Do we allow any started service in the runlevel to satisfy the dependency
# or do we want all of them regardless of state? For example, if net.eth0
# and net.eth1 are in the default runlevel then with rc_depend_strict="NO"
# both will be started, but services that depend on 'net' will work if either
# one comes up. With rc_depend_strict="YES" we would require them both to
# come up.
#rc_depend_strict="YES"

# rc_hotplug is a list of services that we allow to be hotplugged.
# By default we do not allow hotplugging.
# A hotplugged service is one started by a dynamic dev manager when a matching
# hardware device is found.
# This service is intrinsically included in the boot runlevel.
# To disable services, prefix with a !
# Example - rc_hotplug="net.wlan !net.*"
# This allows net.wlan and any service not matching net.* to be plugged.
# Example - rc_hotplug="*"
# This allows all services to be hotplugged
#rc_hotplug="*"

# rc_logger launches a logging daemon to log the entire rc process to
# /var/log/rc.log
# NOTE: Linux systems require the devfs service to be started before
# logging can take place and as such cannot log the sysinit runlevel.
rc_logger="YES"

# Through rc_log_path you can specify a custom log file.
# The default value is: /var/log/rc.log
rc_log_path="/var/log/rc.log"

# By default we filter the environment for our running scripts. To allow other
# variables through, add them here. Use a * to allow all variables through.
#rc_env_allow="VAR1 VAR2"

# By default we assume that all daemons will start correctly.
# However, some do not - a classic example is that they fork and return 0 AND
# then child barfs on a configuration error. Or the daemon has a bug and the
# child crashes. You can set the number of milliseconds start-stop-daemon
# waits to check that the daemon is still running after starting here.
# The default is 0 - no checking.
#rc_start_wait=100

# rc_nostop is a list of services which will not stop when changing runlevels.
# This still allows the service itself to be stopped when called directly.
#rc_nostop=""

# rc will attempt to start crashed services by default.
# However, it will not stop them by default as that could bring down other
# critical services.
#rc_crashed_stop=NO
#rc_crashed_start=YES

##############################################################################
# MISC CONFIGURATION VARIABLES
# There variables are shared between many init scripts

# Set unicode to YES to turn on unicode support for keyboards and screens.
unicode="YES"

# Below is the default list of network fstypes.
#
# afs cifs coda davfs fuse fuse.sshfs gfs glusterfs lustre ncpfs
# nfs nfs4 ocfs2 shfs smbfs
#
# If you would like to add to this list, you can do so by adding your
# own fstypes to the following variable.
#extra_net_fs_list=""

##############################################################################
# SERVICE CONFIGURATION VARIABLES
# These variables are documented here, but should be configured in
# /etc/conf.d/foo for service foo and NOT enabled here unless you
# really want them to work on a global basis.

# Some daemons are started and stopped via start-stop-daemon.
# We can set some things on a per service basis, like the nicelevel.
#export SSD_NICELEVEL="-19"

# Pass ulimit parameters
#rc_ulimit="-u 30"

# It's possible to define extra dependencies for services like so
#rc_config="/etc/foo"
#rc_need="openvpn"
#rc_use="net.eth0"
#rc_after="clock"
#rc_before="local"
#rc_provide="!net"

# You can also enable the above commands here for each service. Below is an
# example for service foo.
#rc_foo_config="/etc/foo"
#rc_foo_need="openvpn"
#rc_foo_after="clock"

# You can also remove dependencies.
# This is mainly used for saying which servies do NOT provide net.
#rc_net_tap0_provide="!net"

##############################################################################
# LINUX SPECIFIC OPTIONS

# This is the subsystem type. Valid options on Linux:
# ""        - nothing special
# "lxc"     - Linux Containers
# "openvz"  - Linux OpenVZ
# "prefix"  - Prefix
# "uml"     - Usermode Linux
# "vserver" - Linux vserver
# "xen0"    - Xen0 Domain
# "xenU"    - XenU Domain
# If this is commented out, automatic detection will be attempted.
# Note that autodetection will not work in a prefix environment or in a
# linux container.
#
# This should be set to the value representing the environment this file is
# PRESENTLY in, not the virtualization the environment is capable of.
#rc_sys=""

# This is the number of tty's used in most of the rc-scripts (like
# consolefont, numlock, etc ...)
rc_tty_number=12
Zievatron

Avatar utente
conoscenza
Messaggi: 3821
Iscritto il: venerdì 2 dicembre 2011, 23:27
Località: Parma

Re: Gentoo notebook: Aggiornamento in difficoltà

Messaggio da conoscenza »

Ti manca, probabilemte, il sevizio che attivi il log.

Fai vedere:
emerge -p sys-fs/devfsd
ed anche
emerge -p sys-fs/udev
Sono allergico a mele morsicate e a finestre con tende.

Segnalate qui le vostre offerte di smartphone e tablet!!!

Avatar utente
Zievatron
Messaggi: 1657
Iscritto il: mercoledì 21 dicembre 2011, 23:49

Re: Gentoo notebook: Aggiornamento in difficoltà

Messaggio da Zievatron »

Codice: Seleziona tutto

darkstar / # emerge -p sys-fs/devfsd

These are the packages that would be merged, in order:

Calculating dependencies... done!

!!! All ebuilds that could satisfy "sys-fs/devfsd" have been masked.
!!! One of the following masked packages is required to complete your request:
- sys-fs/devfsd-1.3.25-r9::gentoo (masked by: missing keyword)

For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.

darkstar / # emerge -p sys-fs/udev

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R    ] sys-fs/udev-171-r6 
Zievatron

Avatar utente
conoscenza
Messaggi: 3821
Iscritto il: venerdì 2 dicembre 2011, 23:27
Località: Parma

Re: Gentoo notebook: Aggiornamento in difficoltà

Messaggio da conoscenza »

ok.
echo "sys-fs/devfsd **" >> /etc/portage/package.keywords

poi riportami tutta la parte finale di:
emerge sys-fs/devfsd
Sono allergico a mele morsicate e a finestre con tende.

Segnalate qui le vostre offerte di smartphone e tablet!!!

Avatar utente
Zievatron
Messaggi: 1657
Iscritto il: mercoledì 21 dicembre 2011, 23:49

Re: Gentoo notebook: Aggiornamento in difficoltà

Messaggio da Zievatron »

Codice: Seleziona tutto

darkstar / # emerge sys-fs/devfsd
Calculating dependencies... done!

!!! All ebuilds that could satisfy "<sys-kernel/linux-headers-2.6.18" have been masked.
!!! One of the following masked packages is required to complete your request:
- sys-kernel/linux-headers-2.4.36::gentoo (masked by: missing keyword)
- sys-kernel/linux-headers-2.4.33.3::gentoo (masked by: missing keyword)

(dependency required by "sys-fs/devfsd-1.3.25-r9" [ebuild])
(dependency required by "sys-fs/devfsd" [argument])
For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.
Zievatron

Avatar utente
conoscenza
Messaggi: 3821
Iscritto il: venerdì 2 dicembre 2011, 23:27
Località: Parma

Re: Gentoo notebook: Aggiornamento in difficoltà

Messaggio da conoscenza »

echo "sys-kernel/linux-headers-2.4.36 **" >> /etc/portage/package.keywords

poi ridai:
emerge sys-fs/devfsd
mostrami sempre il finale e poi anche:
rc-update show
Sono allergico a mele morsicate e a finestre con tende.

Segnalate qui le vostre offerte di smartphone e tablet!!!

Rispondi