Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Jessie coming soon!
Jessie coming soon!
Hello
Today I just get the notification from https://www.debian.org/News/weekly/2015 ... tml#Jessie
!!!
So before it's coming make sure that you remove that god damn systemd next to DRACUT, the new initramfs dynamic futuristic event driven automatic what the f* ever this garbage is.
I'm sick and tired that after I pulling in 3.16 and other recent kernels from the wheezy backports they replace initramfs-tools with this then I manually have to purge it out, recreate all the initramfs images but guess what, the crap stays inside in some images!!!
Yesterday I spent the entire day reconfiguring initrd images, rebooting a server million times which takes about 10 minutes to boot up just to get kernel 4 working with mdraid and at the end it failed.
Systemd+Dracut, I dont EVER want to see these again !!!
Today I just get the notification from https://www.debian.org/News/weekly/2015 ... tml#Jessie
!!!
So before it's coming make sure that you remove that god damn systemd next to DRACUT, the new initramfs dynamic futuristic event driven automatic what the f* ever this garbage is.
I'm sick and tired that after I pulling in 3.16 and other recent kernels from the wheezy backports they replace initramfs-tools with this then I manually have to purge it out, recreate all the initramfs images but guess what, the crap stays inside in some images!!!
Yesterday I spent the entire day reconfiguring initrd images, rebooting a server million times which takes about 10 minutes to boot up just to get kernel 4 working with mdraid and at the end it failed.
Systemd+Dracut, I dont EVER want to see these again !!!
Re: Jessie coming soon!
I run sid on two systems and jessie on another one and none of them has dracut.Deutsches wrote: So before it's coming make sure that you remove that god damn systemd next to DRACUT, the new initramfs dynamic futuristic event driven automatic what the f* ever this garbage is.
Maybe you've installed something that depends on it? (would be really weird).
Can you do apt-cache rdepends dracut and post the output?
Re: Jessie coming soon!
Code: Select all
dracut
Reverse Depends:
linux-image-3.16.0-0.bpo.4-amd64
|linux-image-3.16.0-0.bpo.4-amd64
dracut-network
Code: Select all
./init:. /lib/dracut-lib.sh
./init: loginit $DRACUT_QUIET </run/initramfs/loginit.pipe >/dev/console 2>&1 &
./init:[ -n "$VERSION" ] && info "dracut-$VERSION"
./init: warn "file a bug against dracut."
./usr/bin/mount-hook:type getarg >/dev/null 2>&1 || . /lib/dracut-lib.sh
./sbin/initqueue:type getarg >/dev/null 2>&1 || . /lib/dracut-lib.sh
./sbin/insmodpost.sh:. /lib/dracut-lib.sh
./sbin/lvm_scan:type getarg >/dev/null 2>&1 || . /lib/dracut-lib.sh
./sbin/dmraid_scan:type getarg >/dev/null 2>&1 || . /lib/dracut-lib.sh
./sbin/mdraid-cleanup:type getarg >/dev/null 2>&1 || . /lib/dracut-lib.sh
./sbin/mdraid_start:type getarg >/dev/null 2>&1 || . /lib/dracut-lib.sh
./sbin/loginit: if [ "$line" = "DRACUT_LOG_END" ]; then
./sbin/loginit: echo "<31>dracut: $line" >&5
./sbin/loginit: [ -n "$QUIET" ] || echo "dracut: $line"
./shutdown:. /lib/dracut-lib.sh
./lib/dracut/hooks/mount/99mount-root.sh:type getarg >/dev/null 2>&1 || . /lib/dracut-lib.sh
./lib/dracut/hooks/pre-pivot/50mount-usr.sh:type info >/dev/null 2>&1 || . /lib/dracut-lib.sh
./lib/dracut/hooks/pre-mount/10mdraid-waitclean.sh: type getarg >/dev/null 2>&1 || . /lib/dracut-lib.sh
./lib/dracut/dracut-:dracut-
./lib/dracut-lib.sh:hookdir=/lib/dracut/hooks
./lib/dracut-lib.sh: source_all "/lib/dracut/hooks/$_dir" "$@"
./lib/dracut-lib.sh: echo "<24>dracut: FATAL: $*";
./lib/dracut-lib.sh: echo "<24>dracut: Refusing to continue";
./lib/dracut-lib.sh: echo "warn dracut: FATAL: \"$*\"";
./lib/dracut-lib.sh: echo "warn dracut: Refusing to continue";
./lib/dracut-lib.sh: if [ -z "$DRACUT_QUIET" ]; then
./lib/dracut-lib.sh: DRACUT_QUIET="yes"
./lib/dracut-lib.sh: getargbool 0 rd.info -y rdinfo && DRACUT_QUIET="no"
./lib/dracut-lib.sh: getargbool 0 rd.debug -y rdinitdebug && DRACUT_QUIET="no"
./lib/dracut-lib.sh: getarg quiet || DRACUT_QUIET="yes"
./lib/dracut-lib.sh: [ -n "$a" ] && [ $a -ge 28 ] && DRACUT_QUIET="yes"
./lib/dracut-lib.sh: export DRACUT_QUIET
./lib/dracut-lib.sh: echo "<28>dracut Warning: $*" > /dev/kmsg
./lib/dracut-lib.sh: echo "dracut Warning: $*" >&2
./lib/dracut-lib.sh: echo "<30>dracut: $*" > /dev/kmsg
./lib/dracut-lib.sh: [ "$DRACUT_QUIET" != "yes" ] && \
./lib/dracut-lib.sh: echo "dracut: $*"
./lib/dracut-lib.sh: printf '. /lib/dracut-lib.sh\nismounted "%s"\n' $1 \
./lib/dracut-lib.sh: echo "DRACUT_LOG_END"
./lib/dracut-lib.sh: local _rdshell_name="dracut" action="Boot" hook="emergency"
./lib/fs-lib.sh:type getarg >/dev/null 2>&1 || . /lib/dracut-lib.sh
./etc/initrd-release:NAME="Dracut"
./etc/initrd-release:VERSION="7 (wheezy) dracut-"
./etc/initrd-release:ID=dracut
./etc/initrd-release:PRETTY_NAME="Debian GNU/Linux 7 (wheezy) dracut- (Initramfs)"
Re: Jessie coming soon!
That's what the OP said. Better question is, why in the f**k are backports enabled for this server's OS. OP, wut u smokin yo? Backports are for non mission critical desktops.pcalvert wrote:Have you installed anything from backports on those systems?
Phil
Edit: OP, did you really mean "Jessie-d coming soon!"
Linux Registered User 533946
Re: Jessie coming soon!
We're talking about just the kernel. No need for backports or any complicated dependency-dance. The OP could just install 3.16 from unstable and be happy ever after.Linadian wrote:That's what the OP said. Better question is, why in the f**k are backports enabled for this server's OS. OP, wut u smokin yo? Backports are for non mission critical desktops. :Ppcalvert wrote:Have you installed anything from backports on those systems?
Phil
And he should report a bug about the backported kernel depending on dracut.
Re: Jessie coming soon!
It looks like you were hit by Bug #771379Deutsches wrote:Hello
Today I just get the notification from https://www.debian.org/News/weekly/2015 ... tml#Jessie
!!!
So before it's coming make sure that you remove that god damn systemd next to DRACUT, the new initramfs dynamic futuristic event driven automatic what the f* ever this garbage is.
I'm sick and tired that after I pulling in 3.16 and other recent kernels from the wheezy backports they replace initramfs-tools with this then I manually have to purge it out, recreate all the initramfs images but guess what, the crap stays inside in some images!!!
Yesterday I spent the entire day reconfiguring initrd images, rebooting a server million times which takes about 10 minutes to boot up just to get kernel 4 working with mdraid and at the end it failed.
Systemd+Dracut, I dont EVER want to see these again !!!
Ben has it marked as "Solved" on the 8th April.
Re: Jessie coming soon!
Installed Jessie the other day.
And once again, kudos to all people contributing to Debian. I really like Gnome, and once again Gnome is implemented most 'lightly' than any other distro, the artwork (plymouth etc.) is professional-grade to complement the system and I really look forward to using it for the next two years
+ the opensource fontconfig is now so good i really don't need the patched ones anymore.
Best release ever, imho
And once again, kudos to all people contributing to Debian. I really like Gnome, and once again Gnome is implemented most 'lightly' than any other distro, the artwork (plymouth etc.) is professional-grade to complement the system and I really look forward to using it for the next two years
+ the opensource fontconfig is now so good i really don't need the patched ones anymore.
Best release ever, imho
Re: Jessie coming soon!
So can I change "wheezy" to "jessie" in sources.list and perform a dist-upgrade now? The latest stable still seems Wheezy here.fireExit wrote:https://twitter.com/debian/status/591908938171457536
EDIT: https://twitter.com/debian/status/591921041850634240
Re: Jessie coming soon!
i would wait until the process is completed (we are in the middle of the release) and would read this >> https://www.debian.org/releases/jessie/releasenotes
- Hallvor
- Global Moderator
- Posts: 2020
- Joined: 2009-04-16 18:35
- Location: Kristiansand, Norway
- Has thanked: 138 times
- Been thanked: 204 times
Re: Jessie coming soon!
Latest news are here: https://identi.ca/debian
[HowTo] Install and configure Debian bookworm
Debian 12 | KDE Plasma | ThinkPad T440s | 4 × Intel® Core™ i7-4600U CPU @ 2.10GHz | 12 GiB RAM | Mesa Intel® HD Graphics 4400 | 1 TB SSD
Debian 12 | KDE Plasma | ThinkPad T440s | 4 × Intel® Core™ i7-4600U CPU @ 2.10GHz | 12 GiB RAM | Mesa Intel® HD Graphics 4400 | 1 TB SSD
Re: Jessie coming soon!
Looks like twitter page is a bit faster to announce.Hallvor wrote:Latest news are here: https://identi.ca/debian
Won't it be safe to upgrade before CD's are tested and officially released? Does this procedure take much time?
Re: Jessie coming soon!
I don't know how knowledgeable you are, but if I were you, I'd keep my fingers crossed through the upgrade, don't expect any miracles, your going from a few tiny bits of systemd in Wheezy to a virtual puke-fest of systemd in Jessie, your swapping out inits on the fly, from a known good init to beta crapware. I wish you all the luck in the world.farukdgn wrote:So can I change "wheezy" to "jessie" in sources.list and perform a dist-upgrade now? The latest stable still seems Wheezy here.fireExit wrote:https://twitter.com/debian/status/591908938171457536
EDIT: https://twitter.com/debian/status/591921041850634240
Linux Registered User 533946
Re: Jessie coming soon!
Maybe a shock, but there's more to Jessie than just systemd. Some people may think Jessie is a kind of synonym to systemd...Linadian wrote:I don't know how knowledgeable you are, but if I were you, I'd keep my fingers crossed through the upgrade, don't expect any miracles, your going from a few tiny bits of systemd in Wheezy to a virtual puke-fest of systemd in Jessie, your swapping out inits on the fly, from a known good init to beta crapware. I wish you all the luck in the world.
Re: Jessie coming soon!
Systemd is the next generation standard in the enterprise. Anything with a few years experience in using it is valuable. If you don't like it personally, be the change. Though it won't go away until something better comes along.
Always on Debian Testing
Re: Jessie coming soon!
Woah, you really mean Redhat's "generation standard in the enterprise", who do you think you're kidding? Nice spin and soft peddling, you're funny.vbrummond wrote:Systemd is the next generation standard in the enterprise. Anything with a few years experience in using it is valuable. If you don't like it personally, be the change. Though it won't go away until something better comes along.
Face it, Debian got sucked in to the systemd black-hole vortex because it's a hobbled, castrated weak shell of its former self, RIP to Debian the trailblazing GNU warrior.
That MS love-in is especially hilarious too, Debian is bending over for anybody now, Debian would be the 'favourite' on any cell-block, lol. Yep folks, that's right, that link is an actual MS website purporting to its love for Debian and GNU, the trojan horse is entering the castle. *PUKE!*
Linux Registered User 533946
Re: Jessie coming soon!
You mean RedHat and SUSE pretty much the only two things that are worth getting certified in. I opted for SUSE and it has been worthwhile. Trolling will not change reality, systemd is here and not going away. If you think I am peddling, think again, I prefer the BSD init but I have nothing against systemd. It's whatever.
Always on Debian Testing